<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[accessibility-a11y - Medium]]></title>
        <description><![CDATA[Articles on Web Accessibility - Medium]]></description>
        <link>https://medium.com/accessibility-a11y?source=rss----4a795546f0a7---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>accessibility-a11y - Medium</title>
            <link>https://medium.com/accessibility-a11y?source=rss----4a795546f0a7---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:22:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/accessibility-a11y" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ARIA Landmark Roles]]></title>
            <link>https://medium.com/accessibility-a11y/aria-landmark-roles-459bc1a9e483?source=rss----4a795546f0a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/459bc1a9e483</guid>
            <category><![CDATA[aria]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[aria-landmark-roles]]></category>
            <dc:creator><![CDATA[Saptarshi Katwala]]></dc:creator>
            <pubDate>Sun, 28 Apr 2019 19:00:32 GMT</pubDate>
            <atom:updated>2019-04-28T19:00:32.680Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5t6pvtLhMQm2N12UBlU8g.jpeg" /></figure><p><strong>Introduction</strong>: ARIA stands for Accessible Rich Internet Applications. This is a W3C specification for adding mark up to HTML and is consumed by assistive technologies including screen readers. Adding such mark up clearly communicates the intent of the various elements of a Web Page.</p><p><strong>ARIA Landmark roles</strong>: ARIA Landmark roles define key areas of content on the page. These allow screen readers to understand the semantic structure of the page. So the structure of the page to be conveyed visually to users should be programmatically achieved using these roles.</p><p>There are 8 common ARIA landmark roles, these are:</p><p>role=”banner” (e.g. in header)<br>role=”navigation” (e.g., menu of links)<br>role=”main” (the main area of the page)<br>role=”complementary” (e.g., a sidebar)<br>role=”contentinfo” (e.g. footer containing legal terms)<br>role=”search”<br>role=”form”<br>role=”application”</p><p>These roles are shown in the diagram below for a sample web page style. This shows the first 5 ARIA landmarks, viz. banner, navigation, main, complimentary and contentinfo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Q14t7aa4tIsyds0nXPGDQ.png" /></figure><p>The above page design is somewhat common and developers can include these landmarks in their HTML and make this page much better understood by accessible technologies such as screen readers. A sample HTML showing these roles for the above layout is shown below (minus CSS):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Ln5B6uOOoiEwtplBeW7Ug.png" /></figure><p>Additionally if this layout had a search box and also a form, then the additional 2 landmark roles would also be used as shown in screen shot below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uf-4C373p093x9i8333Ybg.png" /></figure><p>Several screen readers including Voice Over, JAWS and NVDA support these roles.</p><p>The land mark role of application indicates to the screen reader that area (the element and all its children) should be treated as a desktop application and not like HTML page. This should be very rarely required to be used. Some known places where this has been used is in certain parts of Gmail, Google Docs and CKEditor. This is used for extremely sophisticated use-cases which are unlikely to occur for vast majority of web applications.</p><p><strong>HTML 5 elements</strong></p><p>HTML 5 has elements which are similar to ARIA landmarks as shown in table</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wz1mgbGyY3CuY2qtjmP4Mg.png" /></figure><p>Screen readers have a better support for ARIA landmarks than for their equivalent HTML elements. Hence it is recommended that even if developers are using the HTML 5 elements from the table above they also use ARIA Landmark roles.</p><p><strong>Conclusion</strong>: Using ARIA Landmark roles will enable assistive technologies to better convey the web page information to the end user. It is therefore recommended that such roles be used while developing web pages.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=459bc1a9e483" width="1" height="1" alt=""><hr><p><a href="https://medium.com/accessibility-a11y/aria-landmark-roles-459bc1a9e483">ARIA Landmark Roles</a> was originally published in <a href="https://medium.com/accessibility-a11y">accessibility-a11y</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Skip Links and Accessibility]]></title>
            <link>https://medium.com/accessibility-a11y/skip-links-and-accessibility-4e1b3809225a?source=rss----4a795546f0a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/4e1b3809225a</guid>
            <category><![CDATA[wcag]]></category>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[skip-link]]></category>
            <dc:creator><![CDATA[Saptarshi Katwala]]></dc:creator>
            <pubDate>Sun, 21 Apr 2019 19:17:08 GMT</pubDate>
            <atom:updated>2019-04-21T19:17:08.196Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5t6pvtLhMQm2N12UBlU8g.jpeg" /></figure><p><strong>Introduction</strong>: Skip Links allow better accessibility for key board devices where the user may not be able to use the mouse due to a disability. Skip Links allow user to skip repetitive navigation and go the the relevant content. In absence of Skip Links, the user would have to tab through several unnecessary navigation links.</p><p><strong>Steps to implement Skip Links</strong>: We need 2 main steps to implement skip links. These are:</p><ol><li>Have a skip link near the top of the page, ideally before the navigation. The skip link is a regular&lt;a href&gt; anchor that points to a div later in the page that has the relevant content.</li><li>Hide the skip link via css, show it only when the focus is on it, — usually when the page is opened.</li></ol><p>Let us look at skip links with an actual example.</p><p>When the user tabs after the page opens, the user sees “Skip to main content” link. Pressing Enter key here takes the user to the main section of “Loren Ipsun…”. So the user can skip the navigation links.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5-6qJulilDiHP56HSV2Mig.png" /></figure><p>Once the user tabs again the “Skip to main content” link disappears.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GA2t9XmA1cMQEhl0ycQdlQ.png" /></figure><p>Let us look at the code behind this.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2cd1980a57d92b5157610c3e9f5ec9a1/href">https://medium.com/media/2cd1980a57d92b5157610c3e9f5ec9a1/href</a></iframe><p>Above, the skip link is shown on lines 11 to 13. If a user were on this link and press the “Enter” key, the focus would go to the main div on line 27.</p><p>This skip link has go to be hidden when the focus is elsewhere on navigation links. This is done by CSS below non lines 6–9, where the top is outside the page at -100 px. When user tabs and reaches the skip link, then the top changes to 0px and the skip link is seen on the screen.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/af1d54959f3dd0067e2c77a7677675ee/href">https://medium.com/media/af1d54959f3dd0067e2c77a7677675ee/href</a></iframe><p><strong>Conclusion</strong>: Skip Links allow keyboard users to directly go to the relevant section of the page and are considered to be a good accessibility practice. There are users who have motor challenges and are not able to use mouse. Skip links benefit such users as they can directly go to a specific section of the page with fewer tabs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e1b3809225a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/accessibility-a11y/skip-links-and-accessibility-4e1b3809225a">Skip Links and Accessibility</a> was originally published in <a href="https://medium.com/accessibility-a11y">accessibility-a11y</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accessibility legislation: Section 508 vs WCAG]]></title>
            <link>https://medium.com/accessibility-a11y/accessibility-legislation-section-508-vs-wcag-dfe63ebcc97?source=rss----4a795546f0a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/dfe63ebcc97</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[section-508]]></category>
            <category><![CDATA[wcag]]></category>
            <dc:creator><![CDATA[Saptarshi Katwala]]></dc:creator>
            <pubDate>Sun, 14 Apr 2019 12:35:06 GMT</pubDate>
            <atom:updated>2019-04-14T12:38:17.481Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction</strong>: There are legal requirements to ensure that Websites are accessible by everyone. Here, in America, there are 2 common terms used in this context — Section 508 and WCAG. This article explains each of these terms and what it means in terms of compliance.</p><p><strong>WCAG:</strong></p><p>WCAG stands for Web Content Accessibility Guidelines. This is published by W3C. W3C is the governing body for all web standards and WCAG is its initiative as part of Web Accessibility Guidelines.</p><p>WCAG has had 3 major revisions, viz.</p><ol><li>version 1.0 published in 1999</li><li>version 2.0 which was published in 2008 and</li><li>version 2.1 that was published in 2018.</li></ol><p>Most organizations use version 2.0, so let us take a moment to review this. Then we will consider the newer features introduced in 2.1.</p><p><strong>WCAG 2.0:</strong></p><p>Version 2.0 compliance requirements are highly intuitive. The ask is that a web site be usable under the following 4 criteria. There are conformance levels for each criteria — levels A, AA and AAA. Level A suggests minimal conformance, AA greater conformance and AAA the highest conformance.</p><p>Perceivable : The major guidelines here are that images should be understood by visually impaired users (so assistive technology should read the narration of the image). That time based content — and by that the implication is for audio-video content — have alternate presentation available. So say the video content should have closed captioning for users who may have hearing difficulties as well as text representation. Likewise audio content to ta have text transcript.</p><p>Operable: Here the guidelines are around making the web page more navigable. Guidelines suggest that the site be usable via keyboard if a person cannot use the mouse, that content be easier to be found especially by assistive technology so that such users can directly go to a specific section of the page and not have to go through entire page, etc.</p><p>Understandable: Here the guidelines are around better comprehension, especially for consumers using assisted devices. An example here is that such users should be able to correct mistakes in data entry screens. E.g,. if a required field is missing, or say a wrong selection is made, the page should give sufficient indication to all users.</p><p>Robust: The web page should be understood by assistive technology such as screen readers.</p><p>Please refer to the check list published by Web AIM <a href="https://webaim.org/standards/wcag/checklist">here</a>. This is fairly detailed, the above is an executive summary of the same.</p><p><strong>WCAG 2.1:</strong></p><p>WCAG 2.1 was published in 2018. This has enhancements to take into account technical advancements that are now commonly used but were not that common 10 years earlier — when WCAG 2.0 was released. A detailed spec of WCAG 2.1 is found <a href="https://www.w3.org/TR/WCAG21/">here</a>. Below is an executive summary of some of the changes in WCAG 2.1:</p><p>Pointer: In past 10 years there have been advances in mobile devices such as tablets, smart phones, etc which are touch based. Here guidelines are around providing alternates for touch device gestures. So say pinch &amp; zoom or swiping must be performed using alternate gestures such as single, double or long tap.</p><p>Label in name: There have been advances in speech software. This guideline is geared towards this. It asks that a component be such that its label and its perceivable name be the same. E.g. if a button is shown as “Search” on the screen then its label should also be “Search”. That way if the user speaks “Search”. then voice recognition software will recognize this and trigger the Search action.</p><p>Orientation and Re-flow: The web page should be equally functional in both portrait and landscape mode. Zoom should be proportional, smooth and should not result in loss of functionality.</p><p>Content on Hover or Focus: The guidelines here are around modals and tooltips as there have been cases where such widgets were not easily accessible without using mouse. E.g. In case of modals, focus would switch to background page when consumed using assistive technologies. The guideline now suggests that user should be able to stay on this content (eg a form modal) and navigate using keyboard without loosing focus to the background page. User should be able to close such content using ESC key.</p><p>Timeouts: User should be clearly informed of time out. A common use case is when the user is going to be signed off from an authenticated site. There should be very clear notifications so that all users — including users with disabilities are clearly informed when such an event occurs.</p><p>Switching off animation that is not critical to functioning of site.</p><p><strong>Section 508:</strong></p><p>The Congress passed an act in 1973 called the Rehabilitation Act to help all individuals, including individuals with disability. In 1998 and 1999 this act was amended to make Electronic Information Technology be more accessible, this amendment was Section 508.</p><p>Section 508 is required if an organization is a government organization — eg a federal or a state agency or department. This is required of private companies if they do business with the government — e.g. government contractors and consulting firms hired by government. This is also required if an organization receives money from government. E.g. a non-for-profit may receive money from government to build a web site for its members then this site will have to be 508 compliant.</p><p>WCAG deals with web sites. Section 508 deals with all consumer technologies — this includes web sites, but also includes other technologies such as kiosks, etc.</p><p>Since Jan 2018, the government has modified Section 508 to include WCAG guidelines for A and AA conformance.</p><p>So for web sites, the decision making for conformance and compliance has become a bit easier. WCAG compliance to A and AA standards will now be accepted towards 508 compliance.</p><p>Conclusion: It is a good practice to review WCAG and Section 508 documentation each year to understand if there are any major changes that can impact the usability of the web assets. Achieving WCAG A and AA compliance will now be counted towards Section 508 compliance.</p><p>WCAG 2.0 guidelines <a href="https://www.w3.org/TR/WCAG20/">here</a>.</p><p>WCAG 2.1 guidelines <a href="https://www.w3.org/TR/WCAG21/">here</a>.</p><p>Section 508 guidelines <a href="https://www.section508.gov/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfe63ebcc97" width="1" height="1" alt=""><hr><p><a href="https://medium.com/accessibility-a11y/accessibility-legislation-section-508-vs-wcag-dfe63ebcc97">Accessibility legislation: Section 508 vs WCAG</a> was originally published in <a href="https://medium.com/accessibility-a11y">accessibility-a11y</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do an Accessibility Audit using Google Chrome LightHouse]]></title>
            <link>https://medium.com/accessibility-a11y/do-an-accessibility-audit-using-google-chrome-lighthouse-30ff7887901c?source=rss----4a795546f0a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/30ff7887901c</guid>
            <category><![CDATA[chrome-lighthouse]]></category>
            <category><![CDATA[a11y-testing]]></category>
            <category><![CDATA[chrome-accessibility]]></category>
            <category><![CDATA[accessibility-testing]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Saptarshi Katwala]]></dc:creator>
            <pubDate>Sat, 13 Apr 2019 15:23:09 GMT</pubDate>
            <atom:updated>2019-04-13T15:23:09.524Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5t6pvtLhMQm2N12UBlU8g.jpeg" /></figure><p><strong>Introduction</strong>: In the past few years there have been many tools and browser extensions which allow developers, testers and business teams to review their web assets for accessibility compliance. This article reviews the out-of-the-box built in features in Google Chrome browser that enable such reviews.</p><p><strong>Google Chrome Accessibility review features</strong>:</p><p>Open any page in Google Chrome and press either the F-12 key or right click and select “Inspect” option as shown in screen shot below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s0Wr2hR9KTT4cyFe0HHYnQ.png" /></figure><p>This opens the Chrome Dev Tools. If we select the “Audits” option, we get the screen that may look similar to the one shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ASvF9xjiogRDUEOec3Gl1A.png" /></figure><p>The audits feature which is based on <a href="https://developers.google.com/web/tools/lighthouse/">LightHouse</a> technology has several options for improving the quality of web pages including accessibility. This accessibility check feature uses axe-core technology developed by dequeue systems.</p><p><strong>Using LightHouse Audits in Chrome to test a page for Accessibility</strong>:</p><p>Consider a very simple web page as shown below.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/304b5574b870960d81e1e7e6572de4c4/href">https://medium.com/media/304b5574b870960d81e1e7e6572de4c4/href</a></iframe><p>Let us run this on a web server (as Google Chrome Audit tools for accessibility will require page running on web server). Once this done, the page will look like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iq8k_tMCgbrfN69BGle-Mw.png" /></figure><p>Now click Inspect and open dev tools and go to Audits like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lKd-4yk_4MsKq2mLj0vaBQ.png" /></figure><p>Only check the Accessibility check box and click the run audits button. We will get an accessibility score as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vCK3dsnoHkAEWJEze9G_6g.png" /></figure><p>We get a score of 30 — which is somewhat low. The neat thing about this audit is that it gives the developer very powerful suggestions on how to improve the accessibility score. Let us review the suggestions offered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ef27UmAzeCR8qvg_Apl8pQ.png" /></figure><p>The suggestions to increase the score are :</p><ol><li>To have a &lt;title&gt; element which is a desirable feature for screen readers.</li><li>Specify Language — again this is immensely helpful to assistive technology such as screen readers</li><li>Image not having the alt attribute. The assistive technology will narrate the information in the alt attribute so that a user with seeing difficulty can understand the content.</li></ol><p>Let us implement these suggestions. These are shown in the code below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8254fb6cfe6c60d24e09c16d543d212a/href">https://medium.com/media/8254fb6cfe6c60d24e09c16d543d212a/href</a></iframe><p>We have made the following 3 changes per the earlier recommendation by Audit Accessibility test.</p><ol><li>Added the language attribute on line 2</li><li>Added title (line 4, also added head tag recommended for title, lines 3 and 5)</li><li>Added alt tag on line 9</li></ol><p>Now let us refresh this page in the browser and re-run Accessibility audit.</p><p>This time the score goes to 100% meaning that the page is consistent with industry standard best practices for accessibility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9csCGNkQcG1KWZrXerLeEA.png" /></figure><p><strong>Conclusion</strong>: Google Dev Tools offers a very easy to use and extremely sophisticated Audit facility for Accessibility. The suggestions offered to improve accessibility are very relevant and presented in a manner which is easy to implement.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30ff7887901c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/accessibility-a11y/do-an-accessibility-audit-using-google-chrome-lighthouse-30ff7887901c">Do an Accessibility Audit using Google Chrome LightHouse</a> was originally published in <a href="https://medium.com/accessibility-a11y">accessibility-a11y</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best Practices on aria-label, aria-labelledby and aria-describedby]]></title>
            <link>https://medium.com/accessibility-a11y/best-practices-on-aria-label-aria-labelledby-and-aria-describedby-913fc9e396ae?source=rss----4a795546f0a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/913fc9e396ae</guid>
            <category><![CDATA[arai-labelledby]]></category>
            <category><![CDATA[aria-label]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[aria-describedby]]></category>
            <dc:creator><![CDATA[Saptarshi Katwala]]></dc:creator>
            <pubDate>Sat, 06 Apr 2019 18:31:36 GMT</pubDate>
            <atom:updated>2019-04-06T18:46:45.808Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5t6pvtLhMQm2N12UBlU8g.jpeg" /></figure><p><strong>Introduction:</strong> ARIA, also known as WAI-ARIA stands for Web Accessibility Initiative — Accessible Rich Internet Applications (WAI-ARIA). This is a specification describing how to achieve accessibility for websites (developed using AJAX, JavaScript, HTML, which is how most websites in past few years have been).</p><p>Aria offers roles, states and attributes which enable assistive technologies such as screen readers to better understand (and better narrate) the web page. In this article, we look at 3 ARIA attributes viz. aria-label, aria-labelledby and aria-describedby and the use cases for each.</p><p><strong>Similarities and Differences between aria-label, aria-labelledby and aria-describedby</strong></p><p><strong>aria-label</strong> This attribute can be attached to any HTML element. The screen reader will announce the label text when the user is on this element. In the example below the screen reader will announce “Real time news by CNN”</p><pre>&lt;a href=&quot;...&quot; aria-label=&quot;Real time news by CNN&quot;&gt;<br>  CNN<br>&lt;/a&gt;</pre><p><strong>aria-labelledby</strong> This attribute allows the label to be set based on content of other ids. E.g. in the code below, we have 3 divs with ids of account, firstName and lastName. The div with id of account has the value of “Primary Account Holder”. The div with the id of firstName has the value of “First Name”. So when the screen reader reaches the line <em>&lt;input type=”text” aria-labelledby=”account firstName”/&gt;</em>,<em> </em>it will announce “Primary Account Holder First Name”.</p><pre>&lt;html xmlns=&quot;<a href="http://www.w3.org/1999/xhtml">http://www.w3.org/1999/xhtml</a>&quot; xml:lang=&quot;en&quot; lang=&quot;en&quot;&gt;</pre><pre>&lt;head&gt;<br>      &lt;meta http-equiv=&quot;Content-Type&quot; content=&quot;text/html; charset=utf-8&quot;/&gt;<br>      &lt;title&gt;Demo&lt;/title&gt;<br>&lt;/head&gt;</pre><pre>&lt;body&gt;</pre><pre>&lt;div id=&quot;account&quot;&gt;Primary Account Holder&lt;/div&gt;</pre><pre>   &lt;div&gt;<br>        &lt;div id=&quot;firstName&quot;&gt;First Name&lt;/div&gt;<br>        &lt;input type=&quot;text&quot; aria-labelledby=&quot;account firstName&quot;/&gt;<br>   &lt;/div&gt;</pre><pre>   &lt;div&gt;<br>      &lt;div id=&quot;lastName&quot;&gt;Last Name&lt;/div&gt;<br>      &lt;input type=&quot;text&quot; aria-labelledby=&quot;account lastName&quot;/&gt;<br>    &lt;/div&gt;<br>&lt;/body&gt;</pre><pre>&lt;/html&gt;</pre><p><strong>aria-describedby</strong> This is very similar to <strong>aria-labelledby</strong> described above.This attribute allows the description to be set for an element based on ids.</p><p>So what is the difference between aria-describedby and aria-labelled-by? This is hard to tell as both these are very similar. A label describes the essence of an element where as the description provides greater information to help the user. So aria-described by tends to be longer although this is only a heuristic, not a rule.</p><p><strong>Use Cases where these can be leveraged:</strong></p><p>aria-label, aria-labelledby and aria-describedby can be used in interactive HTML elements.</p><p>These should not be used for non interactive elements such as &lt;div&gt;, &lt;span&gt;,etc.</p><p>The best use case for leveraging the above attributes is form inputs. Here either aria-label or one of aria-labelledby or aria-describedby can help screen readers.</p><p>Other interactive elements such as button may not require the above attributes although these can still be used. E. g. a screen reader would be able to read the narration “Save Form” quite easily and hence the above attributes may not be required.</p><pre>&lt;button&gt;Save Form&lt;/button&gt;</pre><p><a href="https://developer.paciellogroup.com/blog/2017/07/short-note-on-aria-label-aria-labelledby-and-aria-describedby/">Here</a> is a good note from Paciello Group on suggestions on when to use the above attributes.</p><p><strong>Conclusion:</strong> Either aria-label or one of aria-labelledby and aria-describedby allow the screen reader to better narrate the inputs of a form to the user and should be used in form input elements. Hence these must be leveraged while developing web forms.</p><p>Using these attributes on other interactive elements will also help. However there are other ways by which screen readers can read such elements (as described in the button example above). Hence these attributes are not required to be used exclusively for most interactive elements except form inputs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=913fc9e396ae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/accessibility-a11y/best-practices-on-aria-label-aria-labelledby-and-aria-describedby-913fc9e396ae">Best Practices on aria-label, aria-labelledby and aria-describedby</a> was originally published in <a href="https://medium.com/accessibility-a11y">accessibility-a11y</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accessibility and Captcha]]></title>
            <link>https://medium.com/accessibility-a11y/accessibility-and-captcha-265fd6ee6bb9?source=rss----4a795546f0a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/265fd6ee6bb9</guid>
            <category><![CDATA[recaptcha]]></category>
            <category><![CDATA[nocaptcha]]></category>
            <category><![CDATA[captcha]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Saptarshi Katwala]]></dc:creator>
            <pubDate>Sun, 31 Mar 2019 19:06:21 GMT</pubDate>
            <atom:updated>2019-03-31T19:13:32.086Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*h9yKtHgbR_IzQ9TF9PDW8A.jpeg" /></figure><p><strong>Summary</strong>: This article discusses issues around accessibility related to Captcha Implementations and looks at the NoCaptcha ReCaptcha approach.</p><p>Captcha is an acronym for Completely Automated Public Turing test to tell Computers and Humans Apart. This is a challenge used by many websites to distinguish human users from automated bots. Here is a sample screenshot of a Captcha challenge. The user is asked to type the words seen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*iubB5ZbuNPN5DIWLEAPtnQ.png" /></figure><p>Alternately, the user is presented with a voice recording and asked to type the word(s) heard.</p><p>The visual or audio captcha challenges are designed to allow humans to process these but make it hard for machines (programs, bots) to process these. Hence the visual captcha can have wavy characters. It can also have wavy ,curly and sometime strikethrough lines (as seen in screen shot above) to make it hard for a program to process these. An audio captcha can have whispers or other background noise to prevent machines from processing this.</p><p><strong>Accessibility Challenges</strong>:</p><p>Captcha present a problem for Accessibility. Visual Captcha cannot contain alt-text; because then it would defeat the purpose of having captcha to begin with. alt-text can be easily read not only by screen readers but also by bots and programs that should not be using such web sites. The captcha exists to prevent such bots from the web site. Hence captcha cannot contain alt-text and hence screen readers cannot read the captcha.</p><p>Similarly, an audio Captcha cannot have associated text file describing its challenge — doing so again would allow bots to read the challenge very easily and defeat the purpose of using Captcha. However this makes it hard from an Accessibility perspective.</p><p><strong>NoCaptcha reCaptcha</strong></p><p>To overcome above issues, Google has built 2 solutions which are available for free and can be integrated into any web form. These are called reCaptcha version2 and reCaptcha version 3. reCaptcha version 3 is also referred to as No Captcha for reasons that we will soon see.</p><p>reCaptcha version 2: This is a very powerful solution and will serve a great many web sites. The web site user is asked to check a simple check box as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/402/1*SbyEsV1sZFvAIJ7NqYjfIw.png" /></figure><p>This check box processed by screen readers — so the screen readers are able to announce this check box to the user.</p><p>This check box is also accessible by the keyboard, so without a mouse the user can select interact with this reCaptcha 2.0 widget.</p><p>Google is also offering a more advanced version of reCaptcha — called reCaptcha version 3.0. This will work invisibly behind the scenes. There is no widget such as the one above. This is how reCaptcha 3.0 may work in principle (the actual algorithm is not yet public) to distinguish a bot from a human:</p><p>When a user uses a web site, reCaptcha 3.0 will track mouse movements, cookies, etc and use Machine Learning to make subtle distinctions between the mouse movements of a human (vs. that of a bot).</p><p>It will also track other parameters such as the IP address of the user (so the user location), the number of requests being made to this page from this IP (bots will typically make multiple requests), etc.</p><p>In both reCaptcha version 2.0 and 3.0, if the Google algorithm is not satisfied, it will still pose a regular Captcha challenge, however the chances are of this are negligible with users on screen readers.</p><p><strong>Summary</strong> : Google reCaptcha versions 2 or 3 should be considered to defeat spammers on web pages. It needs to be understood that this will involve sending minimal user pattern data to the Google servers (as the check for bots vs humans and issuing the challenge — if any, will run on their servers.) . Further that this integration requires minimal JavaScript programming. The documentation for including reCaptcha version 2 or 3 is at <a href="https://developers.google.com/recaptcha/intro">https://developers.google.com/recaptcha/intro</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=265fd6ee6bb9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/accessibility-a11y/accessibility-and-captcha-265fd6ee6bb9">Accessibility and Captcha</a> was originally published in <a href="https://medium.com/accessibility-a11y">accessibility-a11y</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using aXe Command line to evaluate a web page for accessibility]]></title>
            <link>https://medium.com/accessibility-a11y/using-axe-command-line-to-evaluate-a-web-page-for-accessibility-1cc4be4aacc9?source=rss----4a795546f0a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/1cc4be4aacc9</guid>
            <category><![CDATA[axe-core]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[a11y]]></category>
            <dc:creator><![CDATA[Saptarshi Katwala]]></dc:creator>
            <pubDate>Sun, 24 Feb 2019 19:37:11 GMT</pubDate>
            <atom:updated>2019-02-24T19:38:05.035Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ZYU5CjDlSPcv_5U8pAFGmQ.jpeg" /></figure><h3>Using axe command line to evaluate a web page for accessibility</h3><h4>Introduction:</h4><p><a href="https://www.npmjs.com/package/axe-core">axe-core</a> is a JavaScript Framework for enabling automated testing of Web Pages for identifying Accessibility issues. It is high configurable, open source and has the backing of Deque Systems — which is a prominent company in the accessibility and the digital equality space. This article shows how to get started with axe-core and how to use this to test a web pages using command line.</p><p>Intended audience:</p><ul><li>Developers</li><li>QA — Testers of Web pages</li><li>Product Owners of IT Web Applications</li></ul><h4>Downloading axe-core</h4><p>axe-core is an open source JavaScript framework available as a download via npm — node package manager.</p><p>To download axe-core, Node JS needs to be installed. Here are the instructions for <a href="https://nodejs.org/en/">installing Node JS</a>.</p><p>Once Node JS is installed, one can install axe-core by the following command:</p><pre>npm install axe-cli -g</pre><p>This installs axe globally and can be accessed from any folder in the file system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_iFXYquED_nyUthcO5JHrw.png" /></figure><p>Once installed, to test any web page, use the following command.</p><pre>axe web-page-url --timeout=120 --save results.json  --tags wcag2a</pre><p>The above command will test the page at the specific url and save the results in a file called results.json. The value of the time out can be changed. The tags option specifies the rules to be run. There are several tags supported oiut of the box by axe framework. For the above example we are running the WCAG2.0 rules at level A. Other tags include</p><ul><li>wcag21aa (Level AA of WCAG 2.1 guidelines)</li><li>section508 (guidelines for section 508)</li><li>experimental</li><li>best-practice (as endorsed by Deque systems on accessibility)</li></ul><p>E.g. to test <a href="http://www.google.com,/">www.google.com,</a> use the following command:</p><pre>axe <a href="http://www.google.com/">www.google.com</a> --timeout=120 --save results.json  --tags wcag2a</pre><p>Running this produces the following output:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z2b43eH4EOyBAReQwqEipw.png" /></figure><p>It identifies 2 violations (these results as these violations may get rectified). A detailed report is saved in file results.json. Open this file in a JSON editor. Drill down to the violations attribute. The details of the Accessibility violations along with suggestions for fixes will be seen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nQiViQDj9IEgzVE_fj17ZA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NgTpmpNnYEwT7p3j3gu9Zg.png" /></figure><h4>Conclusion</h4><p>axe-core is a very powerful framework that can help developers and IT teams build web products that are inclusive. In this article we have seen how to do install and use axe-core for testing a web page. In another article, we will look at how to include this framework in local codebase and how to run this framework and the accessibility rules during each build of the codebase.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cc4be4aacc9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/accessibility-a11y/using-axe-command-line-to-evaluate-a-web-page-for-accessibility-1cc4be4aacc9">Using aXe Command line to evaluate a web page for accessibility</a> was originally published in <a href="https://medium.com/accessibility-a11y">accessibility-a11y</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 steps to create Accessible Documents]]></title>
            <link>https://medium.com/accessibility-a11y/5-steps-to-create-accessible-documents-ee7fbf276434?source=rss----4a795546f0a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/ee7fbf276434</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[accessible-documents]]></category>
            <dc:creator><![CDATA[Saptarshi Katwala]]></dc:creator>
            <pubDate>Sun, 24 Feb 2019 15:49:08 GMT</pubDate>
            <atom:updated>2019-02-24T15:49:08.745Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ZYU5CjDlSPcv_5U8pAFGmQ.jpeg" /></figure><h4>Introduction</h4><p>An accessible document is a document that can be understood and better narrated by screen readers and other assistive technologies. Per National Institutes of Health, at any given time, 15% of the population is disabled — partially or otherwise. If a document is authored and created with accessibility in mind, it will help everyone read these documents.</p><p>This article describes 5 ways to make a document accessible with an example. We will create a simple document in Microsoft Word with accessibility in mind, but the principles will apply to other document editors such as Open Office equally so.</p><h4>5 step check list</h4><p>To create an accessible document, the following 5 features of MS Word (or equivalent document editor) must be explicitly used.</p><ul><li>For Headings and Sub-Headings, used the heading styles provided by the document editor. Screen Readers treat headings separately and allow users to switch between headings. Kindly do not use a higher bold font for headings as screen readers will not be able to switch between such headings. The Heading Styles provided by Word are shown below.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gxY8BkDYL42vy4AOnBcmNg.png" /></figure><ul><li>For list items, use the built in list option. Screen readers understand and can announce to the user that a list is being read. Otherwise the screen reader will read the items without the user realizing that this is a list and the comprehension will not be as clear.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ue7WvpuXOROmVYyh5G2TeA.png" /></figure><ul><li>Use Alt Text For Images. The screen reader cannot read an image but it can announce the content of Alt Text so that the user can understand what this image is about , which results in better comprehension. Otherwise the user will just hear that there is an image — which is not as helpful as knowing what this image is about. In MS Word, right click on a picture, select “Format Picture…”. In the Format Picture dialog box, enter the values of Title and Description.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6U6TOCqO3y9QLF2juPV8kQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a3Q7r5os7Odjuj5lay5Z0w.png" /></figure><ul><li>Specify the language of the document. This is true of documents which are to be shared across different locales, eg same document being shared across different countries with different languages. Screen readers may otherwise assume the local language which may be different than the language of the document. In MS Word, this is under Tools, Language.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jDtUr3WZB4CDjHYWNeB2WA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3u5jlK_o_w0OrbpepD4OQg.png" /></figure><ul><li>Finally, document editors offer feature(s) to check the document for accessibility. Once the document is ready, run this feature as it will check the document and suggest changes specific to accessibility if necessary. In Word this is under “Tools, Check Accessibility”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ai1c0a2ne25AkNguYjKtwA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rOibgW2r0ZMvIefkRdHXDA.png" /></figure><h4>Conclusion</h4><p>When creating documents, leveraging the following 5 features of document editor, will lead to content that will be much better understood by assistive technologies including screen readers.</p><ol><li>Use built In Headings and Sub headings</li><li>Use built in Lists (for list items)</li><li>Specify Alt Text for Images</li><li>Specify that language of the document</li><li>Use built in Accessibility checkers</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee7fbf276434" width="1" height="1" alt=""><hr><p><a href="https://medium.com/accessibility-a11y/5-steps-to-create-accessible-documents-ee7fbf276434">5 steps to create Accessible Documents</a> was originally published in <a href="https://medium.com/accessibility-a11y">accessibility-a11y</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 highly effective ways to audit a web page for Accessibility]]></title>
            <link>https://medium.com/accessibility-a11y/3-highly-effective-ways-to-audit-a-web-page-for-accessibility-de6da178a900?source=rss----4a795546f0a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/de6da178a900</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[a11y-audit]]></category>
            <category><![CDATA[doing-accessibility-audit]]></category>
            <dc:creator><![CDATA[Saptarshi Katwala]]></dc:creator>
            <pubDate>Sat, 23 Feb 2019 20:54:33 GMT</pubDate>
            <atom:updated>2019-02-23T20:54:33.669Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ZYU5CjDlSPcv_5U8pAFGmQ.jpeg" /></figure><p>Here are 3 simple, free and effective ways to check a web page or a complete web application for Accessibility. These can be performed on any operating system. These are:</p><ul><li>Use a Screen Reader to read that page (or the web application)</li><li>Use Key Board Tabs on the page and check the behavior</li><li>Use browser dev tools. Here we will look at built in Accessibility features of Chrome</li></ul><h4>Step 1 . Screen Reader</h4><p>Run the web page through the screen reader. This is the real test because users who face accessibility challenges will be doing this. Other techniques suggested here will be secondary, this one will be primary.</p><p>When the page is read by screen reader, the following 3 steps need to be explicitly verified:</p><ul><li>That Screen reader should be able to scan the page. The screen reader must call out headings, landmarks, images, forms, etc and allow the user to directly go to such sections if the user so desires. Apple Voice Over Screen reader that is available in Macs out-of-the-box achieves this via a Modal which is called the Rotor. The screen shot below is for illustration only. It shows the Wikipedia page for Earth being read by a screen reader (Voice Over). Using Voice Over’s “Control+Option+U”, the rotor which resembles a dark grey modal window appears over the page. Now using right or left arrows will cause information such as summary, headings, forms, etc to appear. Using top or bottom arrows, the user can select a specific element on the page from here.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*6ej38iYSMYIg9qmNQtLDWw.png" /></figure><ul><li>That the user should be able go across headings (which is similar to the above bullet point, but slightly different in that, that the user can key tab to each heading and sub heading, without a modal rotor). In Voice Over this is achieved by “Control+Option+Command+T”. Screen shot below shows the user have reached a particular heading using this approach without the rotor.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*6i_bE3aoSnjLmP9bouzhnw.png" /></figure><ul><li>That the screen reader should be able to read the text content and the alt-text for images.</li></ul><p>In this step, we check if Headings are proper, if Landmark elements are correctly used and whether alt-texts for images is proper as screen reader will read the alt-text.</p><h4>Step 2. Manual Verification</h4><p>Here we check keyboard tab key navigation. Each field or link should be accessible using tab keys in the correct order. User should be able to submit the data if the client side validations are proper via Enter key, however is data entry is pending or if there are client side errors then the user should not be able to submit, so the submit button must be correctly enabled or disabled.</p><p>An additional condition here is that notifications (eg success or failure) must be easily perceivable or recognizable to the users.</p><p>Modal windows if any should be focusable and focus should stay on such window till the user explicitly closes this window. Keyboard focus must not escape to the background screen as long as the modal is open</p><h4>Step 3. Browser Dev Tools.</h4><p>There are several browser extensions available for validating accessibility. This is a dynamic area with large amounts of innovation.</p><p>For this article, we are recommending the Chrome Dev Tools which are available out-of-the box with Google Chrome.</p><p>Open the web page that you want to audit for in Chrome and right click, select Inspect. In the Inspect window, select Audits.</p><p>In the Audits pane, select the Accessibility Audit Option. This internally runs the AXE technology built by Deque systems. Deque has also made its technology available as Chrome and Firefox browser extensions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kuyl_HGCctMOIkFBKh1sug.png" /></figure><p>Clicking “Run Results” produces a report which highlights any Accessibility Issues. One such sample report for illustration purposes is shown below. It shows a score of 70% with 4 accessibility issues having been identified. Per this report these 4 issues are</p><ul><li>image not having alt attribute (so screen reader will not be able to narrate the image)</li><li>button not having an accessible name (screen reader will not be able to narrate the button properly)</li><li>insufficient color contrast (making it hard for individuals with visual issues to see this page well)</li><li>page not having the lang attribute (this can be an issue for screen readers when locales and languages are being changed or the content is not in the default language)</li></ul><p>The error message is very specific — so each part in code where this failure occurs is identified and possible solutions or suggestions are offered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3S3Y_EPIOEEES57r6OZMJw.png" /></figure><h4>Conclusion:</h4><p>Using an actual screen reader, doing manual accessibility inspections and using Browser Dev Tools (such as Chrome Light House which uses aXe toolset developed by Deque systems) are 3 very effective ways to test a web page for Accessibility Issues.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de6da178a900" width="1" height="1" alt=""><hr><p><a href="https://medium.com/accessibility-a11y/3-highly-effective-ways-to-audit-a-web-page-for-accessibility-de6da178a900">3 highly effective ways to audit a web page for Accessibility</a> was originally published in <a href="https://medium.com/accessibility-a11y">accessibility-a11y</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reading a Web Page using Apple Voice Over]]></title>
            <link>https://medium.com/accessibility-a11y/reading-a-web-page-using-apple-voice-over-cd1a637e6285?source=rss----4a795546f0a7---4</link>
            <guid isPermaLink="false">https://medium.com/p/cd1a637e6285</guid>
            <category><![CDATA[screen-reader-basics]]></category>
            <category><![CDATA[apple-voice-over]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Saptarshi Katwala]]></dc:creator>
            <pubDate>Sat, 23 Feb 2019 16:26:43 GMT</pubDate>
            <atom:updated>2019-02-23T16:31:27.570Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5t6pvtLhMQm2N12UBlU8g.jpeg" /></figure><p>Apple Voice Over is a very powerful screen reader. It is available out-of-box in Macs and in iOS devices including iPads and iPhones. This article shows how to quickly get started using Apple Voice Over and how can it enable reading or more specifically the narration of web pages. This goes over the following 3 use cases:</p><ul><li>Using Voice Over to scan and find a specific section</li><li>Going through headings one at a time</li><li>Reading using Voice Over</li></ul><h3><strong>Intended audience</strong></h3><ul><li>Users who would like to read web pages being read out</li><li>Digital Product Owners wanting to test their web pages for accessibility</li><li>Mac access required</li></ul><h3><strong>Starting Voice Over</strong></h3><p>There are at least 2 ways to start Voice Over.</p><ol><li>Keyboard Short Cut — Command + F5 .</li><li>Going to System Preferences; clicking Accessibility and clicking the Enable Voice Over Check box</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dKkhLcd59bmEOIoz3ntABw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ht3G1KLbBr8_vVA5MAzw2Q.png" /></figure><h3>Reading Wikipedia page using Voice Over</h3><p>Let us consider a fairly common use case of screen reader — in fact the most canonical use case. A user is looking for specific information on a web page that contains lot of content. E.g. the user opens Wikipedia page of Planet Earth to look for physical characteristics of earth. The user will scan through the headings, the sub headings, the tables, images, captions under the images, etc. till she (or he) finds the specific section of interest.</p><p>Voice over allows such a narrated scan of content. This feature in Voice Over is called Rotor and is activated using keyboard short cut of “Control+Option+U”. The “Control + Option” key is also known as VO key (within Voice Over documentation). So in Voice Over documentation, this command may be expressed as VO-U.</p><ol><li><strong>Scan (via narration of Voice Over) . the main items of the page</strong></li></ol><p>The rotor appears as shown in screen shot below. Is shows an empty modal windows titled “Web Spots”. Now let us use this rotor modal window to scan this page to identify specific section of interest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sn03FfRnxFcuhtj2ds2bPQ.png" /></figure><p>To do the, keep pressing the Right Arrow Key or the Left Arrow Key.</p><p>For each press, views and corresponding narrations for the following items will appear that exist on the page</p><ul><li>Tables</li><li>Landmarks</li><li>Articles</li><li>Headings and Sub Headings</li><li>Forms</li></ul><p>Clicking the Up or Down Arrow and Enter key will allow user to go the specific section. This closely resembles the behavior of normal users who would be looking for specific items, they would scan for such items and go to that section to read more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LhAwiHusFIzOk1WcUm7qBw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zULvk7lSzaM3XfLXS5wg9w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P0pyNJ8C969plifBQUvBVQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ej38iYSMYIg9qmNQtLDWw.png" /></figure><p><strong>2. Go to each Heading without using the Rotor</strong></p><p>The rotor is great feature but Voice Over has other powerful features that allow users to read the page strategically. If the user wanted to read each heading on the page, they would use the command, “Control+Option+Command+T”. Now for each such click the screen reader will travel to the next heading (or a sub heading within heading). The screen shot below shows the heading of Physical Characteristics having been selected (and also narrated) by Voice Over using this command. The “Control + Option” key is also known as VO key (within Voice Over documentation). So in Voice Over documentation, this command may be expressed as VO-Command-T.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6i_bE3aoSnjLmP9bouzhnw.png" /></figure><p><strong>3. Start Reading the Page</strong></p><p>The Voice Over Command for this is “Control + Option + A” or VO-A, pressing the “Control” key stops the reading.</p><p><strong>Conclusion</strong> : While there are many Voice Over commands, the Rotor (VO-U) is very effective in consuming informational content on a page as normal user would. Its companion command “VO-Command-T” allows users to scan and hear headings. Once a specific section is identified, Voice Over will narrate that section using VO-A.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd1a637e6285" width="1" height="1" alt=""><hr><p><a href="https://medium.com/accessibility-a11y/reading-a-web-page-using-apple-voice-over-cd1a637e6285">Reading a Web Page using Apple Voice Over</a> was originally published in <a href="https://medium.com/accessibility-a11y">accessibility-a11y</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>