UAAG 2.0 Reference: Explanations, Examples, and Resources for User Agent Accessibility Guidelines 2.0

Applies to:

Content user interface, Configuration settings (optional)

Typically Implemented in:

browser, media player, plugin, add-on (e.g. to render longdesc)

Intent of Success Criterion 1.1.1:

Users with some disabilities can find a specific content element causes them physical pain (e.g. an image with high contrast) or distress (e.g. an image that triggers post traumatic stress disorder), or that the element's size can make the page difficult to use (because of difficulty scrolling, or shifting gaze, or moving the pointer more than a certain distance). In these cases the user needs to be able to hide that element or replace it with alternative content or a placeholder. Other users can find specific elements are simply unusable (e.g. an image that is too low contrast for the user's vision). In these cases the user needs to be able to access author-provided alternative content (e.g. alt text or longdesc) or the very minimum a placeholder (e.g. filename).

Some users with disabilities need alternate languages or audio tracks (e.g. descriptive video). Users need the ability to choose tracks that best meet their accessibility needs (e.g. the caption track in their own language) when authors have provided many alternatives.

Note: If the user cannot directly select or choose the element in order to perform commands upon it (e.g. if the browser does not support clicking on HTML background images or moving focus to them with the keyboard), the user agent must provide an alternative user interface for this feature.

Examples for Success Criterion 1.1.1:

• Rodney has low vision and finds some images on a web page are painful to look at. He can hide foreground images by right-clicking on them or pressing the Tab key to move focus to them, and then choosing a command from the element's context menu. However, the browser does not let him right-click or navigate to the background image. Therefore it provides a user preference setting to hide all background images or to hide the background image on the current site.
• Carly has repetitive strain injuries and uses speech recognition to communicate with her computer. She's a paralegal and often has to search long documents for terms that are rendered as acronyms. It's often easier for her to speak full terms into the search box rather than acronyms because full terms are easier to say and better recognized, and this allows her to keep her vocabulary less cluttered by acronyms that can increase misrecognitions. She chooses a setting on her browser that automatically expands all acronyms and abbreviations before she does a search.
• Laura has impaired vision and uses the shapes of words to help her recognize them easily. It is more difficult for her to read strings of seemingly random upper case letters than strings of familiar words written with only their initial letters capitalized, so she changes her preference settings to have all abbreviations replaced by their expanded strings.
• Betty has an auditory processing problem. She is watching a movie that has several caption and audio tracks. She pulls up a menu to determine which tracks are available and switches between audio tracks until she find one she can understand. She also reinforces the audio by selecting a caption track.
• Marka is blind. She is listening to a video of a lecture. The professor is demonstrating a chemistry experiment and is not speaking during a key portion of the video. Since Marka cannot see what the professor is demonstrating, she brings up a menu of the available tracks and discovers that there is an audio description track available. Marka selects the description track, skips back, and listens to the description of the experiment.
• Gorges has profound hearing loss. He enjoys current run movies, and subscribes to a web service that streams major popular movies. Although he speaks English, he doesn't understand all the slang in the movie. He pauses the movie, selects a menu of caption tracks and finds a Spanish caption track. He watches the rest of the movie with Spanish captioning.

Related Resources for Success Criterion 1.1.1:

• Firefox extension "Text Equivalent Expand Abbreviations"

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, media player, plugin, add-on

Intent of Success Criterion 1.1.2:

Users need to be able to easily discover when authors have provided alternative web content that may be of interest so they can decide whether to have it rendered (see Success Criterion 1.1.1). While the type of indicator is not prescribed, the success criterion requires that the indicator be placed along with the rendered content that has the alternative. This rules out indicators such as in the status bar, that don't clearly identify which content within a document has the alternative. Suitable indicators include outlines, adjacent icons, and adjacent links. As with any other feature of the user agent, the indicator itself must be accessible (e.g. keyboard accessible, alternative text, zoomable).

Examples for Success Criterion 1.1.2:

• Chris is color blind. He doesn't use a screen reader or other assistive technologies, but sometimes has difficulty interpreting diagrams where the author has used color alone to convey meaning (e.g. to label lines). Therefore, Chris likes to read long descriptions when the author has provided them. To let himself know when long descriptions are available, Chris sets a setting in his browser that places a "Description" link adjacent to any image with a long description. Chris clicks the link the open the long description in a new browser pane.
• Aosa is blind. When rendering a web page using synthesized speech, the user agent generates an audible tone to signify that the word being read is an acronym, and Aosa can press the * key to hear the expansion. When the phrase being read is the alt text for an image, another tone indicates that Aosa can press + to hear the long description.
• Brin is deaf. The video player she is using has a button displayed beneath the playing video that indicates that captions are available. She clicks the button to toggle the captions on so she can understand the video. On her mobile phone, Brin touches a video, which displays the controls including the "display caption" control.

Related Resources for Success Criterion 1.1.2:

• "HTML5 Image Description Extension (longdesc)" (http://www.w3.org/TR/html-longdesc/#longdesc)
• "User Agents and longdesc Discoverability" (http://www.d.umn.edu/~lcarlson/research/ld-ua.html)

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, media player

Intent of Success Criterion 1.1.3:

Users may wish to hide images for a number of different reasons. Some users with cognitive disabilities may wish to hide images in order to avoid those that would be severely distracting. Some users with visual disabilities may wish to hide images in order to avoid those that are painful (such as those with high contrast). Other users may wish to replace images with alternative content because they are unlikely to be able to visually discern, understand, or otherwise benefit from the images. Some users with impaired motion or dexterity may wish to replace images with smaller alternative content to reduce the amount of scrolling they have to do, while some users with attention deficit disorder may wish to do the same thing in order to keep as much information visible on the screen as possible.

Examples for Success Criterion 1.1.3:

• Tyler has a learning disability and finds images very distracting. He sets a preference in his browser to always display alternative text instead of an image.
• Ben has low vision and needs to use a very large font size to be able to read text. On his mobile device, enlarging the page makes any images so large that they use up too much screen space and require excessive scrolling. He sets a preference to render all images as text (if available) and to reflow the page so that the text flows smoothly with no space for the missing images.
• Lee has low vision where text is blurred. She finds that the transparency effect that shows detail "bleed through' under the window she is reading makes the text she is trying to read illegible. She sets a preference that hides all background images and transparency effects that the author may have written into a web page or application.
• James has a reading disability where he needs text to be clear from distractions that are not related to the text. He configures his user agent to not load background images. Then when he navigates to a web page, James gets only the text from the web page without any images interfering with what he is reading.
• Sasha requires high contrast to be able to discriminate the shape of letters. She always sets a preference in her browser to turn off background images, so that she can see the text clearly without the variations in the background.
• Matilda finds high contrast colors painful, and wants lower contrast font and background colors. She sets the default font and background colors in her operating system, which her browser picks up and uses for the default settings for web pages font and background colors.
• Betty is a low vision user and has difficulty reading text on her mobile device when it is displayed over a background image. Using her user-defined style sheet, she can disable all background images from being rendered in her browser.

Related Resources for Success Criterion 1.1.3:

• 1.4.1 Configure Rendered Text for more information related to background colors.
• 1.1.5 Configure Alternative Defaults allows the user to hide foreground images by replacing them with alternative content, but 2.10.1 extends this to background images in languages such as HTML that do not support alternative content for background images.
• CSS 2.1: section 14.2.1 The Background In CSS, background images can be turned on/off with the background and background-image properties.
• CSS 2.1: section 9.9.1 Specifying the stack level: the 'z-index' property

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

media player, web-based media players

Intent of Success Criterion 1.1.4:

Users who require or can benefit from alternative media tracks in video or audio may not find that the default or authored position and size of those tracks is usable. Enabling the user to move and scale any displayed alternate media tracks (e.g. captions) allows displayed content to be positioned and sized to meet the needs of the user.

Examples for Success Criterion 1.1.4:

• Justin has low vision and works in a noisy environment that makes it difficult to listen to instructional videos. When he enlarges the text of the captions to a viewable size, they block most of the video image. To fix this, he selects an option that displays the caption track in a separate window, which he positions below the video image so the captions don't block the video image.
• Jaime is deaf and is taking courses from on online university. She prefers to use ASL if it is available for online media. A course she is taking offers captions and a signing avatar for the recorded lectures. The default size of the avatar window is small, making it difficult to follow the signing. The avatar also overlays a significant part of the lecture video. Jaime drags the avatar out of the video and enlarges it, so that they are side by side and equally sized.
• Jaime is deaf and prefers to always display captions on her mobile phone. She has set her global settings on the phone to turn on closed captions. All videos displayed on the phone will automatically display captions.

Related Resources for Success Criterion 1.1.4:

• 1.1.6 Use Configurable Text for Time-based Media Captions

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, media player, plugin, add-on

Intent of Success Criterion 1.1.5:

Alternative content is wasted if the user agent doesn't render it for users who need it. Default alternative content is a global setting because it is an unreasonable burden for users to change the rendering options every time they visit a new page.

Examples for Success Criterion 1.1.5:

• Sally has low vision. In the browser's preferences dialog box, Sally specifies that she wants alt text displayed in place of images, and that the document reflow to allow the entire alt text to be displayed rather than truncated.
• Ben has low vision. In the browser's preferences dialog box, he chooses to always display the alternative ("fallback") content for embedded objects, such as a transcript in place of a video.
• Ben has low vision and keeps his mobile phone browser "zoomed" so he can read the text. Because images can become pixelated when enlarged, he prefers the alternative text. In the mobile settings dialog box, he chooses to always display the alternative ("fallback") content for images and to reflow the page without a placeholder for the image. This saves screen space and reduces the amount of scrolling he has to do.
• Brin is deaf. She toggles a menu item which turns on the display of all captions for video and audio content.

Related Resources for Success Criterion 1.1.5:

• Success criterion 1.1.5 adds additional required options to success criterion 1.1.3 Replace Non-Text Content.

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

media player, web-based media players

Intent of Success Criterion 1.1.6:

Users who require or can benefit from alternative media tracks in video or audio might find that recognized text displayed within alternate media tracks is unusable due to its configuration. Enabling the user to configure alternate media tracks (e.g. changing caption font and color) allows content to be displayed in a way that meets the needs of the user.

Examples for Success Criterion 1.1.6:

• Ben has low vision that becomes worse throughout the day as he becomes more tired. He keeps a floating control on his mobile phone that allows one touch access to his configuration so that he can change the font size. The floating control can be easily moved around the screen so it is not in the way of other controls, and it becomes translucent after it is idle for a few seconds.

Related Resources for Success Criterion 1.1.6:

• 1.4.1 Configure Rendered Text

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

media player, web-based media players

Intent of Success Criterion 1.1.7:

Users can want to reposition the alternative in close proximity to the most important portion of the main media to reduce the visual scanning distance between them. For example, if the video frequently includes on-screen text near the top of the video then the captions will be easier to read if they are located above the video.

Examples for Success Criterion 1.1.7:

• Maximilian is hard of hearing and prefers to use captions. He adjusts the position of his captions depending on what he's watching. When watching a sporting event with a dashboard displaying statistics at the top, he positions the captions immediately above the top so the captions are close to the statistics. However, when he watches a movie, he positions the captions so that they overlap the video frame near the bottom. When he watches financial news with a stock ticker along the bottom, he moves the captions to be immediately below the ticker.
• Raymond has one functioning hand. He positions captions so that they're not covered by the hand he's using to hold his tablet.
• Tom is deaf. When Tom watches narrow-aspect video on a wide-aspect screen or in landscape mode on his mobile device, he moves the window displaying sign language interpretation to the side, allowing the primary video to take up the entire height of the screen without the interpretation getting in the way.

Related Resources for Success Criterion 1.1.7:

• None

Applies to:

Communication with platform accessibility services

Typically Implemented in:

browser, plugin

Intent of Success Criterion 1.2.1:

When alternative content is missing, it can be helpful for users to access metadata such as the filename, but not to have it be substituted as repair text for the missing alternative text. Because the metadata is not as useful as alternative content that's properly authored for the original document, the user agent should not interfere with the assistive technology attempts to repair. The assistive technology can provide users with information that can be more helpful than any one piece of repair text the user agent could provide. Therefore it's important that assistive technology have access to as much information as possible about the non-text content that needs repair, and also to be able to inform the user that no author-provided text alternative is available. User agents should provide assistive technology with available metadata for the non-text content that needs repair, but not substitute repair text in ways assistive technology will mistake for author-provided text alternatives.

This is to avoid problems when (for example) the metadata in an image does not match the way it's being used on the current page. It allows a screen reader to distinguish between metadata provided by the page author, who knows the image's use here, vs. metadata tagging along from some long-ago source. For example, John is creating a web page that uses an image of a check mark for "Selected". He grabs a PNG file from another site, not realizing that it's embedded IPTC TITLE attribute says "You are a winner!". John is supposed to set alternative text for the image, but if he forgets to, it's better for a screen reader to say "image, unknown" than for the user agent to use inappropriate metadata substitution saying "image, You're a winner!"

Examples for Success Criterion 1.2.1:

• Ray is blind and counts on alternative text for images. When his screen reader is reading a web page and encounters an image, it asks the user agent for alternative text. If the user agent reports that no alternative text is available, the screen reader accesses the DOM to retrieve the title attribute associated with the image, its original file name, and path to the downloaded image file. The assistive technology screenreader software can then tell Ray that there is an image with no alternative text, provide him with the value it considers most likely or that Ray has selected through his preferences, then provide a command that lets him hear the other values so he can make his own judgement about the nature and purpose of the image.

Related Resources for Success Criterion 1.2.1:

• None

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

operating system, browser, plugin, add-on

Intent of Success Criterion 1.3.1:

Users need to be able to easily discover web content they can interact with. One effective way to do this is to highlight enabled elements and links (including recently visited links). Highlighted selection and content focus lets people who use keyboard, gesture and speech input know where they are working. On some pages controls can be difficult to discern amid a large amount of other content, or can be styled so the controls are difficult to distinguish from other content. This can be particularly difficult for people with visual impairments, who may not be able to distinguish subtle visual differences. People with some cognitive impairments can have difficulty distinguishing between items with similar or non-standard appearance. Visually distinguishing these items reduces the amount of time or number of commands these groups require to examine a page.

• Note 1: In addition to these required categories, it is recommended that user agents also allow the user to highlight the active viewport, even when it is a frame or similar within the active window. This makes it much easier for the user to visually locate the active focus.
• Note 2: Platform conventions will dictate whether or not keyboard focus in an inactive viewport is visually indicated by an inactive cursor.
• Note 3: the definition of visited and unvisited links is up to the user agent. Visited links can be links visited during the current session or in the browser's history.

Examples for Success Criterion 1.3.1:

• Jerry has low vision. He goes to a website that uses Cascading Style Sheets (CSS) to override visited link color. He wants to know what links have yet to be explored. The user agent provides a dialog box for setting overrides to author-selected link colors. Jerry uses the dialog box to override these so visited links are indicated.
• Jerry has low vision. He goes to a website with styles that remove the content focus outline. The user agent provides a dialog box for setting overrides to the author's focus outline declaration. Jerry uses the dialog box to display the content focus outline so he can tell where the focus is on the page.
• Binh gets easily frustrated when he cannot locate the buttons and links on a page. This happens when buttons and links don't have the standard appearance he's used to. The user agent provides a dialog box for setting overrides to author-selected link colors. Binh turns on the option to have all links appear in bright purple, and buttons drawn with a bright purple border so he can easily scan the page and find the items he's looking for.
• George has limited hand use and uses custom gestures on his mobile phone. He wants a visible focus indicator to know what element on the page has focus so when gestures are used on the mobile phone, he will know what element will be activated.
• Aosa is blind. When rendering a web page using synthesized speech, the user agent generates an audible tone to signify that the word being read is an acronym, and Aosa can press the * key to hear the expansion. When the phrase being read is the alt text for an image, another tone indicates that Aosa can press + to hear the long description.
• Brin is deaf. The video player she is using has a button displayed beneath the playing video that indicates that captions are available. She clicks the button to toggle the captions on so she can understand the video. On her mobile phone, Brin touches a video, which displays the controls including the "display caption" control.

Related Resources for Success Criterion 1.3.1:

• 1.3.2 Highlighting Options describes user options to configuring how these categories are highlighted
• 2.1.2 Keyboard Focus requires every window have an active or inactive keyboard focus at all times
• 1.8.1 Highlight Viewport provides guidance for highlighting viewports
• 1.8.2 Move Viewport to Selection and Focus provides guidance for highlighting an active window

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

operating system, browser

Intent of Success Criterion 1.3.2:

Low vision users and users with some cognitive disabilities need control over visual properties to meet their individual needs. These include foreground colors, background colors, and visual borders (with the same configurable range as the operating environment's conventional selection utilities)

Examples for Success Criterion 1.3.2:

• Alex has low vision. He sometimes has difficulty distinguishing fields on web forms. The user agent provides a dialog box allowing the user to override any author settings. He chooses to have all form fields displayed with a yellow background and outlined with a thick black border.
• Marcy has a cognitive disorder that makes it difficult to stay focused on the task she wants to accomplish. The user agent provides a dialog box allowing the user to override any author settings. She chooses to have all form fields displayed with a yellow background and outlined with a thick black border.

Related Resources for Success Criterion 1.3.2:

• CSS 2 specification – box border styles

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

operating systems, browser, plugin, add-on

Intent of Success Criterion 1.3.3:

Low vision users and users with some cognitive disabilities need control over visual properties to meet their individual needs. These include foreground colors, background colors, and visual borders (with the same configurable range as the operating environment's conventional selection utilities)

Examples for Success Criterion 1.3.3:

• Alex has low vision. He sometimes has difficulty distinguishing fields on web forms. The user agent provides a dialog box allowing the user to override any author settings. He chooses to have all form fields displayed with a yellow background and outlined with a thick black border.
• Marcy has a cognitive disorder that makes it difficult to stay focused on the task she wants to accomplish. The user agent provides a dialog box allowing the user to override any author settings. She chooses to have all form fields displayed with a yellow background and outlined with a thick black border.

Related Resources for Success Criterion 1.3.3:

• CSS 2 specification – box border styles

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, add-on

Intent of Success Criterion 1.3.4:

Low vision users and users with some cognitive disabilities need control over visual properties to meet their individual needs. These include foreground colors, background colors, and visual borders (with the same configurable range as the operating environment's conventional selection utilities)

Examples for Success Criterion 1.3.4:

• Alex has low vision. He sometimes has difficulty distinguishing fields on web forms. The user agent provides a dialog box allowing the user to override any author settings. He chooses to have all form fields displayed with a yellow background and outlined with a thick black border.
• Marcy has a cognitive disorder that makes it difficult to stay focused on the task she wants to accomplish. The user agent provides a dialog box allowing the user to override any author settings. She chooses to have all form fields displayed with a yellow background and outlined with a thick black border.

Related Resources for Success Criterion 1.3.4:

• CSS 2 specification – box border styles

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, add-on

Intent of Success Criterion 1.3.5:

Low vision users and users with some cognitive disabilities need control over visual properties to meet their individual needs. These include foreground colors, background colors, and visual borders (with the same configurable range as the operating environment's conventional selection utilities)

Examples for Success Criterion 1.3.5:

• Alex has low vision. He sometimes has difficulty distinguishing fields on web forms. The user agent provides a dialog box allowing the user to override any author settings. He chooses to have all form fields displayed with a yellow background and outlined with a thick black border.
• Marcy has a cognitive disorder that makes it difficult to stay focused on the task she wants to accomplish. The user agent provides a dialog box allowing the user to override any author settings. She chooses to have all form fields displayed with a yellow background and outlined with a thick black border.

Related Resources for Success Criterion 1.3.5:

• 1.4.1 Basic text formatting (Globally)

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

operating system, browser, add-on, web-based reader

Intent of Success Criterion 1.4.1:

Users with some types of disabilities have difficulty reading text as the author has formatted it. For example, some users with low vision, dyslexia, and related conditions and situations cannot read author-formatted text. However, they can read text that has a format customized to their individual needs (e.g. larger letters, different font, more spacing). Users with some cognitive disabilities and those who need to reduce the number of commands they enter to scroll through a document, may need to fit more information on the screen (e.g. smaller letters or spacing). Users need to access a wide range of font sizes, styles, colors, and other attributes in order to find the combination that works best for their needs. In providing preferences, it is important to avoid making assumptions. For example, some users can increase font size to make text more legible, while other users can reduce the font size to decrease the need to scroll the content.

The relative size of text provides visual cues that help in understanding and navigating web content. Some content can be authored in a way that makes it difficult or impossible to understand when font distinctions are hidden, such as headlines that are in not in a larger font than body text. It's important that users who need to enlarge or reduce text size be able to preserve these visual cues.

At a minimum, it is recommended to offer line spacing options of 1, 1.25, 1.5 and 2.0.

Examples for Success Criterion 1.4.1:

• Lee has low vision from albinism and when the background is white, it is hard for her to read and hurts her eyes. She changes the colors in her operating system to white text on a black background. However, many web pages specify their own colors, so she adjusts the user preferences in her browser to always use the system colors (or another set of colors of her choosing), regardless of how the pages are authored.
• Betty Sue has low vision from nystagmus and has difficulty seeing small fonts. The browser on her laptop provides five font sizes. However, the largest isn't big enough. The browser settings provide an option to override the five font sizes with customized font range, so that Betty Sue can select the specific font size she needs.
• Mike has a reading disability. A website uses a fancy script font for the headings that he cannot understand. He uses his browser's font settings to select plain fonts that he can read.
• Ben has low vision. In the mobile settings dialog box, he chooses a large text for font size. All applications on the mobile phone display text in large font.
• Sebeeya has low vision. She finds text easiest to read at 16 pt Palatino and chooses to have her browser display body text in the 16 pt Palatino font. She needs the headlines to scale proportionally (e.g. 24 pt) in order to preserve headline prominence.

Related Resources for Success Criterion 1.4.1:

• Guideline 1.7 Enable Configuration of User Stylesheets
• Success Criteria 1.8.5 Allow Zoom
• Success Criteria 1.8.13 Multi-Column Text Reflow
• Success Criteria 1.8.8 Allow Viewport Resize

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, add-on, web-based reader

Intent of Success Criterion 1.4.2:

Some users with low vision, dyslexia, and related conditions and situations cannot read normally-formatted text. However, they can read text that has a format customized to their individual needs (e.g. larger letters, different font, more spacing). Users need to access a wide range of font sizes, styles, colors, and other attributes in order to find the combination that works best for their needs. In providing preferences, it is important to avoid making assumptions. For example, some users can increase font size to make text more legible, while other users can reduce the font size to decrease the need to scroll the content.

Users who need large amount of screen magnification need to control the appearance of types of elements. For instance, a magnification of 300% can make headlines too large for display. Users need to be able to set the characteristics of element types (e.g. heading 1, heading 2, table heading) to make the web content readable. Magnification users who find that text size distinction greatly increases scrolling and fatigue also need to be able to display important elements such as headings (including table headings) and input fields independently from global settings.

Many users with low vision have difficulty reading italic and underline and must be able to globally remove these styles. This can be accomplished with user stylesheets, but if the browser doesn't support user stylesheets, the browser needs to provide this ability through settings. Bold characters can "bleed" when characters are too close together which reduces readability for some.

User stylesheets can be used where available. Users can control characteristics by element type, so that, for example, headings at the same level will have a similar appearance.

Examples for Success Criterion 1.4.2:

• Tomas has low vision and uses a screen magnifier. He chooses to have his browser display all text the same size, and sets that size as large as he can without making the letters too tall for his screen. Tomas chooses not to have headings be proportionately larger than normal text because that would make them taller than his screen and so unreadable. He uses a user stylesheet to make the different levels of headings a different color. He makes the table headings bold so they stand out from the table text without significantly increasing the size.
• Adele is 84 and has macular degeneration and is experiencing fine motor problems. She loves using her mobile tablet to read her email and follow her grandchildren on social media. She has difficulty selecting text areas to enter forms. Her granddaughter helps her create a font size setting for input fields so that the text is larger and increases the area where she can tap, making it easier to enter text.
• Wade has low vision and needs large text, extra line spacing, italics changed to regular font, and a muted background color in order to read. To make web pages readable, Wade uses a user stylesheet to change the way the headings are displayed. He makes the headings a little smaller than the main text, changes the font to Arial and red, adds space before and after the headings, and adds border above the headings. This ensures that headings aren't too big, navigation links don't break across lines as much, and a reasonable amount of text is visible at a time, so Wade doesn't have to do extra scrolling. By changing the heading elements to have a different appearance from the main text, Wade can easily distinguish headings without them being them too large.

Related Resources for Success Criterion 1.4.2:

• Guideline 1.3 Provide highlighting for selection, keyboard focus, enabled elements, visited links
• Guideline 1.7 Enable Configuration of User Stylesheets
• Success Criteria 1.8.5 Allow Zoom
• Success Criteria 1.8.13 Multi-Column Text Reflow
• Success Criteria 1.8.8 Allow Viewport Resize

Applies to:

UA user interface, Content user interface, Configuration settings

Typically Implemented in:

browser, reader

Intent of Success Criterion 1.4.5:

Some people find that it easier to read when text is displayed using a specific set of attributes, such as font, size, text and background colors, or spacing. While some requirements are most common (such as larger text), the combination that works best will vary from one individual to the next. They will typically want these setting applied to both user interfaces and rendered content. On many platforms the user can adjust platform preference settings to meet their needs, and these settings are available to applications such as user agents. Each applications can then provide a simple user option to follow those settings, rather than make the user repeat the configuration process in every application. Likewise it means that if their needs change, or they discover settings that work better for them, they can make that change in one place rather than repeating it over and over again. This also makes it easier for the user to maintain a consistent presentation across all their applications. If the user relies on these settings, they can instruct the user agent to override author-specified text attributes (per other success criteria in Guideline 1.4).

Examples for Success Criterion 1.4.5:

• Lee has low vision from albinism and when the background is white, it is hard for her to read and hurts her eyes. She changes the colors in her operating system to white text on a black background. However, many web pages specify their own colors, so she adjusts the user preferences in her browser to always use the system colors, regardless of how the pages are authored.
• Erin has dyslexia and finds it easiest to read sans serif text with relatively low brightness and color differences between text and its background. She changes the font and colors in her operating system’s Control Panel to work well for her. These settings are automatically reflected in her browser’s user interface. However, many web pages specify their own colors, so she adjusts the user preferences in her browser to always use the system fonts and colors, regardless of how the pages are authored.
• Sebeeya has low vision. She finds text easiest to read at 16 pt Palatino and adjusted her operating system’s preference settings to use these for its menus and other controls. She appreciates that her browser automatically respects these settings by displaying its menus and controls in this same style.

Related Resources for Success Criterion 1.4.5:

• Guideline 1.4 Provide text configuration discusses additional success criteria about options for text presentation.
• Guideline 2.6 Preference settings discusses additional success criteria about configuring preference settings.

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, add-on, web-based reader

Intent of Success Criterion 1.4.6:

Advanced features that improve readability include override of capitalization and auto-hyphenation. Some users need to turn off capitalization because words that are in all caps can be hard to read. This should not be interpreted as a requirement to provide heuristics to interpret text that has been entered in all caps into appropriate mixed case. The intent is that if all caps has been controlled by a style, the user can override that style.

Some users with low vision prefer to remove borders that may be located too close to the text and appear to bleed into the text, making it difficult to read.

Examples for Success Criterion 1.4.6:

• Lori has low vision. She is using her mobile phone to find a restaurant. The restaurant search listing puts the restaurant names in all caps, which she finds difficult to read. Lori touches the Settings button and chooses Sentence case. Since the restaurant names were originally entered in mixed case,

Related Resources for Success Criterion 1.4.6:

• 1.4.2 Text Size, Color and Font (by Element)
• 1.4.3 Text Spacing and Style (Globally)
• 1.3.1 Highlighted Items and 1.3.2 Highlighting Options for borders on input fields.
• CSS 2.1 16.5 Capitalization
• CSS 3 5.3 Breaking Rules for Letters (as of this publication, CSS 3 is not a completed W3C Recommendation and could change)
• CSS 2.1 10.8.1 Leading and half-leading
• CSS 2.1 16.5 Capitalization

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

operating system, media player, web-based player

Intent of Success Criterion 1.5.1:

User agents can render audio tracks from a variety of sources, and in some cases, multiple audio tracks can be present on a single page. Users should be able to globally set the volume of audio tracks, rather than having to adjust the volume of each audio track being played.

Examples for Success Criterion 1.5.1:

• Magdalene is very sensitive to loud noises. She uses preference settings to adjust the master audio volume control of her computer operating system that applies to all audio tracks rendered within the environment, including the user agent. This volume control setting is retained even after Magdalene shuts down her browser and turns off her computer.
• Alisha is easily distracted by audio that she does not expect. She encounters a webpage with two advertisements and a video that begin playback when the page loads. She immediately silences the playing audio tracks by clicking a mute key on her keyboard that invokes a global mute command.

Related Resources for Success Criterion 1.5.1:

• None

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

operating system, self-voicing browser, add-on

Intent of Success Criteria 1.6.1 and 1.6.2:

These success criteria allow users to control speech characteristics so they can perceive and understand the audio information.

For example, a user may need to increase the volume to a level within the user's range of perception. Or a user may increase the rate of synthesized speech presentation because the user understands it at a rate faster than the default setting of the user agent.

Success criterion 1.6.1 covers characteristics that users most commonly need to adjust and that are adjustable in most technologies. Success criterion 1.6.2 covers characteristics that are less widely altered and less widely supported.

Examples for Success Criteria 1.6.1 and 1.6.2:

• Jamie is blind. He uses a mobile-based web browser to read a web page. He presses a key to increase the rate at which the information is read back. He also uses a mobile browser in noisy environments such as a crowded subway. With a key press, Jamie quickly increases the volume.
• Randy has a hearing disability where speech at lower pitches is difficult to hear. He is using an audio browser that reads web pages back to him. He issues a voice command saying "raise pitch" and the overall pitch of the synthetic speech is raised.

Related Resources for Success Criteria 1.6.1 and 1.6.2:

• None

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

operating system, self-voicing browser, add-on

Intent of Success Criterion 1.6.3:

The synthetic speech presentation of text can be difficult to understand. These success criteria improve understandability by giving the user the ability to adjust the way the speech synthesizer presents text.

Examples for Success Criterion 1.6.3:

• Penny has a reading disability. She is using a browser that reads web pages to her so she can review her most recent banking transactions. She has configured her browser to speak currency instead of digits. With this setting she hears a transaction as "Deposit, two hundred fifty five dollars".
• Penny has a reading disability. Her speech synthesizer is repeating a phone number. She wishes to copy this number, so she switches to the mode where each digit is spoken as a unique word (e.g. five, five, five, seven, nine).
• George is blind. His speech synthesizer incorrectly pronounces technical terms employed in his organization. The terms are consistently mispronounced in a way that makes it difficult for George to distinguish them. A dictionary allows George to enter a spelling of the name that causes the synthetic speech to produce the correct pronunciation.

Related Resources for Success Criterion 1.6.3:

• None

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

operating system, self-voicing browser, add-on

Intent of Success Criterion 1.6.4:

Synthesized speech users who are multi-lingual need to be able to respond to changing content by quickly changing the language of the speech synthesizer, overriding any values specified by the author or inferences made by the user agent. Much web content lacks the appropriate language indication or has an incorrect language attribute, and the user agent may not be able to accurately determine the language from the text, so that the user needs a convenient mechanism to change the language.

Examples for Success Criterion 1.6.4:

• Hosea is blind. He speaks Spanish but his instructors only speak English. Hosea keeps a floating control on his mobile device that allows one-touch access to his configuration so he can quickly change the language the speech synthesizer reads. He is reading class-related material on the internet in Spanish, but must refer to an explanatory reference link in English. Because the reference link isn't properly coded with a language attribute, his speech synthesizer doesn't recognize the language change. Hosea uses the floating control to quickly switch to English for the reference, then back to Spanish when he returns to the main article he was reading.

Related Resources for Success Criterion 1.6.4:

• W3C Internationalization resources

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

operating system, self-voicing browser, add-on

Intent of Success Criteria 1.6.5:

These success criteria allow users to control speech characteristics so they can perceive and understand the audio information.

For example, a user may need to increase the volume to a level within the user's range of perception. Or a user may increase the rate of synthesized speech presentation because the user understands it at a rate faster than the default setting of the user agent.

Success criterion 1.6.1 covers characteristics that users most commonly need to adjust and that are adjustable in most technologies. Success criterion 1.6.2 covers characteristics that are less widely altered and less widely supported.

Examples for Success Criteria 1.6.5:

• Jamie is blind. He uses a mobile-based web browser to read a web page. He presses a key to increase the rate at which the information is read back. He also uses a mobile browser in noisy environments such as a crowded subway. With a key press, Jamie quickly increases the volume.
• Randy has a hearing disability where speech at lower pitches is difficult to hear. He is using an audio browser that reads web pages back to him. He issues a voice command saying "raise pitch" and the overall pitch of the synthetic speech is raised.

Related Resources for Success Criteria 1.6.5:

• None

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, add-on

Intent of Success Criteria 1.7.1, 1.7.2, and 1.7.3:

Mechanisms exist to allow users and authors to customize the rendering of web content (e.g. CSS stylesheets). Such customization is frequently used to make web content accessible to a wide range of user needs. These success criteria ensure that users can take full advantage of this ability to customize stylesheets. Since different websites may require different style changes to be readable, it is recommended that user agents provide a feature that lets the user specify which stylesheet should be automatically applied to different web pages as they are loaded (e.g. based on a list of domain names or URL templates).

Examples for Success Criteria 1.7.1, 1.7.2, and 1.7.3:

• Tanya has low vision. She finds yellow text on a black background easiest to read. When a website loads, the user agent provides a menu that allows Tanya to select among several stylesheets that the web author has created for the website. Tanya selects the "yellow on black" stylesheet from the menu. The web content is then rendered using this stylesheet.
• Kendra has low vision. She has changed a website that is normally in full color to yellow text on a black background. When her husband Jeromy sits at her computer to look at the site, he goes to the user agent menu to quickly de-select the user-defined stylesheet that Tanya previously applied to the web page. The website is now rendered in full color.
• Lee has low vision and finds text easiest to read on her mobile device when it is presented in yellow on a black background. She has configured her browser to override the author stylesheets to always display text in her browser using this color scheme.
• Mattias has attention deficit hyperactivity disorder (ADHD) and finds text easiest to read if text is highlighted in blue as it is being read out loud on his desktop or mobile device. Both the highlight and text color are configurable and override the author stylesheets so text is readable and has sufficient color contrast.

Related Resources for Success Criteria 1.7.1, 1.7.2 and 1.7.3:

• CSS 2 Recommendation: cascade weight rules
• Custom Styles for iOS
• Stylish for FF and Chrome
• Web Developer for Firefox and Chrome

Applies to:

UA user interface

Typically Implemented in:

browser, add-on

Intent of Success Criterion 1.7.4:

Stylesheets provide for powerful customization of rendered content. Occasionally a user may need to make slight modifications to the author-supplied external stylesheets used on a website to satisfy certain accessibility needs. At other times a web author may have created a stylesheet that a user with a disability finds helpful. The intent of this success criteria is to allow users to easily save the stylesheet for a website and make needed modifications without having to create full stylesheet of their own and to apply well designed stylesheets to other web pages where they find the stylesheets helpful. While it is customary for authors to compress stylesheets and scripts to save load time, it would be highly beneficial if the user agent saved the stylesheets in a format that facilitates reading and editing by users (e.g. without stripping out line breaks).

Stylesheets can be difficult to make sense of. UAAG realizes that most users will want to use a tool to read and edit the stylesheet. It is recommended that tools or add-ons are supported for making stylesheets easier to use for less technical users. Many low vision users require custom stylesheets for accessibility and better support for user stylesheets will improve the browsing experience for these users.

Examples for Success Criterion 1.7.4:

• Mikki browses to a new website and discovers that the Arial 14-point type used for all headlines does not work well with her level of vision. A friend helps Mikki discover that the headlines are created with a CSS stylesheet. They save this stylesheet and study how it is created. Mikki modifies this stylesheet to adjust the headline text to a larger font and a different typeface. She uses the modified stylesheet by applying it as a user style sheet.
• Tanya has low vision. She browses to a new website on her mobile phone and finds that the site is not optimized for mobile devices. She alters the stylesheet to provide better layout and larger fonts. The custom settings for the stylesheet are saved and applied when she returns.

Related Resources for Success Criterion 1.7.4:

• None

Applies to:

UA user interface, Content user interface, Configuration settings (optional)

Typically Implemented in:

operating system, browser

Intent of Success Criterion 1.8.1:

When a user agent presents content using multiple viewports, users benefit from a clear indication of which viewport has focus. Text foreground and background colors may not provide enough indication of viewport focus for users with low vision.

Examples for Success Criterion 1.8.1:

• Tanya has low vision. Her favorite music website allows her to select which of the top 10 songs are available for listening. Each song is represented by a thumbnail of the album cover – a graphical viewport containing a music player. Tanya uses a keyboard-based screen magnification tool to tab between songs. This highlights the currently selected player with a thick, yellow border against a dark gray background.

Related Resources for Success Criterion 1.8.1:

• 1.8.7 Customize Viewport Highlighting

Applies to:

Content user interface

Typically Implemented in:

browser

Intent of Success Criterion 1.8.2:

When content extends horizontally or vertically beyond the visible bounds of its viewport, users must be able to move to one or more selectable elements that may be out of view and to have the selected content automatically move into view. This gives keyboard users and screen magnification users an efficient means to view selected content without having to scroll to locate and view the selection.

Examples for Success Criterion 1.8.2:

• John has low vision and uses a screen magnifier. He is spellchecking his blog, which is contained within a scrollable viewport. The blog text exceeds the vertical size of the viewport. The blogging software provides a command to move to the first, and then any subsequent, unrecognized words. With two unrecognized words in the posting, John ignores the first selected word, and presses the key to move to the next unrecognized word, which is out of view. As the key is pressed, the viewport scrolls to show the selected word.
• George uses a screen reader. He is showing a sighted colleague how to complete a registration form that's contained within a viewport. The form exceeds the vertical bounds of the viewport. When George completes each form entry, if the next form is not already visible in the viewport, it scrolls into view.
• Taja typically views web content on her mobile phone at a high level of zoom. This can frequently position elements outside the viewport, requiring scrolling. When moving between focusable elements, the user agent viewport automatically scrolls to the element currently in focus.

Related Resources for Success Criterion 1.8.2:

• 1.8.6 Maintain point of regard

Applies to:

Content user interface, Configuration settings (optional)

Typically Implemented in:

browser, media player, plugin, web-based user agent (readers, players)

Intent of Success Criterion 1.8.3:

When rendered content exceeds the bounds of a graphical viewport, horizontal or vertical scrollbars show that not all of the rendered content is currently visible within the viewport and provide a means of navigation to that content. The scrollbars make it clear that the rendered content is not fully visible.

Examples for Success Criterion 1.8.3:

• Tanya has low vision. She is reading a recipe on a website with a fixed size popup window. Tanya has set a preference in her browser to override the author setting and always display scrollbars on content overflow. She increases the font size causing the recipe to exceed the vertical and horizontal dimension of the viewport. The presence of the scrollbar shows her that additional ingredients may be present. She uses the scrollbar to move them into view.
• Terry has memory issues. She configures her mobile computer so that scrollbars are always on so she can instantly see where she is in a document.

Related Resources for Success Criterion 1.8.3:

• None

Applies to:

Content user interface

Typically Implemented in:

browser, media player, plugin, add-on, web-based user agent (readers, players)

Intent of Success Criterion 1.8.4:

Users who have fine-motor problems that make it difficult to scroll, users who have cognitive issues that make it difficult to orient on the page, and screen reader users, who rely on audio to scan the page, all need to quickly assess the amount of content on the page and where they are located within the content.

Examples for Success Criterion 1.8.4:

• Ally has cognitive issues that make it difficult to orient. She navigates to a lengthy web page and begins paging through the content. A scroll bar indicates her position within the content as she pages and shows that with each paging action only a small portion of the content is rendered.
• Ally has cognitive issues that make it difficult to orient. When looking at a map on her mobile device, she must frequently zoom in to view her current location or destination and zoom out to put the location into the context of the large map.
• George uses a screenreader to access a lengthy web page. His screen reader speaks the percentage that the page is scrolled, allowing George to know where the cursor is relative to the entire page.

Related Resources for Success Criterion 1.8.4:

• None

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, plugin

Intent of Success Criterion 1.8.5:

Some users want to be able to magnify content to so it is more legible. Some users  want to be able to shrink content so that more of it is visible onscreen. This can help them understand the structure of the content and their position in  the content, even if text has become too small to read. The commonly needed range is between 150-400%. A user agent could provide 6 steps in that range, or let the user set their own exact percentage.

Examples for Success Criterion 1.8.5:

• Tanya has low vision and needs large text. On web pages where graphics are strictly decorative, she increases the text size and leaves the graphics small. If she is using a web application with important graphics, however, both the graphics and the text need to be bigger, so she uses the zoom page feature.
• Alexandra has low vision. When she views a website on her mobile phone, she first scans the website at a very small size to guess where she wants to zoom in first. The zoom feature increases the size of both text and images.
• Perttu has a learning disability. He is studying an organization chart but has difficulty maintaining a mental representation of the organizational linkages for items out of view. In order to facilitate his understanding of the organization, Perttu zooms out to allow the entire chart to be displayed.

Related Resources for Success Criterion 1.8.5:

• 1.8.9 Allow Viewport Resize
• 1.8.6 Maintain point of regard

Applies to:

Content user interface

Typically Implemented in:

browser, plugin

Intent of Success Criterion 1.8.6:

Users can be confused and disoriented when the area where they are working suddenly shifts outside the visible region of the viewport. When this happens, users may have to expend considerable time and effort to re-navigate back to their previous point of regard. Just as the location in audio does not change when the user increases the volume, the point of regard should not change when the user changes the size of the window or zooms the content.

The point of regard is the information within the viewport that is visible to the user. When there is focused or selected content inside a viewport, and the viewport is resized, or content is zoomed, scaled, or formatted differently, that content will remain visible in the viewport. Otherwise, the user agent should maintain the same top-left (top-right for text read right-to-left) corner as the initial viewport.

Note: User agents are encouraged to allow user to override author instructions not to wrap content (e.g. nowrap).

Examples for Success Criterion 1.8.6:

• Jorge has low vision. While viewing a web page he sees a picture with a caption that is too small to read. He highlights the caption, then uses the browser's zoom feature to increase the size of the content so he can read the caption. Throughout the zooming process the highlighted caption remains in the viewport, allowing Jorge to keep oriented on the caption and begin reading it when the appropriate content size is reached. Later, while reading on a page, Jorge finds some text that's too large to read. The beginning of the large text is at the top of the browser content area. Jorge uses the zoom feature to make the content smaller. The text is reduced to a comfortable reading size and the beginning of the text remains at the top of the browser window.
• Melissa has a distraction disorder. She is doing research for school. She scrolls the content so the relevant section heading is the top line of the browser. She resizes the browser so she can see her notes and the browser at the same time. After resizing the browser the heading is still the top line.
• Xu has a reading disability. He is reading a page with footnotes that are too small to read on his mobile device. Xu places the footnote at the top of the browser, and using the increase font-size feature, he increases the font-size of the text on the page. The footnotes stay on the top of the viewport.

Related Resources for Success Criterion 1.8.6:

• 1.8.2 Move Viewport to Selection and Focus

Applies to:

UA user interface, Content user interface, Configuration settings

Typically Implemented in:

operating system, browser, plugin, add-on

Intent of Success Criterion 1.8.7:

When a user agent presents content in multiple viewports, users benefit from a clear indication of which viewport has focus. Text foreground and background colors may not provide enough indication of viewport focus for users with low vision. These users need to customize viewport frames using color, contrast, and border thickness to provide multiple visual highlighting cues.

Examples for Success Criterion 1.8.7:

• Tanya has low vision. She tabs through the open windows on her new browser, but can't determine which viewport is the active viewport. She opens the browser settings and customizes the viewport frame in bright yellow with a thick black border so it's easier to see.

Related Resources for Success Criterion 1.8.7:

• 1.8.1 Highlight Viewport

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player

Intent of Success Criterion 1.8.8:

If a viewport contains content that exceeds the dimensions of the viewport, users can increase the size of the viewport – up to the limits of the physical display screen – to allow the content to be displayed without horizontal scrolling. This benefits keyboard users who may find it difficult to scroll content. Other users with cognitive or learning disabilities may improve their ability to read the text by making the viewport narrower, and thus shortening the line lengths.

Examples for Success Criterion 1.8.8:

• Perttu has a learning disability. He is studying an organization chart and has difficulty maintaining a mental representation of the organizational linkages for items out of view. In order to facilitate his understanding of the organization, he sizes the viewport to allow the entire chart to be displayed.
• Vaalu has tunnel vision and can only see a few words at a time. If blocks of text are in long lines, it is difficult for him to get from the end of one line to the beginning of the next line. He often makes the viewport narrower and rewraps the text so the text is in shorter lines.

Related Resources for Success Criterion 1.8.8:

• W3C: Fullscreen (not complete at this writing)

Applies to:

UA user interface, Content user interface, Configuration settings

Typically Implemented in:

browser

Intent of Success Criteria 1.8.9, 1.8.10 & 1.8.11:

Unexpected focus and viewport changes can be disorienting for all users, requiring time and effort for the user to orient to the change. These success criteria are intended to allow the user to be in control of when viewport changes happen so the user can orient to the changes in a predictable fashion.

Examples for Success Criteria 1.8.9, 1.8.10 & 1.8.11:

• Justin has an attention deficit disorder. He is studying an online college course and finds a word that he doesn't know. He follows a link to the definition of the word. After reading the definition, he uses the back button (viewport history) to return. The word remains selected so he doesn't have to reorient or find it on the page.
• George uses a screen reader. He visits a web page that ordinarily opens a popup page. George receives an audio alert that additional content is available. He can choose to have this pop-up content open on request.
• John has low vision and uses a screen magnifier to access his browser. He configures his browser so popup windows do not take focus because the pop-ups can open outside the view of his magnifier.
• Frank has repetitive strain injuries and uses speech input. He configures his browser so that pop-ups always take focus, so he doesn't have to take multiple steps to locate the window and take the desired action.
• Ray is blind. His mobile device automatically opens location links and calendar dates found on web pages in native apps available on the device. When he returns to the browser, focus on the original link is maintained.

Related Resources for Success Criteria 1.8.9, 1.8.10 & 1.8.11:

• 3.3.1 Avoid unpredictable focus
• 3.1.5 Back button

Applies to:

UA user interface, Content user interface, Configuration settings

Typically Implemented in:

browser

Intent of Success Criterion 1.8.12:

Users orient themselves to a browsing environment with a variety of techniques. This success criteria is designed to ensure that the user does not have to learn multiple strategies to use the browsing viewport.

Examples for Success Criterion 1.8.12:

• Robert has low vision. He uses magnification software. After setting up his user agent, he knows that web content begins predictably one inch from the top of the window, so he can configure his magnification software to present content starting at that location.
• Courtney has difficulty understanding and using complex user interfaces. She has worked with her sister to set up her browser to have only a few of the most common browser controls displayed and she knows to expect them on every browser window.

Related Resources for Success Criterion 1.8.12:

• 2.6.3 Multiple Sets of Preference Settings

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, plugin, add-on, web-based readers

Intent of Success Criterion 1.8.13:

Keeping oriented within multi-column content can be challenging for some users, especially when content is zoomed. This is an especially acute issue for users who find it difficult or impossible to use the mouse to scroll and for users who find it difficult to reorient when the content changes. This does not require or prohibit the user agent from providing an option to turn off reflow. Success criteria 1.8.13 through 1.8.15 work together to allow users to work with enlarged text without having to scroll horizontally

Examples for Success Criterion 1.8.13:

• Frank has repetitive strain injuries and uses speech input. When Frank uses his mobile phone to read a web page, he needs to zoom in to read an article on a web site. He configures his mobile phone so that text reflows to always display zoomed content to fit in one column.

Related Resources for Success Criterion 1.8.13:

• 1.4.4 Configured and Reflowed Text Printing
• 1.8.14 Ignore Absolute Layout Dimensions
• 1.8.15 Linearize Content

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, add-on

Intent of Success Criterion 1.8.14:

Content is not as easily usable if the user has to scroll back and forth horizontally. This is an especially acute issue for users who find it difficult or impossible to use the mouse to scroll and for users who find it difficult to reorient when the content changes. Most user agents default to wrapping content within the horizontal dimensions of the top-level viewport unless authors specify absolute layout dimensions that necessitate extending the content beyond the width of the viewport. This success criteria gives users the option to check how the content would appear without those author-specified absolute layout dimensions. Success criteria 1.8.13 through 1.8.15 work together to allow users to work with enlarged text without having to scroll horizontally

Examples for Success Criterion 1.8.14:

• Maggie has cognitive issues that make it difficult for her to reorient when the computer screen changes. Finding and activating scrollbars, then finding the next words in the sentence requires extra effort and causes Maggie to lose her orientation, which degrades her reading flow and comprehension. When text is reflowed so it is in one column that doesn't require horizontal scrolling or vertical scrolling to get to another column, she can read and understand it.

Related Resources for Success Criterion 1.8.14:

• 1.4.4 Configured and Reflowed Text Printing
• 1.8.13 Multi-Column Text Reflow
• 1.8.15 Linearize Content

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, plugin, add-on

Intent of Success Criterion 1.8.15:

In some cases, author-specified layouts (e.g. such as layout tables, layouts that must be scrolled, etc.), can impede access, especially when content is zoomed. This is an especially acute issue for users who find it difficult or impossible to use the mouse to scroll and for users who find it difficult to reorient when the content changes. Success criteria 1.8.13 through 1.8.15 work together to allow users to work with enlarged text without having to scroll horizontally

Examples for Success Criterion 1.8.15:

• Ansgard has low vision and physical disabilities that make it difficult to use the mouse. He needs to zoom in to read text. When using his PDF viewer, he makes use of the zoom and single column reflow features to reflow the content into a single column that fits the window.

Related Resources for Success Criterion 1.8.15:

• 1.4.4 Configured and Reflowed Text Printing
• 1.8.13 Multi-Column Text Reflow
• 1.8.15 Ignore Absolute Layout Dimensions

Applies to:

UA user interface, Content user interface, Configuration settings (optional)

Typically Implemented in:

browser, add-on, web-based readers

Intent of Success Criterion 1.8.16:

This success criterion is crucial for users who have trouble navigating a web page. People who use speech input, have memory problems, or use small screens may be able to go from one area of a web page to another area once or twice, but may have trouble frequently repeating the action. The ability to mark areas of the page allows these types of users to navigate more quickly with less fatigue.

Examples for Success Criterion 1.8.16:

• Jamie is a quadriplegic who uses speech input. She is a professor who reads long documents online and often finds herself comparing different portions of the same document. It is tedious carrying out multiple scrolling commands by speech every time she needs to change to another portion of the document. She sets several bookmarks instead. This allows her to instantly jump among sections, eliminating the time and effort penalties she usually has to pay for slow scrolling. Jamie also uses bookmarks on her mobile phone to cut down on scrolling.
• Julie has memory problems. She finds it difficult to remember key points from a document she has just read. She uses bookmarks to mark important points she needs to read again. Without the ability to bookmark, she won't remember what she needs to read multiple times in order to do so.
• George is blind and occasionally travels to unfamiliar places for work. He sometimes uses an smart phone to orient himself within a map of the building he's in. Once he's found a key place on the map – a room where a conference session is held, or the bathroom – he bookmarks it to build a map of useful places. This makes navigation easier the second time around. He sets the marks to be persistent across sessions so next time he visits he won't have to repeat his work.
• Mary has repetitive strain injuries that make it painful to use a mouse. She is a college professor who uses an elaborate web application to correct papers. After putting a comment in a comment field she has to scroll all the way to the bottom of the document to enter the comment. The bookmarks make even this badly designed application something she can use successfully without hurting herself.

Related Resources for Success Criterion 1.8.16:

• None

Applies to:

UA user interface

Typically Implemented in:

browser, add-on, web-based readers

Intent of Success Criterion 1.9.1:

Outline views allow users to get a simplified view or overview of a document. They are particularly useful for users with memory or cognitive disabilities, blind users, and users who find it difficult or impossible to use a mouse. A navigable outline views reduce orientation and navigation time and fatigue.

Examples for Success Criterion 1.9.1:

• Frank has repetitive strain injuries and uses speech input. He uses a web browser to read financial information. His browser provides an optional panel displaying a hierarchical list of the headers and tables in the current document. Frank is able to expand or shrink portions of the outline view for faster access to the information he wants.
• George uses a screen reader. He reads long standards documents and uses the headings to navigate quickly so he can compare sections of the standards. George also finds the outline view useful when he is quickly checking a reference on his mobile phone.

Related Resources for Success Criterion 1.9.1:

• Guideline 2.5 Provide structural navigation
• Success Criterion 2.3.1 Direct Navigation to Important Elements
• ARIA Landmark Roles

Applies to:

UA user interface

Typically Implemented in:

browser

Intent of Success Criterion 1.9.2:

The source view is the ultimate fallback for a person with disabilities when the browser cannot properly render some content, or when the user cannot take advantage of the content as rendered or using the mechanisms provided.

Examples for Success Criterion 1.9.2:

• George is a web developer who uses a screenreader. He visits a web page where the content author failed to provide alt text or a long description for an image he wants to access. As a last resort, George examines the source to see the image's URI, class, and similar attributes. He sees that part of the URI for the image is "home.jpg" and concludes that he can click on that image to return to the home page of the site. George also uses the source view feature on his mobile device when he needs to identify an image.
• Mikki has low vision. She wants to create a user stylesheet for her web-based email program. She examines the source code to identify the CSS class of the email heading. She then creates a user stylesheet that increases the size and contrast of the email headings.

Related Resources for Success Criterion 1.9.2:

• None

Applies to:

Content user interface

Typically Implemented in:

browser, add-on

Intent of Success Criterion 1.10.1:

Some users have difficulty perceiving, remembering, or understanding the relationships between elements and their descriptions. Certain elements relate to others in defined semantic relationships (e.g. HTML label element, figcaption, table heading to table cell, and aria-labelledby attributes). This allows users to better understand these relationships even if the elements are not adjacent on the screen or the DOM.

Examples for Success Criterion 1.10.1:

• John has low vision. When interacting with tables and spreadsheets John has to move the viewport of the magnifier to understand the row and column titles of the cell with which he is interacting. This takes additional time and effort and is therefore frustrating. John switches to a browser that presents the row and column titles when he hovers over a cell. This makes him much more productive at his accounting job.
• Courtney has a cognitive disability that makes it difficult for her to comprehend complex user interfaces. She is completing an online job application. It is not clear where she should enter her phone number, because the input fields have text labels above, below, and to the left of the current input field. She mouses over the blank box and sees a tooltip that says "home phone number". She is able to complete the form.

Related Resources for Success Criterion 1.10.1:

• 4.1.2 Expose Basic Properties
• WAI-ARIA: 6.5.4 Relationship Attributes
• WAI-ARIA Authoring Practices: 4. Relationships

Applies to:

UA user interface

Typically Implemented in:

browser, add-on

Intent of Success Criterion 1.10.2:

Users who have difficulty working with a web page or document can use user stylesheets or scripts to modify page presentation or interaction so they can gain information or accomplish a task. Stylesheets and scripts may require the user to identify specific elements, element attributes, and element position in the hierarchy. The user agent can facilitate this process by allowing the user to navigate to an element, select it if it's not navigable, and query for element information. If this feature is not provided, the user may be forced to try to find the corresponding element in the source view or entire document tree.

Examples for Success Criterion 1.10.2:

• Jack has low vision and uses user stylesheets frequently. He wants certain content on a web page to be displayed in a larger font, and wants to create a user style sheet that would modify its appearance. He needs to identify the class or ID of the particular element, so he selects the text he's interested in, opens the browser's debug window, which shows him that the selected text is an element with class "story" inside a paragraph inside a DIV with class "Premiere". He then knows the combination of classes and element types to specify in the user style sheet.

Related Resources for Success Criterion 1.10.2:

• Guideline 1.7 Enable Configuration of User Stylesheets

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player, plugin, web-based user agent (readers, players)

Intent of Success Criterion 2.1.1:

A user has many ways to input information into a computer or device, including mouse, keyboard, gesture, and speech. The keyboard paradigm is the most universal interface for text input – even devices that do not have a keyboard (like mobile phones) support a software interface for them. A user should be able to navigate, read and use all of the web page or application without needing to use a mouse. Some users do not use a mouse. Others can only use a pointing device that uses the keyboard API. It's important that these users be able to interact with enabled components, select content, navigate viewports, configure the user agent, access documentation, install the user agent, and operate user interface controls, all entirely through keyboard input. User agents generally support at least three types of keyboard operation:

1. Direct (e.g. keyboard shortcuts such a "F1" to open the help menu; see checkpoint 11.4 for single-key access requirements)
2. Sequential (e.g. navigation through cascading menus)
3. Spatial (e.g. when the keyboard is used to move the pointing device in two-dimensional visual space to manipulate a bitmap image)

User agents should support direct or sequential keyboard operation for all functions. The user agent should offer a combination of keyboard-operable user interface controls (e.g. keyboard operable print menus and settings) and direct keyboard shortcuts (e.g. to print the current page).

Examples for Success Criterion 2.1.1:

• Amal has a medical condition that prevents him from using the mouse. Jeremy finds it difficult or impossible to use a mouse or keyboard and therefore uses speech to control the keyboard. Tanya is blind and uses a screenreader and must be able to accomplish all tasks with the keyboard. Jamie uses a switch device to control the computer. Each of these users must be able to do the following through keyboard alone, speech input alone, or switch device alone:
  • Select content and operate on it. For example, if it is possible to select rendered text with the mouse and make it the content of a new link by pushing a button, these users also need to be able to do so through the keyboard and other supported devices. Other examples include cut, copy, and paste.
  • Set the focus on viewports and on enabled elements.
  • Install, configure, uninstall, and update the user agent software.
  • Use the graphical user interface menus even though they cannot use the mouse (Amal, Jeremy and Jamie).
  • Fill out forms.
  • Access documentation.
• Amal has a medical condition that prevents him from using the mouse. He is reading a web page where the author used the CSS overflow property to constrain the size of a block of content. Amal's browser provides scroll bars to display text that overflows the viewport. He uses the keyboard to enter the element and operate the scrollbars to read all the content, he then uses the keyboard to return focus to the main web page. (see 2.1.3 No Keyboard Trap)
• Tanya is blind and uses a screen reader. She needs to use a volume control widget to change the volume on a video she is watching. She use the keyboard to navigate to the widget, uses the arrow keys to increase the volume, then uses the keyboard to navigate to the comments below the video player.
• Cade has low vision. He can't identify an icon and so he needs to read its alternative text. Mouse users could hover the mouse over the icon and have its alternative text displayed as a pop-up or tooltip, but Cade cannot use a mouse. He uses the keyboard to move focus to the icon. The browser automatically displays the "hover" tooltip, or allows him to press a key to have it displayed.
• Jeremy is a speech-input user who cannot use his hands to control his computer. It is much easier for him to speak keyboard shortcuts then click on an icon in a new program. He needs to be able to see tooltips to discover keyboard shortcuts without having to use the mouse.
• Karen has muscular dystrophy and cannot easily use the onscreen keyboard to navigate web pages on her mobile phone. Instead, she uses simple gestures to move between elements on the page. As focus moves from one element to another, there is a visible focus indicator.

Related Resources for Success Criterion 2.1.1:

• Modality Independent Controls
• 2.1.3 No Keyboard Trap

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player, plugin

Intent of Success Criterion 2.1.2:

Both the user and some types of assistive technology need to know what will be affected by any keyboard input, so it's important that they be able to tell which window, viewport, and controls have the keyboard focus at any time. This applies whether window and viewport are active (active keyboard focus) or inactive (inactive keyboard focus). Even when a window is inactive, it can be affected by simulated keyboard input sent by assistive technology tools. Active keyboard focus is indicated to the user by focus cursors and text cursors, as required by Guidelines 1.3, and made available to assistive technology, as required by Success Criterion 4.1.2.

Examples for Success Criterion 2.1.2:

• Amal has a medical condition that prevents him from using the mouse. He launches a web browser and navigates to a web page. Initially the keyboard focus is on the entire document, which is exposed to assistive technology, but there is no visible cursor. When Amal presses the tab key, the focus moves to the first link on the web page, and a cursor in the form of a dotted rectangle appears around that link.
• Amal has a medical condition that prevents him from using the mouse. He launches a web browser and navigates to a web page that has an enabled edit field. The browser places the keyboard focus on the edit field so Amal can immediately start entering text, and its location is shown using a text cursor (usually a vertical line or I-beam). As he types, the text cursor moves to show where the next character will appear. If Amal activates another window, the browser may hide the cursor in the now inactive window, but its location is still available to assistive technology.
• Raymond has low vision. As the keyboard focus moves from one control to another, or one window to another, his screen enlarger utility detects the focus change and pans its viewport to keep the focus location visible.
• Jeremy is a speech-input user who cannot use his hands to control his tablet. He opens a web page using a speech command. The web page has a search field, and normally comes up with the keyboard focus in the search field. Jeremy sees the indicator in the search field and knows he does not have to navigate to the search field before saying a search term.
• Erin has dyslexia which often causes her to confuse directions. She uses gestures to navigate her mobile phone. As focus moves from one element to another, there is a visible focus indicator, which allows her to find the focus easily.

Related Resources for Success Criterion 2.1.2:

• Guideline 1.3 Provide highlighting for selection, keyboard focus, enabled elements, visited links
• 4.1.2 Expose Basic Properties ensures that the focus location is available to assistive technology.

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player, plugin, web-based user agent (readers, players)

Intent of Success Criterion 2.1.3:

If users can put focus on an element, they can remove focus and move on to the next element. This is often not possible with embedded objects. The user agent needs to provide a way to always return to the previous or next element in the content, or a known location such as the address bar. The user agent also needs to take control back from the embedded object, no matter what it is.

Examples for Success Criterion 2.1.3:

• Ari has repetitive strain injuries that are exacerbated when he uses the mouse. He is using a video hosting site where each page hosts a nested media player. He presses Tab until the focus in on the media player, then presses Enter to activate and put the keyboard focus on it. When he's finished watching the video, he presses Tab to navigate to the comments below the video, but cannot get the focus to leave the video player. He presses Alt+Left to return to the previous page, but that also fails because the video player is consuming those keystrokes. Luckily, Ari knows that Shift+Esc will return focus from a nested user agent, with or without its cooperation. Thus, even a badly behaved nested user agent cannot prevent Ari from getting on with his work.
• Ari has repetitive strain injuries that are exacerbated when he uses the mouse. He uses the tab key to move the focus to a toolbar add-on that does not relinquish control back to the user agent. He presses Alt-D to move the focus to the address bar.
• Mary is a blind user who does not use the mouse. She moves the focus to an embedded scripted application that was poorly programmed. She presses a documented key combination – Alt+N – to override the scripting and move the focus to the next element in the content.
• Katan cannot use the mouse and has trouble with short-term memory. He is using a virtual machine. The escape sequence is Shift+Ctrl+Escape. Every time Katan opens the program, it briefly shows the escape sequence near the top right corner of the screen.  The virtual machine also has an Exit option in its menu system. The Escape keystrokes are also indicated on the menu.

Related Resources for Success Criterion 2.1.3:

• None

Applies to:

UA user interface, Content user interface, Configuration settings

Typically Implemented in:

browser, media player, plugin, add-on, (web-based UA are already required to do this by WCAG)

Intent of Success Criterion 2.1.4:

People do not expect side effects when moving the keyboard focus regardless of whether the side effect is caused by the user agent or author content. If users fail to notice side effects, they could end up doing something disastrous. This is especially likely for users of assistive technology who cannot see changes happening elsewhere on the screen. Users may also find it confusing or disorienting if the effect causes unexpected focus movement or changes in context. If the user agent does implement side effects to keyboard navigation, it is recommended that it provide a user preference setting to disable them. However, in some cases it may be more appropriate to provide a separate navigation mechanism that avoids side effects, such as allowing the user to hold down the Ctrl key while navigating to avoid changing selection or choice. Note: It may not be possible for the user agent to detect or prevent side effects implemented by scripts in the content, but the user agent is required to prevent side effects that are under its control.

Examples for Success Criterion 2.1.4:

• Murray has low vision. He uses a screen magnifier that allows him to see the element with the focus and a small area around it. He explores a dialog box by repeatedly pressing the Tab key to move to, and read each control in succession. He uses the arrow keys to navigate through a dropdown menu. When he moves the focus to the first option he goes to that page. He wants to navigate to the third selection, but can't get there. Fortunately, the platform also has a convention that holding down the Ctrl key while navigating that moves the focus without changing selection or option choice. Murray uses this while exploring. His web browser implements its own form controls and navigation mechanisms rather than using the platform's infrastructure, but also implements this Ctrl-key mechanism for users like Murray.
• Malak is blind. He uses the screen reader on his smartphone to navigate a web page. He selects an item and is able to activate the element using gestures. This requires sufficient screen real estate to perform gestures without changing focus.
  

Related Resources for Success Criterion 2.1.4:

• WCAG 2.0: 3.2.2 - On Input
• WCAG 2.0: 3.2.5 Change on Request
• WCAG Techniques: SCR19: Using an onchange event on a select element without causing a change of context
• WAI-ARIA: aria-selected (state)
• 1.8.11 Allow Top-Level Viewport Focus Control
• 3.3.1 Avoid Unpredictable Focus - more information on unexpected changes initiated by the user agent.

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player, plugin, web-based user agent (readers, players)

Intent of Success Criterion 2.1.5:

Keyboard users rely on the user agent to provide keyboard support that is full-featured and consistent among applications. Following platform conventions for keyboard access helps ensure that the functions that people rely on are not accidentally omitted. In addition, making these inputs consistent within and across programs greatly reduces learning curve, cognitive load, and errors. User agents are encouraged to add keyboard commands when the commands provide additional features or benefit for users. User agents should avoid omitting the standard commands, or assigning them to different keys.

Examples for Success Criterion 2.1.5:

• Jack is blind and uses a screenreader. He edits blog posts in his browser's text area control, and can use the same keys for navigation, editing, and formatting that he's used to using in other applications on the platform (e.g. arrow keys, commands to move to the beginning and end of the line, cut, copy, paste, ctrl-b for bolding).
• Wenda is blind and uses a screen reader. Her user agent uses a custom tree control showing a hierarchical outline view of the document headings. She can navigate within that control using the same keys as work in the native tree controls used in other applications (e.g. up, down, left and right arrow keys, and navigating directly to entries by typing the beginning of their text).
• Jack is blind and uses a screenreader. He puts his browser into a caret browsing mode so he can move the text cursor through the text on the page. The browser supports the same keys for navigation and editing as are used in other applications.

Related Resources for Success Criterion 2.1.5:

• None

Applies to:

UA user interface,Content user interface

Typically Implemented in:

browser, media player, plugin, add-on, web-based user agent (readers, players)

Intent of Success Criterion 2.1.6:

Efficient keyboard navigation is especially important for people who cannot easily use a mouse, are quickly fatigued, or find it difficult to memorize the menu structure for sequential navigation. This is important in all types of user agent environments.

• In a browser: A browser provides keyboard shortcuts for its menu functions as well as access keys in the design of its menus and dialog boxes. The choice of shortcut keys follows platform conventions where applicable (e.g. for open document, save document, cut, copy, paste).
• In a mobile environment: A social networking application on a mobile device has only a very few keyboard shortcuts available on its targeted devices. These few keyboard shortcuts are used for the most commonly accessed functions of the application (e.g. home, list of friends).
• In a media player: An embedded media player provides shortcut keys for commonly used functions (e.g. pause and play).

Examples for Success Criterion 2.1.6:

• Jack is blind and uses a screenreader. He opens his browser to write his email. He uses a shortcut to start a new message. He uses the same Ctrl-N command he uses in his desktop email application.
• Jean has a medical condition that makes it difficult to visualize complex visual structures like dropdown menus. She is writing a new blog entry and discovers that her blogging application has updated and all the menus have changed. She cannot find the menu option to format the text, but is pleased to find that Ctrl-B still works to bold the text she wants.
• George is blind and uses the gestures on his mobile device to move focus to the top of the page, return to the previous web page and activate links.

Related Resources for Success Criterion 2.1.6:

• 5.1.3 Implement Accessibility Features of platform

Applies to:

Content user interface

Typically Implemented in:

browser

Intent of Success Criterion 2.2.1:

Sequential keyboard navigation is a fundamental, universal method of keyboard access. While it can be slower and require more input than other methods (such as direct, structural, or search-based navigation) it is a simpler mechanism that requires very little cognitive load or memorization, and is consistent across contexts. Users need keyboard access to all viewports and all enabled elements so that they can manipulate them, view them with screen magnifiers, or have them described by screen readers. The ability to move both forward and backward through the navigation order greatly reduces the number of keystrokes and allows the user to more easily recover from mistakes in overshooting a destination.

Examples for Success Criterion 2.2.1:

• Sooj has a repetitive stress injury and cannot use a mouse. She cannot use a pointing device, so she moves the keyboard focus to the next enabled element by pressing the Tab key, and to the previous enabled element by pressing Shift+Tab. Within list boxes and radio button groups she uses the up and down arrow keys to move to the next and previous items.
• George is blind and uses a screenreader on his computer and the speech output and gesture features of his mobile phone. When completing a web form on his phone, he uses the swipe gesture to advance through the form. If George goes past the next form field, or wishes to return to a previous form field, he can use a gesture to go backward.

Related Resources for Success Criterion 2.2.1:

• 2.3.1 Direct Navigation to Important Elements
• The following is a non-exhaustive list of keyboard shortcut conventions for various platforms (from ATAG 2.0):
  • Desktop OS
    • GNOME Desktop on Linux:GNOME Human Interface Guidelines 3.4 - Keyboard Interaction
    • Mac OS: Mac OS X keyboard shortcuts
    • Microsoft Windows: Keyboard Shortcuts for Windows
  • Cross-OS environments
    • Eclipse: Eclipse Keyboard Shortcuts
    • Java SE: Java Look and Feel Design Guidelines: Keyboard Operations
    • Lotus Notes: Keyboard shortcuts in Notes 6.x and Notes 7.x

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser,add-on

Intent of Success Criterion 2.2.2:

Users need to be able to jump directly to next or previous viewports without having to visit every element in a viewport on the way to the next viewport. Not being able to jump directly can add an exorbitant number of navigation commands to operations that should be easy and efficient. Users need keyboard access to all viewports and enabled elements so that they can manipulate them, view them with screen magnifiers, or have them described by screen readers. The ability to move both forward and backward through the navigation order greatly reduces the number of keystrokes and allows the user to more easily recover from mistakes in overshooting a destination. This navigation can be among applications, windows, or viewports within an application. This includes the user agent's user interface, extensions to the user interface (e.g. add-ons), and content.

Examples for Success Criterion 2.2.2:

• Sooj has a repetitive stress injury and cannot use a mouse, so she moves the keyboard focus to the next pane by pressing F6 or to the previous pane by pressing Shift+F6. She moves between tabbed document views by pressing Ctrl+Tab and Shift+Ctrl+Tab.
• Sooj has a repetitive stress injury and cannot use a mouse. She is working in her web browser, where one document window (viewport) is active (has the active keyboard focus). When she switches to her word processor, the web browser's window and its keyboard focus become inactive, and it hides its cursor. When Sooj switches back to the browser window, it reactivates that viewport, its keyboard focus becomes active again, and its cursor reappears in the same location as when she switched to a different application.
• Sooj has a repetitive stress injury and cannot use a mouse. A developer creates an add-on to a user agent that allows the user to add notes about each web page being visited. Sooj presses a shortcut key to move focus to the user interface of this add-on and interact with the functionality offered by the add-on. Similarly, Sooj presses another key to move focus back to the main viewport for the user agent in the same location as when she moved to the plug-in.

Related Resources for Success Criterion 2.2.2:

• 2.2.1 Sequential Navigation Between Elements for background information on the importance of sequential navigation.

Applies to:

Content user interface

Typically Implemented in:

browser

Intent of Success Criterion 2.2.3:

When the content author doesn't explicitly define a consistent tab order, the browser will provide one. Users need to have a mental map of where the focus will land when they press the Tab key or use other sequential navigation commands. If the focus jumps in seemingly random fashion, skipping up or down, it becomes impossible to use this method efficiently because users must stop, find the focus, reorient, and determine what direction they should proceed every time they press navigation keys. This is a particular problem for users with some cognitive limitations or whose disability makes input difficult, tiring, or painful. Content authors are expected to define a logical navigation order in their documents, but if they have not, this success criterion ensures that the order will at least be consistent between user agents.

Examples for Success Criterion 2.2.3:

• Alec is filling out an HTML form. Because the form's author has not specified a navigation order using the tabindex attribute, when Alec presses the Tab key the focus moves to the next control in the order defined in the underlying HTML. This order is logical as long as the author is not using styles to change the visual order. Alec has the same experience completing this form on his mobile phone.

Related Resources for Success Criterion 2.2.3:

• WCAG 2.0 success criterion 2.4.3 Focus Order

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser

Intent of Success Criterion 2.2.4:

Users need a good mental map of the navigation sequence and behavior, and particularly need to know when they have started over again so they can maintain that mental map and not waste time and energy inadvertently revisiting information. This is a greater problem for users who have limited short-term memory, perceive a narrow field of vision, or use a screen magnifier, screen reader or small screen device. This also prevents people with mobility issues from having to use extra navigation commands.

Examples for Success Criterion 2.2.4:

• Betsy has low vision. She is using a screen magnifier that only shows her a single line of text. She's navigating through a long list of unsorted items in a list box, searching for an entry that she does not realize is not in the list. Each time she presses the down arrow she is presented with the next item in the list. The list box wraps, so after she reads the final entry and presses the down arrow, she is once again presented with the first entry in the list. Unfortunately, it takes her a long time to realize that she's scrolling through the same set of items again and again. To avoid this, she can turn on an option to prevent wrapping, or have the user agent play a sound or display a message to indicate that it is wrapping back to the first item. This behavior should be under the user's control, because keyboard users who can see the entire screen may not want to be interrupted by a pop-up dialog box.
• Jeff has a mobility impairment. He uses gestures to navigate the page. When he reaches the last active element on the page there is an indicator that the end of the page is reached before changing focus (e.g. wrapping to the top, switching pages).

Related Resources for Success Criterion 2.2.4:

• None

Applies to:

Content user interface

Typically Implemented in:

browser

Intent of Success Criterion 2.3.1:

People who are blind or have mobility problems often find it difficult or impossible to use a mouse to move the viewport to, and focus on, important elements. Some other form of direct navigation – such as numbers or key combinations assigned to important elements – should be available. Direct navigation can be accessed via keyboard, which also supports other forms of input, such as gesture, speech and touch.

Examples for Success Criterion 2.3.1:

• Mary cannot use the mouse or keyboard due to a repetitive strain injury. She uses speech input with a mouseless browsing plug-in for her browser. She is able to use the same plug-in on her smartphone. The plug-in overlays each link with a number that can then be used to directly select it (e.g. by speaking the command "link 12"). This prevents Mary from having to say "tab" numerous times to select a link.

Related Resources for Success Criterion 2.3.1:

• 2.2.1 Sequential Navigation Between Elements
• Mouseless Browsing Firefox Extension

Applies to:

Content user interface

Typically Implemented in:

browser

Intent of Success Criterion 2.3.2:

People who are blind or have mobility problems often find it difficult or impossible to use a mouse to move the viewport to, focus on, and activate important elements. Some other form of direct navigation – such as numbers or key combinations assigned to important elements – should be available. Direct navigation can be accessed via keyboard, which also supports other forms of input, such as gesture, speech and touch.

Examples for Success Criterion 2.3.2:

• Mary cannot use the mouse or keyboard due to a repetitive strain injury, instead she uses voice control technology with uses a mouse-less browsing plug-in to her browser. The plug-in overlays each hyperlink with a number that can then be used to directly select it (e.g. by speaking the command "select link twelve"). This prevents Mary from having to say the word 'tab' numerous times to get to her desired hyperlink.
• Mary cannot use the mouse or keyboard due to a repetitive strain injury. On her mobile phone, Mary uses a single speech command to launch the app, rather than having to use multiple commands to page through screens to find the app icon and activate it.

Related Resources for Success Criterion 2.3.2:

• None

Applies to:

Content user interface, Configuration settings (optional)

Typically Implemented in:

browser

Intent of Success Criterion 2.3.3:

For many users, including those who use the keyboard or an input method such as speech, the keyboard is often a primary method of user agent control. It is important that direct keyboard commands assigned to user agent functionality be discoverable, including in rendered content. If direct commands are not presented in content, many users will not discover them.

Examples for Success Criterion 2.3.3:

• Fiona is blind. She uses an audio browser. When the system reads form controls in the rendered content, it reads the label of the form followed by the accesskey (e.g. "name alt plus n").
• Mary cannot use the mouse or keyboard. She uses speech input. She is composing an email and wants to attach a file. She sees Ctrl+Shift+A next to the link to attach a file. Mary says the command to add the attachment.
• Mary cannot use the mouse or keyboard. She uses speech input. When reading email on her tablet, Mary touches a control which opens a toolbar with a setting to display the accesskeys and other direct commands that the author created. She sees that a 3-finger swipe will delete the current email.

Related Resources for Success Criterion 2.3.3:

• 2.1.5 Follow Text Keyboard Conventions
• Mouseless & More for perceivable navigation and activation keys
• Accesskey shortcuts in Google Chrome and more
• Firefox hack to display "accesskey" keyboard shortcuts

Applies to:

UA user interface, Configuration settings (optional)

Typically Implemented in:

browser, media player, plugin

Intent of Success Criterion 2.3.4:

For many users, including those who use the keyboard or and input method such as speech, the keyboard is often a primary method of user agent control. It is important that direct keyboard commands assigned to user agent functionality be discoverable as the user is exploring the user agent. If direct commands are not presented in content, many users will not discover them.

Examples for Success Criterion 2.3.4:

• Vlad is a keyboard-only user who uses a browser on the Mac operating system. When he needs to perform a new operation with the browser user interface, he searches for it in the menus, and notices that the menu item has a shortcut in the label (e.g. "Copy   ⌘+C"). This indicates the direct activation command he can use in the future to avoid having to traverse the menus.
• Amir uses ability switches to control an onscreen keyboard for the Windows operating system. When he presses the "Alt" key the available browser user interface accesskeys are shown as overlays on the appropriate user interface controls (e.g. "File with 'F' in an overlay").
• Neta has a repetitive strain injury. She relies on gestures and shortcuts to complete tasks. Using a specialized command on her mobile device, she can pull up an overlay of arrows and text showing all the commands that can be completed in that context. This allows her to learn new programs as efficiently as possible, making it less likely she will overtax her hands.

Related Resources for Success Criterion 2.3.4:

• None

Applies to:

UA user interface, Content user interface, Configuration settings

Typically Implemented in:

browser, media player, plugin

Intent of Success Criterion 2.3.5

People using a keyboard interface need the ability to remap the user agent's keyboard shortcuts in order to avoid keystroke conflicts with assistive technology, reduce number of keystrokes, use familiar keystroke combinations, and optimize keyboard layout (e.g. for one-handed use). This is important for people with dexterity issues where every keystroke can be time consuming, tiring or painful. It is also important for people using assistive technologies such as screen readers, where many keystrokes are already in use by the assistive technology. The goal of this success criterion is to enable the user to be in control of what happens when a given key is pressed, use the keyboard commands that meet specific needs, and save the modifications.

Content authors can use the Accesskey attribute to define shortcut keys that allow quick access to specific elements, actions, or parts of the web content. The author can select shortcuts that are different from what the user expects. Users who rely upon keyboard input may want consistent shortcut keys across the sites they visit.

Users should have the option to make any keyboard shortcuts be persistent across browsing sessions. The user should be able to save, import and export these settings.

User agents can also offer the user the option to automatically apply preferred key combinations for content that has author-specified accesskey bindings that are based on the associated text, label, or ARIA role. This overrides any author-specified keybinding.

Examples for Success Criterion 2.3.5:

• Frank has repetitive strain injuries and uses speech input. He has defined standard commands to access commonly used parts of a website. For example, when Frank says "site search", the cursor jumps to the search field. If the author has assigned an access key that is not standard, Frank can override it and set the access key to a standard mapping so he can say the same search command across all the sites he uses.
• Laura types with one hand and finds keys on the left side of the keyboard easier to press. She browses to a web page and notices that the author has assigned access keys using keys from the right side of the keyboard. She opens a dialog in the user agent and reassigns the access keys from the web page to the left side of the keyboard. She also uses the user agent's preference settings to redefine its keyboard shortcuts in the same way.
• Laura types with one hand. On her mobile device, Laura maps common website actions to numeric shortcut keys. For example, she prefers to have the 1 key to activate a site's search function. An author of a site visited daily by this user defines "S" as the accesskey for the search function. Laura overrides the author-specified accesskey of "S" with "1".
• Elaine has low vision and is using a screen magnification program. The program uses Alt+M to increase the size of the magnified area of the screen. She notices that in her web browser, Alt+M is a access key for activating a home button that stops her from being able to control her magnification software. She opens a access key reassignment feature in the user agent, and sets Alt+O to be the new access key for the home button. Her screen magnification software now works correctly.
• George uses a screenreader. The screenreader uses Ctrl+F to read the item with focus. Since this is a common user agent command for Find, the user agent allows George to reassign the Find command to a non-conflicting key binding. The user agent provides a list of user interface features and default keyboard assignments with options for the George to assign new key combinations. George saves the user keyboard customizations the same way he saves other user preferences.

Related Resources for Success Criterion 2.3.5:

• Guideline 2.6 - Configure and store preference settings

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player, plugin

Intent of Success Criterion 2.4.1:

The find or text search function in a user agent allows the user to easily locate desired information in rendered content. People who read or navigate slowly or with difficulty due to a disability rely more heavily on the ability to search for text, rather than scanning or reading an entire document to find it. The ability to search alternative content allows screen reader users to find content they heard on their speaker. Users with hearing impairments use Text Search as an efficient method of jumping to specific points in a video. Users who find it difficult to use the mouse or keyboard and have to limit their physical operations will save movements using search.

Examples for Success Criterion 2.4.1:

• Marvin has a dexterity impairment. He needs to move efficiently to specific text in the document.  The user agent provides a local search function that is available using speech commands. Marvin says "find box," a text box with a search button appears. He speaks the word he is looking for, and says "enter", which executes the search function.
• Betty has low vision. She is attempting to create a user stylesheet for a site and needs to know the 'class' attribute value for navigation headers. Betty gets the source view of the current page and searches for the specific phrase used in a navigation list to find the class associated with  the navigation element
• Joe has a distraction disorder. He is taking an online exam. He is working on the 6th question when he realizes he wrote something wrong in the essay on question 2. He uses the search function in the browser to find the text in error inside the textarea of question 2.
• Sam is a screen reader user. He wants to send the flow chart image on the page to a colleague. Sam searches for the word "flowchart" that he heard spoken as part of the 'alt' text for the image. He then uses the context menu to select the address of the image and sends it to his colleague.
• Agnes is deaf. She is watching a video with captions turned on. Agnes uses the search function to search through the captions and jump to the point in the video where the search term is located in the time line.
• Greta has a reading impairment. She is trying to efficiently locate some information in a large, detailed graphic. She is using a browser with native support for SVG. When Greta searches for a term, text within the SVG is searched along with the HTML content.

Related Resources for Success Criterion 2.4.1:

• None

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player, plugin

Intent of Success Criterion 2.4.2:

People who read slowly or with difficulty due to a disability rely more heavily on the ability to search for the text they're looking for, rather than scanning or reading an entire document to find it. Local find in a user agent allows the user to easily locate desired information in rendered content. The ability to search for alternative text content allows screen reader users to find content they heard on their speaker. Users with hearing impairment use text search as an efficient method of jumping to specific points in a video.

Examples for Success Criterion 2.4.2:

• Gwen is blind. She's been reading through several different web pages and wants to quickly locate a phrase she has previously read. She guesses that it is past where her point of regard is in the current document. She uses the user agent search function to search forward in the document. When the search reaches the end of the document, it notifies her, and she realizes that the remainder of the article she is in doesn't contain that phrase.

Related Resources for Success Criterion 2.4.2:

• None

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player, plugin

Intent of Success Criterion 2.4.3:

It is important for the user to easily recognize that a search term has been found and that the term is revealed to the user in context. The user agent moves the viewport to include the found term and the term is highlighted in some fashion. The point of regard is the found element in the viewport. Any subsequent searches on the same term or other navigation tasks (e.g tabbing to the next anchor) begin from this point.

Examples for Success Criterion 2.4.3:

• Jules has low vision and uses a magnified screen. She frequently searches for terms that appear multiple times in a document that contains a lot of repetition. It is important that the viewport moves and if necessary her screen scrolls after each search so she can easily track where she is in the document.

Related Resources for Success Criterion 2.4.3:

• None

Applies to:

UA user interface, Content user interface, Configuration settings

Typically Implemented in:

browser, media player, plugin

Intent of Success Criterion 2.4.4:

It is important for users to get clear, timely feedback so they don't waste time waiting or, worse, issue a command based on a wrong assumption. It is important during a search that users are informed when there is no match or that the search has reached the beginning of the document.

Examples for Success Criterion 2.4.4:

• Dennis is blind and uses a screen reader. As soon as he gets a message that there is no match he goes on to search for something else, however, if he does not get a message he wastes time retrying the search to make sure the entire document has been searched.
• Dennis is blind and uses a screen reader. When he searches for a word in a web page and the search wraps to the beginning of the page, his computer beeps to alert him that the search has wrapped.

Related Resources for Success Criterion 2.4.4:

• None

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player, plugin

Intent of Success Criterion 2.4.5:

Authors frequently provide alternative content to meet web content accessibility guidelines. Users with disabilities may experience this as part of the content. The purpose of this success criteria is to ensure that text search allows users to locate this content, even if it is not visibly rendered.

Examples for Success Criterion 2.4.5:

• Rhonda is easily distracted. She typically browses the web with images turned off so she sees alternative text rendered in place of images. She visits a favorite website on a friend's computer and wants to find a link to her favorite artist's photo gallery. She searches for the artist's name on her friend's computer. The alt text is not displayed, but the artist's image is highlighted because her 'text search' command has associated the alt text with the image.
• Tasina is hard of hearing and watches movies with captions on. She remembers a phrase in a captioned training movie that he wants to replay. He goes to the web page with the embedded movie. He types in the phrase in the "Find" box and the user agent moves to the point in the movie where the phrase is found.

Related Resources for Success Criterion 2.4.5:

• None

Applies to:

Content user interface

Typically Implemented in:

browser

Intent of Success Criterion 2.5.1:

Users who find it difficult or impossible to use the mouse require an efficient way to jump among elements without having to navigate through intervening content. Navigating by heading is especially important when scanning a web page to find a pertinent section. Navigating by table element is especially important when building or reading tables.

Examples for Success Criterion 2.5.1:

• Jamie is blind and uses a screen reader. When he reads the New York Times he scans the headlines to find interesting stories. To do this he needs a way to go from headline to headline.
• Billie is a paraplegic who uses speech input to write long legal documents. When she is proofing a document she needs to scan each section header. It takes far fewer speech commands to navigate the section headers when she can jump directly to them. Billie also makes extensive use of tables. It takes far fewer speech commands to navigate tables when she can jump directly among elements. Direct navigation to headlines and table elements allows her to do her job without overusing her vocal cords and within required time constraints.
• Celia has short-term memory issues and is easily distracted. When looking for any particular section of the document, she finds it easier to scan through headings by jumping from heading to heading rather than having to scan through an entire page of potentially distracting text. Celia also finds it useful to be able to move from a subheading to a major heading and back to orient herself within the context without becoming confused.
• Armand is blind. When he reads a long web page on his iOS smartphone, Armand navigates from heading to heading using the Rotor commands on his phone.

Related Resources for Success Criterion 2.5.1:

• None

Applies to:

Configuration settings

Typically Implemented in:

operating system, browser, media player, plugin, add-on, web-based user agent (readers, players)

Intent of Success Criterion 2.6.1:

When a user has customized settings within the user agent to maximize accessibility, customization is saved between browsing sessions. The user can automatically use those settings in subsequent browsing sessions.

Examples for Success Criterion 2.6.1:

• Lynn has moderately low vision. She sets the default zoom level, font size, and colors to make pages easier for her to read. Because those settings are persistent, she doesn't have to manually restore her settings every time she starts the browser.
• Brian is a quadriplegic who uses speech input. He has to adjust settings in his browser to make it fully compatible with his speech input system. It's difficult for him to adjust these settings, since he can't fully operate the browser until it's complete. Once his browser is configured this way, he relies on it staying in that configuration even if he upgrades the browser or restarts his system.
• Betty has low vision. She customizes her mobile browser's color and font settings to make text much easier to read. Her browser incorporates a cloud-based profile so she can retain her settings across her browsing sessions and her desktop and tablet browsers.

Related Resources for Success Criterion 2.6.1:

• 5.1.3 Implement Accessibility Features of the Platform

Applies to:

Configuration settings

Typically Implemented in:

operating system, browser, media player, plugin, add-on, web-based user agent (readers, players)

Intent of Success Criterion 2.6.2:

For some users, it may be difficult to easily recall all modified settings. Others may find it difficult to navigate to each modified setting, especially if a particular setting impacts their ability to do so. Users who customize settings may find that their chosen settings are not suitable and decide to restore these settings to default values. This success criteria allows a user to easily restore all preference settings to default values using a single function or action.

Examples for Success Criterion 2.6.2:

• Ron is blind. He accidentally changes a browser setting that makes his browser incompatible with his screen reader, preventing him from changing it back. He restarts his browser using a command line option that starts in the default configuration. From there he can adjust the setting that caused him problems.
• Kathy has repetitive stress injuries which makes it painful to for her to experiment with settings. She accidently turns on a zoom feature on her smartphone and cannot figure out how to turn it off. She gestures to navigate to the preferences menus and selects a command to reset preferences to default.

Related Resources for Success Criterion 2.6.2:

• 3.1.2 Settings Changes can be Reversed or Confirmed
• 5.1.3 Implement Accessibility Features of the Platform

Applies to:

Configuration settings

Typically Implemented in:

operating system, browser, media player, plugin, add-on, web-based user agent (readers, players)

Intent of Success Criterion 2.6.3:

Some users may need to change their setting preferences under circumstances such as varying levels of user fatigue, changes in environmental noise, or changing lighting conditions. Providing an easy method for saving and switching between sets of preferences helps the user complete intended tasks.

Examples for Success Criterion 2.6.3:

• Hiroki has low vision. When he is carrying his tablet computer he operates it with the built-in touchscreen. When at his desk he links it to a Bluetooth keyboard and mouse, and redirects the display to a large computer monitor. The browser allows him to quickly switch between different configurations for different environments.
• Davy has moderately low vision and must adjust the contrast of media to different levels for day and night. Because this requires a multiple steps, he has two user profiles, one for each environment.
• Aaron has repetitive strain injury. He usually uses a keyboard and mouse, but when his repetitive strain injury is bothering him he prefers to use the keyboard and avoid using the mouse as much as possible. At those times he uses his browser's user preference profiles to load a different configuration that’s optimized for the keyboard.

Related Resources for Success Criterion 2.6.3:

• 5.1.3 Implement Accessibility Features of the Platform

Applies to:

Configuration settings

Typically Implemented in:

browser, media player

Intent of Success Criterion 2.6.4:

Users with disabilities may not be able to use a user agent in a particular configuration. This can occur during setup when default settings don't meet their needs, or after someone changes an option. If users cannot change the settings from the user interface, they need a way to adjust or reset those options from outside the user agent. The user agent can accomplish this in multiple ways including detecting and implementing the platform accessibility settings, providing an external file to modify, providing access to settings from a separate utility program, providing accessibility options in the installation program, or providing command-line switches to change the user agent's behavior.

Note: User agents are encouraged to allow all user preferences to be adjusted.

Examples for Success Criterion 2.6.4:

• Aosa is blind. Her web browser is incompatible with her screen reader unless she changes one of the browser's advanced settings. Because she cannot activate and use the appropriate dialog box until the setting is changed, she needs to start the browser using a dedicated command-line switch that changes the behavior.
• Bintu is deaf and enjoys watching captioned videos. Since different video players may not have accessible settings, she sets her browser to always display captions, knowing the video player will respect the browser's request to display captions. In this way the options in one user agent (the embedded video player) are set outside its user interface by being set in another program (the hosting browser).
• Sasha requires high contrast to be able to discriminate the shape of letters. She has set the accessibility preferences on her computer to use high contrast mode. When she launches her browser, it detects that she is using high contrast and adjusts the font and color settings for its user interface to reflect those settings.
• Justin has an attention deficit disorder. He is setting up his new e-book reader and is interrupted while setting the default font colors. He accidentally sets his background and font color to white on white. He can't read the settings screen to recover his default settings, so he exits the reader and follows the instructions on the vendor's website to edit the "settings.ini" file to adjust the colors. He restarts the reader with the corrected color settings.
• Jan is easily confused by new interfaces. Using the screen reader capabilities on her mobile phone she changes the interface of the updated browser, then can't figure out how to undo them. She uses an app from the browser developer to reset the browser settings to default.

Related Resources for Success Criterion 2.6.4:

• 5.1.3 Implement Accessibility Features of the Platform

Applies to:

Configuration settings

Typically Implemented in:

browser

Intent of Success Criterion 2.6.5:

Configuring a user agent can be a complex and time-consuming task. Some users hire assistive technology professional trainers to do their system setup. Users who have spent time customizing accessibility preferences to meet their requirements need to migrate preference setting to other compatible devices. Schools and universities also need to maintain accessibility settings across multiple machines.

Examples for Success Criterion 2.6.5:

• Lori is a rehabilitation specialist who works with clients to customize electronics and assistive technology to their needs. She sets up a new system for Ray, and saves a backup of the accessibility setting for Ray and for herself. She keeps electronic backups of her clients' configurations that she can quickly email to them if they lose their settings.
• Ray is blind and uses a screenreader on his desktop and a voice application on his phone. He sets up web-based email application accessibility preferences on his phone. The preferences are automatically reflected in the desktop version of that web-based email application.
• Trisha is a 4th grader with low vision. When she changes classrooms, she carries a USB stick containing her accessibility settings so she and her teachers do not have to use class time customizing her computer.
• Betty has low vision and has a highly customized color palette defined in her browser. She saves her customizations to a cloud-based storage service, so her preferences can be transferred to the other desktop and mobile browsers that she uses.

Related Resources for Success Criterion 2.6.5:

• 5.1.3 Implement Accessibility Features of the Platform

Applies to:

UA user interface, Configuration settings

Typically Implemented in:

browser, media player, plugin, web-based user agent (readers, players)

Intent of Success Criterion 2.7.1:

The user needs to control which user interface elements are visible and usable, where elements are visually located on the screen, and where elements fall in the navigation order. In some cases adjusting whether an element is visible and usable can involve installing or uninstalling a component — or merely showing or hiding it — depending on the user agent and the specific component.

This can reduce keystrokes, bring buttons into view that are hidden by default or otherwise allow the user to interact with the user agent in a more efficient fashion. Users with dexterity impairments or mobility impairments can have problems making the large movements required to select between non-adjacent controls which they need to use frequently. Similarly, users with low vision can have to move their magnified view-port excessively to see frequently used controls. Enabling these controls to be situated together removes some of the strain faced by these users, and increases productivity as task completion times are decreased.

Examples for Success Criterion 2.7.1:

• Martin accesses the computer by pressing keys with a stick held in his mouth. He gets around the user agent with taps on the tab and arrow keys. The button for printing a web page is the last button on a toolbar. This button requires six presses of a right arrow key. This is the only button Martin uses on the toolbar. Using a preferences dialog, Martin is able to configure this toolbar to only show the Print button, reducing the number of time he must press with his mouthstick.
• Laura has one hand. When she holds her mobile phone in her left hand, she must use her thumb to press the controls. She configures her mobile apps so that the toolbars are at the left side or the bottom, so she can reach them.
• Caraway has a repetitive strain injury. She uses speech input. The speech program automatically clicks toolbar items that she speaks. In programs she uses a lot she removes toolbars that she doesn't use in order to reduce the probability that the speech program will interpret text input as a toolbar command and click something Caraway does not intend.
• Zelda has a brain injury that leaves her easily confused. She reorders the toolbars in her web-based word processing and layout programs so that the text color and highlight color icons are in the same order and she can rely on habit to click the correct button no matter what program she is in. Without this ability to reorder she finds herself constantly clicking the wrong button because they are configured differently by default in the different programs.
• Devon is easily distracted. In programs he uses frequently, he removes toolbars he does not use in order to cut down on distractions.
• Sally has memory issues that make it difficult to memorize keyboard shortcuts. She has aligned the keyboard shortcuts in several programs so she doesn't have to memorize as many shortcuts. She reminds herself of keyboard shortcuts by hitting a key that gives her a list of keyboard shortcuts in the current program.
• Linda has rheumatoid arthritis and finds it difficult to perform the pinch gesture that's commonly used to zoom on mobile phones. She changes the default gesture for zooming to a gesture she can more easily do. Linda's left hand is less damaged than her right hand. She moves a common control from the right side of the screen to the left side of the screen to make it easier to access with her left hand.
• Jennifer is blind. She sometimes configures apps on her friend Linda's mobile phone. When Jennifer picks up Linda's mobile phone, she turns on the built-in screen reader so she so she can quickly find her way around Linda's phone. When Jennifer is done, she changes the controls back to Linda's original settings.

Related Resources for Success Criterion 2.7.1:

• WAI-ARIA

Applies to:

UA user interface, Configuration settings (optional)

Typically Implemented in:

operating system, browser

Intent of Success Criterion 2.8.1:

People who use assistive technology and those who require more time to read, understand, or act upon content (e.g. individuals with reading disabilities or non-native readers of the presented language) should be able to extend or override any content or author imposed presentation or interaction time limits.

Examples for Success Criterion 2.8.1:

• Hildreth has severe arthritis, which affects her computer navigation. She sometimes clicks accidentally, and she needs more time to navigate. When she clicks Exit on her web browser, it displays a message box asking if she is sure she wants to exit, with a timer saying she needs to respond within 10 seconds. Hildreth changes the settings in her user options to turn off this timeout so she has adequate time to respond.
• Susie reads slowly. When she hovers her mouse over a link to see a pop-up showing the destination of the link, the popup ordinarily disappears after two seconds, which is not enough time for her to read it. She turns off this timeout, allowing her to hover the mouse for as long as she needs to read the text before moving it to allow the pop-up to disappear.

Related Resources for Success Criterion 2.8.1:

• Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT)required behaviors for time limits

Applies to:

UA user interface, Content user interface, Configuration settings (optional)

Typically Implemented in:

browser, media player, plugin, web-based user agent (readers, players)

Intent of Success Criterion 2.9.1:

Seizures due to photosensitivity can occur when there is a rapid series of general flashing, or a red flash. A potentially harmful flash occurs when there is a pair of significantly opposing changes in luminance. A transition to or from a saturated red is potentially harmful irrespective of luminance.

Examples for Success Criterion 2.9.1:

• Koa has photosensitive epilepsy. He checks a game website that has just added a flashing red icon to advertise their newest product. Because his browser's default configuration protects him from harmful flashing, the potentially harmful flashing does not occur on his machine.
• Koa has photosensitive epilepsy. He visits a weather web site that uses flashing to indicate a tornado warning. In order to avoid triggering seizures, the flashing is limited to fewer than three times per second, and, to be extra cautious, it is not red.

Related Resources for Success Criterion 2.9.1:

• ITC Guidance Note for Licensees on Flashing Images and Regular Patterns in Television
• WCAG 2.0: 2.3.1 Three Flashes or Below Threshold

Applies to:

UA user interface, Content user interface, Configuration settings (optional)

Typically Implemented in:

browser, media player, plugin, web-based user agent (readers, players)

Intent of Success Criterion 2.9.2:

Seizures due to photosensitivity can occur when there is a rapid series of general flashing, or a red flash. People who are particularly sensitive to flashing can be harmed by any level of flashing. 2.9.2 has the same effect as 2.9.1, going further to ensure that more sensitive users can traverse the web without potentially harmful effects.

Examples for Success Criterion 2.9.2:

• Alfred has photosensitive epilepsy and is particularly sensitive to flashes. He checks a game website that has just added a flashing red icon to advertise their newest product. His browser's default configuration protects him from all flashing, so the potentially harmful flashing does not occur on his machine.

Related Resources for Success Criterion 2.9.2:

• WCAG 2.0: 2.3.3 Three Flashes
• 2.10.1 Time-Based Media Load-Only
• 2.10.5 Stop/Pause/Resume Time-Based Media

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, media player, plugin, web-based players

Intent of Success Criterion 2.10.1:

Users who need to avoid signals that can trigger seizures, users who are easily distracted, and users who have difficulty interacting with the controls provided for playing media need to be able to load media in a paused state. The user agent provides a global control that sets a state equivalent to "paused waiting for user interaction" for all recognized media when a page loads. The user has a global option to set autoplay to off or paused until the user activates "play". The user agent provides a visual or auditory indicator that the video is in paused state and needs user interaction to start. This prevents media from playing without explicit request from the user.

When the media is not in the actual document, but rather has been created with document.createElement('audio'), the user agent does not recognize that the media exists and cannot give a visual indication by default. In this case, it is up to the author to provide the controls. See WCAG in resources below.

Examples for Success Criterion 2.10.1:

• Jill is blind. She browses the web using a screen reader to listen to the text of web pages. She navigates to her favorite shopping site and is greeted with trumpets blaring and an announcer shouting "Sale, sale, sale!" The audio is so loud that she can no longer hear the web page content. Jill closes her browser and changes a setting titled Play Audio on Request to yes and visits her shopping site again. This time she can read the content and when she is ready plays the audio and smiles, thinking of the deal's she is about to find.
• Jamie has epilepsy that's triggered by certain types of audio. She sets her browser so content does not play automatically so she can avoid audio that could trigger her epilepsy.
• Kendra has photo-epilepsy. She sets her browser so content does not play automatically so she can avoid flashing content that could trigger her photo epilepsy.

Related Resources for Success Criterion 2.10.1:

• Guideline 2.9 - Help users avoid flashing that could cause seizures.
• HTML5 4.8.10.8 Playing the media resource
• WCAG 2.0 - 1.4.2 Audio Control

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, plugin, add-on

Intent of Success Criterion 2.10.2:

Documents that do things automatically when loaded can delay, distract, or interfere with user's ability to continue with a task. Replacing executable content like embedded objects, applets and media with a placeholder tells the user what has been blocked and provides a mechanism (e.g. a play button) for unblocking when the user is ready.

Note: A placeholder should take up the same space as the object it is replacing, so that the presentation doesn't need to be reflowed when the execution is started. However, people using mobile devices or screen enlargers, or those who have difficulty with scroll commands can benefit from having the option of a smaller placeholder.

Examples for Success Criterion 2.10.2:

• Jane has difficulty concentrating. In order to concentrate on the text of a document she hides multimedia content and only triggers execution of that content by clicking on the placeholder.
• Evan is blind. He sets the option in his browser so that when a web page loads it does not automatically run an executable object. This way any or music or speech they play won't interfere with his ability to hear his screen reader. When he is ready to hear it, he navigates to the placeholder and presses the Enter key to activate it.
• Evan has configured his mobile phone so that any audio or video file displays a placeholder with a triangle "play" icon. That allows him to control when the audio or video starts.

Related Resources for Success Criterion 2.10.2:

• None

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, plugin, add-on

Intent of Success Criterion 2.10.3:

Documents that do things automatically when loaded can delay, distract, or interfere with user's ability to continue with a task. The user needs to be able to specify that executable content (e.g. scripts) be blocked when a document loads, be told which content has been blocked, and be able to selectively execute the content at a later time.

Note: Although some web applications and document can be empty until scripts are run, it is important for users to have this level of control.

Examples for Success Criterion 2.10.3:

• Jane has difficulty concentrating. In order to concentrate on the text of a document she wants to prevent animations, media, or dynamic content from executing until she is ready. An icon on the status bar tells her that scripts have been blocked. She can click on it to select which scripts to run.
• Evan is blind. He sets an option in his browser so that when a web page loads it does not automatically start running scripts that might play sounds that would interfere with his ability to hear his screen reader. An icon on the status bar tells him that scripts have been blocked. He can activate it to select which scripts to run.
• Pavel has low vision, and his browser is set to show extremely large text. He needs to click a control on a web page, but when he moves the pointer over it a script inserts explanatory text onto the page. The large font size causes the control to shift out from under the pointer, making the new text disappear. When the text disappears, the control moves back under the mouse, and the cycle repeats. As the page flickers, Pavel is unable to click on the control. To work around this problem he uses a browser command to temporarily disable scripts on the page so he can click the control and complete his task.

Related Resources for Success Criterion 2.10.3:

• Enable or Disable Tracks is included as part of 1.1.1 Render Alternative Content

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser, media player, plugin, web-based players

Intent of Success Criterion 2.10.4:

Users with sensory and cognitive impairments can have difficulty following or understanding spoken audio at the normal playback rate. If users can slow down the audio presentation of speech while maintaining the pitch or frequency characteristics, they are better able to follow the spoken content. Users with learning disabilities can be distracted or otherwise unable to follow complex animations or instructional video. With the presentation slowed, users can better observe the visual events of the animation. User can also want to slow down the media if they are taking notes, and do so slowly because of language or dexterity impairments.

Some users with visual impairments prefer faster speech rate on their screen readers or digital audio book players. The ability to speed up the audio while maintaining pitch allows those users to skim spoken audio without loss of understandability.

Examples for Success Criterion 2.10.4:

• Timo experienced a traumatic brain injury and has difficulty comprehending speech. When listening to episodes of his favorite podcast on the web, he slows down the audio by 50% and is able to understand the interviewer's and guest's question and answer session.
• Anu is a blind university student who has grown up with digital talking book players, and regularly listens to spoken audio at 200% of normal speaking rate. In studying for exams, she reviews the online lecture videos from her History course, adjusting the presentation rate to 200% on the web video player in order to quickly review the material. She slows the presentation to normal rate when she encounters material she needs to review carefully.
• Perttu has a learning disability and requires a longer time to follow instructions. He likes to cook and is watching a cooking demonstration on the web. When the instructions go by too quickly, he slows the video player to half speed.

Related Resources for Success Criterion 2.10.4:

• WAI-ARIA
• Enable or Disable Tracks is included as part of 1.1.1 Render Alternative Content

Applies to:

Content user interface

Typically Implemented in:

browser, media player, plugin, web-based players

Intent of Success Criterion 2.10.5:

Users with sensory, attention, or cognitive impairments can have difficulty understanding multimedia content. When users are able to control the presentation rate of time-based media by stopping, pausing, and resuming, they have enough time to understand or act upon presented content, or to stop potentially distracting or harmful content.

Examples for Success Criterion 2.10.5:

• Adam reads more slowly than average because of his dyslexia. He's watching a video of a lecture. When the video shows slides, he presses the space bar to pause the video so that he can read the text at his own speed. When he's ready to continue, he presses the space bar again to resume the video.
• Angelica can have audio-induced seizures. She uses a website to watch and listen to user-contributed podcasts. When she realizes the level of white noise in a particular soundtrack is likely to trigger a seizure. She quickly clicks on the player's "stop" button (or presses the equivalent keyboard command) and the noise is instantly discontinued.
• Allesandro finds it impossible to ignore visual changes. Unnecessary animations make it very difficult for him to read or interact with other content on the screen. When he's reading an article on a newspaper website and finds an animated advertisement or moving text of a news ticker distracting, he chooses the appropriate command to stop all animations.
• Amaryllis is blind and is listening to streaming audio on a web page. When she responds to an incoming email message she uses a keyboard command to pause the audio, which would otherwise interfere with her ability to hear her screen reader.

Related Resources for Success Criterion 2.10.5:

• WAI-ARIA
• Enable or Disable Tracks is included as part of 1.1.1 Render Alternative Content

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player, plugin, web-based players

Intent of Success Criterion 2.10.6:

Users with sensory, cognitive or attention impairments can find it difficult to understand or follow time-based media. This success criteria allows users to position within the timebase to review content or to skip content that can be distracting.

Examples for Success Criterion 2.10.6:

• Jared has a print disability that makes it laborious to read text. He is watching a technical training video which will display section objectives or summary questions as text. When the text flashes by too quickly for him to read, he presses a key command to skip back an increment so he can read the text. He pauses the video if more time is required.
• Debbie has difficulty with bright or flashing video. When she encounters a flashing transition in a video, she quickly presses a key command to forward the video past the flashing, then carefully uses the slider to adjust the video back to the start of the next section so she can avoid the flashing material.

Related Resources for Success Criterion 2.10.6:

• WAI-ARIA

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player, plugin, web-based players

Intent of Success Criterion 2.10.7:

Users need to be able to navigate time-based media in ways that are more meaningful than arbitrary time increments.

Examples for Success Criterion 2.10.7:

• Marka is blind. She is listening to a video of an hour-long lecture. The section she is in has technical information that builds on material from an earlier section. A sighted user could pause the video and move the slider back to reach visually distinct content from earlier section. Marka uses a control to skip back section by section until she hears the section title name she wants to review. When she is finished, Marka uses the control to move forward section by section until she hears the title of the original topic.
• Wes has fatigue injury that limits the length of his computer sessions. He stops playback of a training video when he is tired. After resting, he restarts the video and navigates to the scene where he left off.

Related Resources for Success Criterion 2.10.7:

• WAI-ARIA
• Enable or Disable Tracks is included as part of 1.1.1 Render Alternative Content

Applies to:

Content user interface, Configuration settings (optional)

Typically Implemented in:

operating system, browser, media player, plugin

Intent of Success Criterion 2.10.8:

Users with certain types of low vision need to control contrast and brightness of time-based media so they can discern the content. Users who are prone to seizures need to be able to reduce or dim contrast and brightness to protect themselves from seizures caused by flashing content.

Examples for Success Criterion 2.10.8:

• Frank has albinism. He requires a higher contrast to discern a video image. When Frank is watching an instructional video, he selects a menu item that allows him to increase the contrast of the video. This makes it easier for him to see the important content.
• Kelly has photo-epilepsy and is watching an amateur video taken on a sunny day near the water. Concerned that the video can contain flashing that could trigger a seizure, Kelly selects a menu item of video controls that allow her to reduce the brightness and contrast of the video. While some of the detail is lost, Kelly can safely watch the video.

Related Resources for Success Criterion 2.10.8:

• WAI-ARIA

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player

Intent of Success Criterion 2.11.1:

If the platform does not support text, the user agent provides a mechanism for text input as well as all other input device controls. Some users rely entirely on pointing devices, or find them much more convenient than keyboards. These users can operate applications much more easily and efficiently if they can carry out most operations with the pointing device, and only fall back on a physical or on-screen keyboard as infrequently as possible. If the platform provides the ability to enter arbitrary text using a device (such as large vocabulary speech recognition or an on-screen keyboard utility), the user agent is required to support it per Success Criterion 2.11.1. If the platform does not provide such a feature, the browser is encouraged to provide its own.

Examples for Success Criterion 2.11.1:

• Ruth has extremely limited motor control and slurred speech, so operates her computer using a head pointer. The mouse pointer moves in response to the orientation of her head, and she clicks, double clicks, or drags using a sip-and-puff switch. The operating system does not provide an on-screen keyboard, but in order to be maximally accessible, a small on-screen keyboard is available as an add-on for her browser.
• Randall has a web browser on his smart phone that allows him to perform most operations using speech commands. By offloading the speech recognition to an Internet server, it is able to perform large vocabulary speech recognition, so Randall can use his voice to compose email and fill in forms, as well as controlling the browser itself.
• Rick is paralysed from the neck down. He uses eyeblinks to control an onscreen keyboard. His user agent supports the APIs used by 3rd party eye blink applications.

Related Resources for Success Criterion 2.11.1:

• None

Applies to:

Content user interface

Typically Implemented in:

browser, web-based user agent

Intent of Success Criterion 3.1.1:

Users who are blind, have visual impairments, or have cognitive disabilities can have difficulty determining the location of the keyboard focus. This puts them at risk of entering text in an undesired window or location. Users with mobility problems can have difficulty selecting a form field and can not notice an incorrect selection until they have entered text information.  These users need to be able to reverse a text entry ("Undo") prior to submission.

Examples for Success Criterion 3.1.1:

• Billie is a paraplegic who uses speech input. When she is working from the main office, she is in a noisy location that can interfere with her speech input.  She is writing a blog entry and is almost finished when her speech input software incorrectly interprets some background noise as a "select all" command. This causes her to overwrite her entire blog entry with the next phrase she utters. She then uses the "undo" command to reverse the text entry and restore her blog entry.
• George is blind and uses a screenreader.  He is entering financial information into his banking billpaying account.  He types the first few letters of the payee from a long list. When George reviews the selection prior to pressing "submit", he hears that he had selected the wrong payee. George uses the "undo" command and selects the correct payee.

Related Resources for Success Criterion 3.1.1:

• None

Applies to:

Configuration settings

Typically Implemented in:

browser, media player, plugin, add-on, web-based user agent

Intent of Success Criterion 3.1.2:

The description of some user interface settings can be confusing to less technical users. Settings changes can also have unintended consequences. In addition, some disabilities make it more likely that a user can make an unintended selection on a preference screen.  Users need to be able to reverse changes to the user interface.

Examples for Success Criterion 3.1.2:

• Davy has moderately low vision. He is adjusting the contrast of the background on his mobile phone when he accidentally selects a white background with the previously selected white text. This causes all the icon labels to disappear.  He can see a highlighted rectangle on the screen that usually contains the word "undo" when he makes a change on his phone. He selects that box and the dark background returns, so he can now read the text.  He then changes the background to a color with sufficient contrast for comfortable reading.

Related Resources for Success Criterion 3.1.2:

• Guideline 2.6 - Configure and store preference settings

Applies to:

UA user interface

Typically Implemented in:

browser, media player

Intent of Success Criterion 3.1.3:

Users need to know that their actions are producing results even if there is a time delay. Users with limited ability to interact with a device need a passive indicator of progress. Users who cannot see visual indications need to have feedback indicating a time delay and have an idea of where they are in the retrieval process. This reduces errors and unnecessary duplicate actions.

Examples for Success Criterion 3.1.3:

• Larry has severe repetitive strain injuries and is limited to typing for only a short period of time every day. He downloads a long document, in which he wants to search. He periodically checks the progress bar to make sure it is fully downloaded before running his search.
• Jennifer is blind and uses a screen reader. She clicks on a link that is downloading a large file. The user agent displays a programmatically available progress bar. If the progress stops, the user agent displays a message that it has timed out.
• Jennifer is blind and uses a screen reader. She purchases an item from a online shopping cart and is waiting for confirmation. The user agent displays a programmatically available message that it is waiting for a response from the server. If the process times out, the user agent displays a message that the purchase has timed out.

Related Resources for Success Criterion 3.1.3:

• 4.1.2 Expose Accessible Properties

Applies to:

Content user interface

Typically Implemented in:

browser

Intent of Success Criterion 3.1.4:

Users with various disabilities benefit from spell checkers. The ability to check spelling is particularly important for users with disabilities such as dyslexia that significantly increase the likelihood of misspelled words. Spellcheckers also alert blind and low vision users to errors in text entry.

Spell checking is only expected in editable text in content, most commonly text input controls and form fields. It is not required on text input fields that are part of the UA user interface, such as an address bar or File Open dialog box. Spell checking is also not required on static, read-only, or disabled text elements, controls, and fields in content, except when they display text the user can edit indirectly (e.g. static text that the user can alter using nearby buttons), or when the user agent is in an authoring mode that allows the user to edit text that would otherwise be static.

Spell checking should be available regardless of how the text was entered. For example, text can be entered by the user typing, pasted from the clipboard, initialized by the content (e.g. the HTML value attribute), set programmatically by scripts or assistive technology, or filled in by a feature of the user agent itself (e.g. auto-complete). Spell checking which highlights unrecognized words as they are entered is preferred over requiring the user to use a separate tool or editing pass. Spell checking should be optional, so that it can be avoided by users who find it too distracting, or for whom the highlighting makes the text less legible.

Note: It is recommended that user agents also provide assistance with grammar, as well as spelling. Grammar can pose more difficulty than spelling for people with some cognitive disabilities or whose native language is signed.

Examples for Success Criterion 3.1.4:

• Amanda is dyslexic and frequently spells words incorrectly. She is able to correct words when alerted to the errors. She navigates to her web-based email application and composes a new message. The user agent alerts her to spelling errors as she is typing and she quickly corrects the mistakes and sends an error-free message.

Related Resources for Success Criterion 3.1.4:

• None

Applies to:

Content user interface

Typically Implemented in:

browser

Intent of Success Criterion 3.1.5:

Retracing a navigation step is important for users with cognitive issues that involve memory and attention. This is also important for users whose means of input is not 100% accurate, such as speech input users or users with fine motor challenges. It is also beneficial for users for whom navigation is time consuming, tiring, or painful, because it allows them to avoid having to re-enter long URLs. The Back feature is a part of the UA user interface instead of the rendered content, however, authors should not "break" the Back button by disabling it, or creating sequences of web pages that would cause an error if the Back button were used.

Examples for Success Criterion 3.1.5:

• Joe is a quadriplegic who is using speech input in a relatively noisy room. The program hears an especially loud word from across the room and interprets it as Joe saying "Enter" to click a selected link. Joe says "Go Back" to go back to the page he was on.
• Mike's head injury leaves him easily distracted. He is in the middle of a search when the phone rings. When he comes back he selects the Back button to go back to the original search page so he can reorient himself.
• Ellen had a head injury that affects her short-term memory. She clicks on a link, and is interrupted by a colleague. When she goes back to her task she has forgotten what she was originally doing. It's important that she be able to retrace her steps to reorient herself using the history feature of the browser user interface.
• Etta has moderately low vision and doesn't use assistive technology. She occasionally clicks on the wrong link. When she does so, she clicks the Back button in order to get back to where she had been.

Related Resources for Success Criterion 3.1.5:

• 1.8.9 Provide Viewport History

Applies to:

Content user interface, Configuration settings

Typically Implemented in:

browser

Intent of Success Criterion 3.1.6:

Users need to be protected against accidentally submitting a form. Some assistive technologies use the Enter key to advance to the next field. If the form is designed to submit on Enter, the user can unknowingly "submit on Enter" function.

Examples for Success Criterion 3.1.6:

• Marka is blind and uses a screenreader. When she installs a web browser she selects an option to disable form submission on Enter. This allows her to complete forms from the banking website knowing that the form won't be submitted until she selects the submit button.
• Ryan uses a mouse but his hand tremor makes him more likely to accidentally miss his intended target. Cancel and Submit (or OK) buttons are often next to each other, and Ryan has found that submitting a form inappropriately can cause serious complications, so he sets a browser option to always request confirmation of form submissions. As a result, when he clicks on a submit button the browser presents a message box asking "Are you sure you want to submit this form?" with larger, well-spaced buttons for Submit and Cancel.

Related Resources for Success Criterion 3.1.6:

• 2.1.1 Keyboard Operation
• 3.1.1 Text Entry Undo

Applies to:

Content user interface, Configuration settings (optional)

Typically Implemented in:

browser, add-on

Intent of Success Criterion 3.1.7:

Users with various disabilities benefit from auto-fill functionality, including people who type slowly and people who have difficulty with letter/number order.

Examples for Success Criterion 3.1.7:

• Michael is dyslexic and frequently spells words incorrectly, including his name and email address. Auto-fill reduces the number of fields he must fill out in on-line forms.

Related Resources for Success Criterion 3.1.7:

• None

Applies to:

UA user interface

Typically Implemented in:

browser, add-on

Intent of Success Criterion 3.1.8:

Users who need to fill out a form over several sessions or who accidentally leave a page before a form is fully filled out need to have a way to pick up where they left off rather than having to start over again. Having the ability to retrieve a partially or fully filled out form field helps these users more successfully fill out forms. Users who have trouble remembering what they filled out need to be able to look it up. One way to provide that is through locally saved history that includes saving the form field entries.

Examples for Success Criterion 3.1.8:

• Bruno tires easily. He begins to fill out a long form, but cannot finish. He lies down to rest, and the form times out. When he comes back the browser offers to restore the locally saved session. He opts to restore the session, and goes on to fill out the rest of the form at the point where he left off. This ability allows Bruno to fill out long forms even though he can't maintain focus for the full amount of time it takes to fill out the form, and even if the form times out.
• Marjorie has severe arthritis and uses speech recognition software. Occasionally the software mishears what Marjorie says as a command she doesn't intend. She is half way through filling out a complicated form that includes many comments when the software interprets some of the words she is saying as a command to go to a different page. When she recovers from the speech input error by returning to the page a few seconds later the browser displays the form from the browser history with the data Marjorie has previously entered, but not submitted. She opts to restore the session, and goes on to fill out the rest of the form at the point where she left off rather than losing her work.
• Lara is very forgetful. She remembers that she filled out a form to comment on software she uses, but cannot remember if she included a certain comment. She retrieves the form field from her browser and checks it to remind herself. She also opts to permanently save a copy of the page that includes the form field data in case she wants to check it again.

Related Resources for Success Criterion 3.1.8:

• None

Applies to:

UA user interface

Typically Implemented in:

browser, media player, plugin, add-on, web-based user agent

Intent of Success Criterion 3.2.1:

People with disabilities need documentation in a format that is accessible. If provided as web content, it must at least conform to WCAG 2.0 level "A." If the document is not provided as web content, it must be in conformance to a published accessibility benchmark.

Examples for Success Criterion 3.2.1:

• Randall has repetitive strain injuries. His injuries make it painful to sit at the computer for long periods of time. When exploring a new program, he will often print out the documentation to read while away from his desk. This allows him to be more efficient, and learn new programs without having to spend as much computer time.
• Lee has low vision. When she upgrades her user agent, she wants to see if any features she relies on have changed. She opens the HTML help documentation and pleased to see that the documentation is using her preferred settings.

Related Resources for Success Criterion 3.2.1:

• None

Applies to:

UA user interface

Typically Implemented in:

browser, media player, plugin, add-on, web-based user agent

Intent of Success Criterion 3.2.2:

Some users with disabilities will need help in determining how to use the accessibility features that user agents provide. There are four possibilities:

1. This information is provided in the documentation of the user agent (e.g. help system, context sensitive help, etc.);
2. The user interface element is self-explanatory (e.g. a zoom % drop-down menu);
3. The accessibility feature is actually a service of the platform (e.g. high contrast mode), which therefore has the responsibility to document the feature; or
4. The feature is not used directly by users (e.g., passing information to a platform accessibility service). In this case, user documentation is not required, although developer documentation (e.g. how accessibility services are used, the user agent's own plug-in API) would still be recommended.
   

Examples for Success Criterion 3.2.2:

• Lee has low vision. When she installs a new user agent, she checks the accessibility documentation to see if the features she needs are available. She finds section entitled "Browser Features Supporting Accessibility", which provides a detailed description of user agent features that provide accessibility, describes how they function, and lists any supported third party assistive technologies that can be supported or required.
• Lee has low vision. She is exploring the menus of her user agent and finds a feature named "Use My Style Sheet". She clicks "help" to learn that this feature allows custom CSS stylesheets to be created to help make web content more accessible.
• Neta has a repetitive strain injury. She relies on gestures and shortcuts to complete tasks. Using a specialized command, she pulls up a list of all the gesture commands available including descriptions.

Related Resources for Success Criterion 3.2.2:

• 3.2.5 Centralized View

Applies to:

UA user interface

Typically Implemented in:

browser, media player, plugin, add-on, web-based user agent

Intent of Success Criterion 3.2.3:

It should always be easy to ask and receive help. The Help icon should be available to every screen, and that icon takes the user directly to relevant "how to use these features" or instructions. A symbol for help should be used (such as a question mark) or the word "help". Getting help should not be hidden — it should not be under a menu of options.

Help text for core user tasks and main or essential features should be easy to understand in simple and clear text. Each step should be identified and labeled, and pictures that clarify what to do are recommended.

A layered approach to help is beneficial to many audiences. Tooltip help is a wonderful memory aid for clarifying what user features are and particularly useful for people with an impaired working memory. Include short tooltips on all icons, jargon and shortened forms such as abbreviations. Typically these tooltips should be one or two words long.

Examples for Success Criterion 3.2.3:

• Lotte has low vision and uses a screen magnifier on her smartphone. She wants to email a colleague the link to the blog article she is reading, but cannot find the feature. She taps an icon on her phone with a large red question mark, and types "email link" in the search box that appears. She reads the directions for emailing a link, returns to the article, and successfully emails the link.
• Benecio has a learning disability, and cannot remember what toolbar icons stand for. He uses his mouse to display the tooltip with the name of each icon until he discovers the Print icon.

Related Resources for Success Criterion 3.2.3:

• None

Applies to:

UA user interface

Typically Implemented in:

browser, media player, plugin, add-on, web-based user agent

Intent of Success Criterion 3.2.4:

Users need to be informed about accessibility features implemented in new versions of the user agent.

Examples for Success Criterion 3.2.4:

• Martha has memory problems. She finds it difficult to remember what the icons on her computer do and relies heavily on tool tips. She goes to an app store on her computer and installs an update for her web browser. After it installs, she sees a welcome page describing the new features in this release. One of the welcome page links is titled "What's New For Accessibility". Following this link, Martha reads about the accessibility improvements and discovers a feature that allows her to have tooltips displayed for elements when she is using caret browsing. The text also informs Martha that this feature is off by default and that she should go to accessibility settings to turn it on.

Related Resources for Success Criterion 3.2.4:

• None

Applies to:

UA user interface

Typically Implemented in:

browser, media player, plugin, add-on, web-based user agent

Intent of Success Criterion 3.2.5:

Users need to know about accessibility features and how to operate them. A centralized view of accessibility features makes it easier for people with disabilities and people who are evaluating software to quickly become familiar with the features such as keyboard shortcuts, how to zoom the viewport, and where to find accessibility configuration settings. Nested user agents or add-ons can provide separate centralized documentation. It is also useful to document accessibility features in context (such as displaying keyboard shortcuts next to their menu command).

Examples for Success Criterion 3.2.5:

• Bob is blind and uses a screen reader that is part of his phone's operating system. He downloads a new web browser on his mobile phone. The browser's online help includes a section on accessibility that point him to pages on non-visual access, such as interaction with screen readers, helpful hints such as an explanation of the screen layout, and a list of supported touch gestures.
• Marissa is assessing new user agents for clients who are blind. The first thing she does in looking at each user agent is to turn to the section in the documentation (local or online) that details accessibility features. This gives her a quick overview of the accessibility features across different products.

Related Resources for Success Criterion 3.2.5:

• None

Applies to:

Content user interface, Configuration settings (optional)

Typically Implemented in:

browser, media player, plugin

Intent of Success Criterion 3.3.1:

Users need to know that navigation in a web page is going to start in a predictable location and move in a predictable fashion. If a page moves the initial focus to somewhere other than the beginning of the page, the user can skip over content without realizing it. If the focus moves and remains unnoticed, users can make unintentional changes, such as entering data in an incorrect field. Focus changes can cause a window to scroll unexpectedly, confusing users. This is particularly problematic for users who can only see a small portion of the document, because they must use more effort to determine where the cursor has moved. Such users also are more likely to continue typing, not immediately realizing that the context has changed. Users who find navigation time consuming, tiring, or painful (including those using screen readers or with impaired dexterity) can also need more steps to return to the area where they want to work. It can improve accessibility for some users on some pages to have the page set focus to specific links or fields when the page loads, but this can be detrimental for other users, and therefore users need to control this behavior.

Examples for Success Criterion 3.3.1:

• Jerome has repetitive strain injuries. He tries to limit the number of keyboard and mouse entries he makes each day, because it is painful. He loads a page that has its default focus in a search box. Jerome wants to read the content of the page, rather than search. This requires him to make additional clicks to get to the content of the page. He intends to use this page frequently, so he adjusts his browser's settings to disable the automatic focus change to prevent the extra clicking in the future.
• Jessica uses a screen enlarger. She loads a page that contains instructions followed by a form. If the page automatically moves the keyboard focus to the form, she may not realize there were instructions. To avoid this problem, she sets an option to prevent default focus changes.
• James was born without hands and uses speech input. He speaks his credit card number by saying several digits followed by speaking "tab". He needs to know ahead of time whether it is necessary to include the "tab" command in the phrase.
• Joey is blind and uses a screenreader. She is filling in a web form that asks for her phone number using three separate fields. When she types the three digits of her area code into the first field, the browser automatically moves the focus to the second field. Because Joey does not realize that the focus has moved for her, she presses the Tab key to move it manually, not realizing that this now puts the focus on the third field rather than the second. To avoid this problem, Joey goes to her browser's Preferences dialog box and checks the option that prevents focus changes that she has not explicitly requested.
• Justine has trouble using a mouse. She uses a keyboard macro in her web email program to execute a command to start a new message and put a block of text in the new message. The focus moves without her control, causing the macro to execute in the Inbox instead of the Compose window. With the Inbox in focus several single-key shortcuts execute, changing the column sorting and deleting several messages.

Related Resources for Success Criterion 3.3.1:

• 1.3.1 Highlighted Items
• 1.8.10 Allow Top-Level Viewport Open on Request
• 1.8.11 Allow Top-Level Viewport Focus Control
• 2.1.4 Separate Selection from Activation

Applies to:

Communication with platform accessibility services

Typically Implemented in:

browser, media player, plugin

Intent of Success Criterion 4.1.1:

Platform accessibility services provide common functionality across the well-behaved applications running on the platform. This reduces exceptions that assistive technology has to implement for the hundreds of applications it may need to support. Most major operating environments provide platform accessibility services that allow applications to work with assistive technologies. These platform accessibility services must be supported by both the user agent and the assistive technology. Specifics of what constitutes a platform accessibility service will differ on each platform, but basic features common to these services are addressed by other success criteria under Guideline 4.1.

Most web-based user agents support this requirement automatically because they run inside host user agents. The host is responsible for exposing all content, including nested user agents, via platform accessibility services. As long as the nested user agent's user interface is entirely web-based and complies with Web Content Accessibility Guidelines (e.g. providing alternative text and supporting WAI-ARIA where needed) the host will understand it well enough to provide a bridge between the content and platform accessibility services.

Examples for Success Criterion 4.1.1:

• Jamie is blind and uses a screenreader. He is testing a new type of button bar for a browser. When coding the new component, the developer supported the relevant platform accessibility services so that Jamie's screenreader can recognize it as a toolbar, and Jamie can identify, navigate, and activate the bar and its buttons.

Related Resources for Success Criterion 4.1.1:

• 4.1.2 Expose Accessible Properties for specific information that should be exposed through platform accessibility services.
• Microsoft Active Accessibility (MSAA)
• Microsoft UI Automation
• Gnome Accessibility Toolkit (ATK)
• GNOME Accessibility Architecture (ATK and AT-SPI)
• Accessibility Programming Guidelines for Mac (may require developer account)
• Accessibility Programming Guide for iOS (may require developer account)
• Iaccessible2
• Open Source Accessibility for Windows
• Accessibility API Cross reference
• HTML Accessibility API Mappings 1.0

• Core Accessibility API Mappings 1.1

• SVG Accessibility API Mappings

• Accessible Name and Description: Computation and API

• HTML to Platform Accessibility APIs Implementation Guide

Applies to:

Communication with platform accessibility services

Typically Implemented in:

browser, media player, plugin @Core

Intent of Success Criterion 4.1.2:

Modern web content is highly interactive. Including people who use assistive technology in the interactive experience requires that the user agent provide information about user interface components in a standardized manner. This information includes:

• Name (component name)
• Role (purpose, such as alert, button, checkbox)
• State (current status, such as busy, disabled, hidden)
• Value (information associated with the component such as, the data in a text box, the position number of a slider, the date in a calendar widget)
• Focus (has focus, focusable)
• Selection (selected, selectable)

Every component developed for the user agent must pass this information to the appropriate accessibility platform architecture or application program interface (API). Embedded user agents, like media players can pass Name, Role, State, and Value via the WAI-ARIA techniques. Since not every element supports every property, follow the platform accessibility services convention for cases where an element type does not support one of the listed properties.

Examples for Success Criterion 4.1.2:

• Jamie is blind and uses a screenreader. He adjusts the volume on a web site media player using a slider control. This is easy for him to do because the developer has coded the slider component with WAI-ARIA techniques to pass the following information to the accessibility service:
  Name: Volume control
  Role: Slider
  States & Values:
  • aria-valuenow is the slider’s current value.
  • aria-value-min is the minimum of the volume range
  • aria-value-max is the maximum of the volume range

Related Resources for Success Criterion 4.1.2:

• 1.10.1 Show Related Elements
• ARIA Relationships [ARIA10]
• Core Accessibility API Mappings 1.1

• SVG Accessibility API Mappings

• Accessible Name and Description: Computation and API

Applies to:

UA user interface

Typically Implemented in:

browser, media player, plugin

Intent of Success Criterion 4.1.3:

Like everyone else, users who rely on assistive technology need to be able to carry out all tasks provided by the user agent. When a particular user interface component cannot support the platform accessibility service, and thus can't be made compatible with assistive technology, the user agent should let the user achieve the same goal using another component that is fully accessible.

Examples for Success Criterion 4.1.3:

• Xanni is a screen reader user. She wants to bookmark the current page. Her browser allows a bookmark icon to be dragged with a mouse into the current document to bookmark the location. This functionality cannot be accessed effectively with her screen reader. However, the browser does allow her to add a bookmark from the context menu at the current focus.
• Doug uses a mouse-stick on his smart phone. He uses the assistive touch option on his mobile phone to control an app for 3D design drawing. The app provides a single, complex control for 3-dimensional manipulation of a virtual object. This custom control cannot be represented in the platform accessibility service, so the app provides Doug the option to achieve the same functionality through an alternate user interface: a panel that adjusts the yar, spin, and roll independently using arrow keys.

Related Resources for Success Criterion 4.1.3:

• None

Applies to:

Communication with platform accessibility services

Typically Implemented in:

browser, media player, plugin @Core

Intent of Success Criterion 4.1.4:

Assistive technologies need all possible information. Applications such as user agents and assistive technologies use a combination of DOMs, Accessibility Application Programming Interfaces (AAPI), native platform APIs, and hard-coded heuristics to provide an accessible user interface and accessible content. While most assistive technology vendors prefer to use the AAPIs, if the AAPI cannot provide enough access to the content, then it is the user agent's responsibility to expose the DOM to assistive technology.

What is "sufficient" information can be determined by using the WAI ARIA Accessibility API Mappings:

• Core Accessibility API Mappings (CORE-AAM)
• HTML Accessibility API Mappings (HTML-AAM)
• Accessible Name and Description: Computation and API Mappings (ACCNAME-AAM)
• SVG Accessibility API Mappings (SVG-AAM)

Examples for Success Criterion 4.1.4:

• Joey is blind and uses a screenreader. He is reading a long technical article where code samples are labeled using CSS. In the past, he has had trouble reading technical articles because the CSS text is not exposed to the the platform accessibility service, and is therefore missing from his text. His new browser exposes the CSS DOM information to the platform accessibility services. This allows him to read and search on all of the code sample labels.
  
• Joey is blind and uses a screen reader. He is reading a compound document containing HTML, MathML, and SVG. Each has a separate DOM. As Joey moves through the document, he is moving through multiple DOMs. He has no trouble reading it because the transition between DOMs is seamless and transparent.

Related Resources for Success Criterion 4.1.4:

• Core Accessibility API Mappings (CORE-AAM)
• HTML Accessibility API Mappings (HTML-AAM)
• Accessible Name and Description: Computation and API Mappings (ACCNAME-AAM)
• SVG Accessibility API Mappings (SVG-AAM)

Applies to:

Communication with platform accessibility services

Typically Implemented in:

browser, media player, plugin @Core

Intent of Success Criterion 4.1.5:

If users can control the user interface using any form of input, they can control it through programmatic access. It is often more reliable for assistive technology to use the programmatic method of access versus attempting to simulate mouse or keyboard input.

Examples for Success Criterion 4.1.5:

• Billie is a quadriplegic who uses speech input. When she says "Volume 35" her speech input utility programmatically sets the value of the volume slider to 35%. This allows Billie to set the volume in a single command to a specific value rather than simulating mouse clicks.
• Billie is a quadriplegic who uses speech input. She uses a direct speech command to set the value of a check box in the user agent preference settings to block pop up windows. Even though the control cycles through “checked”, and “unchecked” using the spacebar or mouse, the speech command uses a programatic command to check the box regardless of whether the box is already checked.

Related Resources for Success Criterion 4.1.5:

• None

Applies to:

UA user interface, Content user interface

Typically Implemented in:

web-based user agent (readers, players)

Intent of Success Criterion 5.1.1:

User agent user interfaces that are web-based must meet the same accessibility guidelines as web content. The Web Content Accessibility Guidelines (WCAG) 2.0 are an internationally accepted guideline for accessible web content.

Examples for Success Criterion 5.1.1:

• Lee has low vision. She needs to customize the appearance of her web-based media player. WCAG 2.0 success criteria 2.7.1 requires that a user agent enable a user to change settings that impact accessibility. Her web-based media player enables her to change accessibility settings to display high contrast captions.

Related Resources for Success Criterion 5.1.1:

• WAI-ARIA 1.0 User Agent Implementation Guide
• W3C Web Design and Applications Activity
• WCAG 2.0

Applies to:

Content user interface

Typically Implemented in:

browser, media player, plugin, add-on, web-based user agent (readers, players)

Intent of Success Criterion 5.1.2:

Most content specifications include features important to users with disabilities. Users can find it difficult or impossible to use a product that fails to support those features. Conformance claim documents list the technologies that the user agent fully supports, such as WAI-ARIA, so that users can make informed decisions about whether or not they will be able to use, and therefore should install, a new product or version of that product.

Examples for Success Criterion 5.1.2:

• Jordy is blind and uses a screenreader. He often uses a website that is coded with WAI-ARIA to identify the functions of custom controls. He is downloading a new version of a web browser. If the browser doesn't support WAI-ARIA and expose that information to assistive technology, the website would be unusable. Before he installs the new browser, Jordy makes sure it fully supports WAI-ARIA. He determines this by reading product documentation and UAAG conformance claims posted on the web.

Related Resources for Success Criterion 5.1.2:

• [WCAG20]
• HTML- - listing of the HTML documents
• CSS - listing of the CSS documents
• WAI-ARIA Suite Overview
• Components of a UAAG 2.0 Conformance Claim See #9 Web Content Technologies

Applies to:

UA user interface, Content user interface

Typically Implemented in:

browser, media player, plugin

Intent of Success Criterion 5.1.3:

User agent user interfaces that are not web applications need to be accessible to people with disabilities. Accessibility guidelines already exist for many platforms. Most operating systems have conventions and expectations that aid accessibility, such as keyboard behavior, support of an accessibility service, user interface design. User agents need to comply with the basic accessibility requirements of the platform in use. Developers have the flexibility to conform with the appropriate accessibility guidelines or legislation for their platform or markets.

The user should be able to easily discover detailed information about the user agent's adherence to accessibility standards, platform standards such as MSAA or JAA, and third-party standards such as ISO 9241-171, and should be able to do so without installing and testing the accessibility features.

Note: In the conformance claim, list the requirements you fully comply with, list the requirements you partially comply with and explain, and list the requirements you do not comply with and explain. Where applicable, these explanations can be general and cover several sections at once.

Examples for Success Criterion 5.1.3:

• Lee has low vision and uses a screen magnifier on a Linux system. She loads a new Gnome application that works with her screen magnifier because the developer followed the Gnome Accessibility Developers Guide. For example, the Keyboard Focus section states: "Show current input focus clearly at all times. Remember that in controls that include a scrolling element, it is not always sufficient to highlight just the selected element inside that scrolling area, as it may not be visible. " Lee can use this app because it conforms to this accessibility guideline for focus.
• Martin uses a mouth stick to control his mobile browser. Even though he cannot use a pinch gesture, he controls the zoom in his mobile browser with a custom gesture. He can do this because the app developer followed the guidance provided in the "Accessibility Programming Guide for iOS".
• Sasha requires high contrast to be able to discriminate the shape of letters. She has set the accessibility preferences on her computer to use high contrast mode. When she launches her browser, it detects that she is using high contrast and adjusts the font and color settings for its user interface to reflect those settings.

Related Resources for Success Criterion 5.1.3:

[APPLE-ACCESS]

"Introduction to Accessibility Overview," Apple Computer Inc. (may require login)

[CARBON-ACCESS]

"Accessibility and the Carbon Framework," Apple Corporation (may require login)

[EITAAC]

"EITAAC Desktop Software standards," Electronic Information Technology Access Advisory (EITAAC) Committee.

[GNOME-ACCESS]

"GNOME Accessibility for Developers," C. Benson, B. Cameron, B. Haneman, S. Snider, P. O'Briain, The GNOME Accessibility Project.

[GNOME-API]

"Gnome Accessibility Toolkit API"

[GNOME-KDE-KEYS]

"Gnome/KDE Keyboard Shortcuts," Novell Corporation.

[IBM-ACCESS]

"Software Accessibility," IBM Special Needs Systems.

[IEC-4WD]

IEC/4WD 61966-2-1: Colour Measurement and Management in Multimedia Systems and Equipment - Part 2.1: Default Colour Space - sRGB. May 5, 1998.

[ISO-TS-16071]

"Ergonomics of human-system interaction -- Guidance on accessibility for human-computer interfaces". International Organization for Standardization.

[JAVA-ACCESS]

"IBM Guidelines for Writing Accessible Applications Using 100% Pure Java," R. Schwerdtfeger, IBM Special Needs Systems.

[JAVA-API]

" Java Accessibility Package"

[JAVA-CHECKLIST]

"Java Accessibility Guidelines and Checklist," IBM Special Needs Systems.

[MACOSX-KEYS]

"Mac OS X keyboard shortcuts," Apple Corporation.

[MS-ENABLE]

"Designing Accessible Applications," Microsoft Corporation.

[MS-WIN7-ACCESS]

"Engineering Software For Accessibility", Microsoft Corporation.

[MS-KEYS]

"Keyboard shortcuts for Windows," Microsoft Corporation.

[NOTES-ACCESS]

"Lotus Notes application accessibility," IBM Corporation.

[ORACLE-DESIGN]

"Designing for Accessibility," Eric Bergman and Earl Johnson. This paper discusses specific disabilities including those related to hearing, vision, and cognitive function.

Applies to:

UA user interface

Typically Implemented in:

operating system, browser, media player, plugin, add-on, web-based user agent (readers, players)

Intent of Success Criterion 5.1.4:

When accessing media or specialized content (e.g. MathML) on the web, users with disabilities can have a richer or more accessible experience using a third-party application, plug-in, or add-on, rather than using the browser's built-in facilities. Users need to be able to enable or activate a browser plug-in or add-on to interact with the content. Alternately, they can elect to save that content to disk and launch it in a third-party application. If streaming video cannot be saved to disk, the browser launches the external viewer, passing it the URI to the online video.

Examples for Success Criterion 5.1.4:

• George is blind. His browser supports the VIDEO tag and adds its own play and pause controls, but George prefers to view the video content in a third-party application that provides much more sophisticated navigation controls such as bookmarks, skip-forward and backwards, and the ability to speed playback without increasing pitch of the audio track. In the browser, he right-clicks on the video to display a context menu, and from that chooses "Open in…", and then chooses his preferred video player. The browser launches the player to show that video file.
• Jukka is blind and uses a screenreader. He is a scientist whose uses mathematical models. Many of the journals he reads online use MathML to display equations. Jukka finds the native support for MathML accessibility in his web browser to be generally compatible with his screen reader, but it can become unreliable for extremely complex equations. In those cases, Jukka selects an alternate rendering plug-in to make the MathML understandable to his screen reader.
  

Related Resources for Success Criterion 5.1.4:

• None

Applies to:

UA user interface

Typically Implemented in:

operating system, browser, media player, plugin, add-on, web-based user agent (readers, players)

Intent of Success Criterion 5.1.5:

People who use assistive technologies such as screen readers can find that a technology isn't fully compatible with a web browser, or that the content authored to meet WCAG still is not accessible when rendered in the browser. This causes information loss and inconvenience. When this happens, users benefit from being able to easily file a report with the user agent vendor to report the incompatibility, similar to the way users can file bug reports or provide feedback.

Examples for Success Criterion 5.1.5:

• Alice is a visually impaired college student who frequently uses a refreshable braille display with her web browser. She experiences difficulty with a drop-down list boxes because the text is only partially rendered on her braille display. When Alice notices this incompatibility, she navigates to the feedback section of her browser. After providing some basic information (such as AT software and computer hardware used), Alice describes the problem and submits the report to the browser vendor.
• Fred has low vision and uses screen magnification software to enlarge displayed information and alter color contrast. While reading content on a website in compliance with WCAG, Fred discovers that the scroll bars are not visible and he cannot scroll further down the page. Unable to read the information he needs, Fred selects the Feedback option from his browser's Tools menu, and is presented with a dialog where he can select which information to transmit to the browser vendor. He includes the current URI of the page he is trying to view, system information including OS and screen magnifier version, and enters a description of the problem he is having. Though not required, Fred chooses to provide his email address so that the vendor can contact him for further details or to provide a workaround.

Related Resources for Success Criterion 5.1.5:

• None