Implementing UAAG 2.0

1.1.1 Render Alternative Content [was 1.1.3]:

For any content element, the user can choose to render any types of alternative content that are present. (Level A) ## DONE 28 March 2012

• Intent of Success Criterion 1.1.1:
  Alternative content is wasted if users cannot find it. The user agent should make the presence of alternative content evident to the user. Users should not have to hunt and examine every time to see if it includes such content, because such searching can be time-consuming, especially for users whose disability makes input difficult, tiring, or painful. The user should be able to easily identify which items have alternative content, rather than being merely informed that alternative content is somewhere in the view.
• Examples of Success Criterion 1.1.1:
  • Tinan has repetitive strain injuries and seeks to limit scrolling. The user agent renders distinct visual icons in proximity of content that has short text alternatives, long descriptions, and captions. If the icon forces the text to extend beyond a fixed size container the user agent uses global preference settings to determine whether to expand the container, provide scroll bars, or truncate the content.
  • 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.1:
  • None

1.1.2 Configurable Alternative Content Defaults [was 1.1.1]:

For each type of non-text content, the user can specify a type of alternative content that, if present, will be rendered by default. (Level AA) ## DONE 28 March 2012

• Intent of Success Criterion 1.1.2:
  Alternative content is wasted if the user agent doesn't render it for users who need it. Default alternative content is a global option because it is an unreasonable burden for users to change the rendering options every time they visit a new page.
• Examples of Success Criterion 1.1.2:
  • Sally is blind. In the browser's preferences dialog box, Sally specifies that she wants alt text displayed in place of images, and that the document should 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 videos.
  • $$ Ben has low vision. In the mobile settings dialog box, he chooses to always display the alternative ("fallback") content for embedded objects, such as images. Images become pixelated so on the mobile phone, so he prefers the text version of the images.
  • 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.2:
  • None

1.1.3 Display of Time-Based Media Alternatives:

For recognized on-screen alternatives for time-based media (e.g. captions, sign language video), the following are all true: (Level AA)## DONE 2 August 2012

1. Do not obscure primary media: The user can specify that displaying media alternatives doesn't obscure the primary time-based media; and
2. Do not obscure controls: The user can specify that the displaying media alternatives doesn't obscure recognized controls for the primary time-based media; and
3. Configurable text: The user can configure recognized text within media alternatives (e.g. captions) in conformance with 1.4.1.

Note: Depending on the screen area available, the display of the primary time-based media may need to be reduced in size to meet this requirement.

• Intent of Success Criterion 1.1.3 [was 2.11.11]:
  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 of Success Criterion 1.1.3:
  • 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. Justin 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.
  • $$ 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.3:
  • 1.4.1 Configure Rendered Text

1.1.3 [old] Indicate Unrendered Alternative Content:

## DONE 28 March 2012 ## Deleted 4 June 2012

1.1.4 Default Rendering of Alternative Content (Enhanced):

For each type of non-text content, the user can specify the cascade order in which to render different types of alternative content when preferred types are not present. (Level AAA) ## DONE 28 March 2012

• Intent of Success Criterion 1.1.4:
  For a given piece of non-text content the author may provide one or more alternatives. For example, an image may have different versions based on resolution, ‘alt text’ (@alt) or a link to a long description (@longdesc). A video may have bandwidth alternatives, caption files in different languages, and audio descriptions in different languages. Users can choose which item(s) to render by default, and specify the order of the cascade of alternatives to be rendered if the author provided multiple alternatives.
• Examples of Success Criterion 1.1.4:
  • Mary has a learning disability. She finds looking at images on a webpage very distracting. Mary would like to see all images rendered in the following order: First, for images with long descriptions, render the long description in place of the image. If the long description does not exist, render the ‘alt text’. If neither is available, render the file name. Added functionality would allow Mary to right click (context menu) on an image to list and select the preferred order of available alternatives (thumbnail, original size, full screen, low resolution, high resolution, alt text, long description, file name).
  • Juan is hard of hearing. He always wants to see video on the page. Juan wants to use the Spanish language track and Spanish captions as a default. If these are not available, he wants to see the video with English audio and captions. If no captions are available, Juan wants video with English audio. Added functionality would allow Juan to right click (context menu) on an video to list and select the preferred order of the available alternatives (still image, caption languages, audio languages, audio-description languages).
  • $$ Ben has low vision and prefers to display the longer alternative content (@alt or @title) on his desktop browser where his display allows. When using his mobile device, Ben has configured his device to display the shortest alternative content available for non-text content.
• Related Resources for Success Criterion 1.1.4:
  • Guideline 1.1 Text Alternatives and Guideline
  • WCAG 2.0 Guideline 1.2 Time-based Media

1.1.5 Size and Position of Time-Based Media Alternatives:

The user can configure recognized on-screen alternatives for time-based media (e.g. captions, sign language video) as follows: (Level AAA)

1. The user can resize the media alternatives up to the size of the user agent's viewport.
2. The user can reposition the media alternatives to at least above, below, to the right, to the left, and overlapping the primary time-based media.

Note 1: Depending on the screen area available, the display of the primary time-based media may need to be reduced in size or hidden to meet this requirement.

Note 2: Implementation may involve displaying media alternatives in a separate window, but this is not required.

## DONE 2 August 2012 and IER on 16 August

• Intent of Success Criterion 1.1.5:
  Users may 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 of Success Criterion 1.1.5:
  • Maximilian 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.
  • When Tom watches narrow-aspect video on a wide-aspect screen, 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.
  • Raymond has one functioning hand. He positions captions so that they're not covered by the hand he's using to hold his tablet.
  • $$ 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.5:
  • None

1.2.1 Support Repair by Assistive Technologies:

If text alternatives for non-text content are missing or empty then both of the following are true: (Level AA)

1. the user agent does not attempt to repair the text alternatives with text values that are also available to assistive technologies.
2. the user agent makes metadata related to the non-text content available programmatically (and not via fields reserved for text alternatives).

## DONE 19 April

• Intent of Success Criterion 1.2.1:
  When alternative content is missing, it is sometimes useful for users to have access to alternative information, such as the filename. Users need to control the flow of this information, because an uncontrolled flow can be distracting and time-consuming. This is particularly important for users who can't use some forms of content (e.g. images) or may need to avoid some forms of content (e.g. animations) and replace them with alternative content.
  
  Users need to control the flow of the content when this information is added, because truncating the content to fit its container may make the document unusable (e.g. if important information becomes hidden). In other cases, expanding the container will make the document unusable (e.g. when important cues no longer line up correctly).
  
  Note that repair text is only required for alternative content for images. For example, it would not require the user agent to generate a transcript of audio using speech recognition.
• Examples of Success Criterion 1.2.1:
  • Ray is blind and counts on alternative text descriptions for images. There is an image in web content that does not have alternative text provided. The browser displays the string '(image canoe.png)', which includes the file name because that is the only available information about the image.
  • Bintu is deaf and relies on captions to replace audio. Bintu selects a caption button for a video she wants to watch, and is informed that no captions exist. The player then analyzes the video soundtrack and provides speech-to-text translation served as captions. Note: this is an advanced example, not a requirement.
• Related Resources for Success Criterion 1.2.1:
  • Evaluating Web Sites for Accessibility: Overview

1.2.2 Repair Missing Structure:

The user can specify whether or not the user agent should attempt to insert the following types of structural markup on the basis of author-specified presentation attributes (e.g.. position and appearance): (Level AAA) ## DONE 19 April & IER done on 2 August 2012

1. Labels
2. Headers (e.g. heading markup, table headers)

• Intent of Success Criterion 1.2.2:
  When an author neglects to provide labels and/or headers as necessary for accessibility, the user agent can sometimes use heuristics to determine potential labels and/or headers from presentation attributes. Once potential headings and/or labels have been identified, the user agent can proceed (e.g. with communication via platform accessibility services) as if the relationship was defined in the markup. The user can specify whether heuristics should be applied because some users want to experience the content as the author provided it (e.g. to perform evaluations or when heuristics fail).
• Examples of Success Criterion 1.2.2:
  • Frank uses speech input. When content markup includes a checkbox without a specified label, the user agent detects that a static text component is positioned immediately to the right of the checkbox and no other static text components are nearby. The nearby text is treated as the label. This enables George to toggle the checkbox by speaking its name.
  • Maria uses a screen reader. When a table lacks marked up header rows, the user agent gives her the option to have the first row treated as the table header row.
  • Li uses a scanning keyboard and makes use of the user agent's outline view to more efficiently navigate web pages. The content markup includes instances of static text that differ from surrounding text because they are sentence fragments and styled with a larger font and bold weight. The instances are treated as headings as therefore appear in the outline view, enabling Li to more efficiently navigate to them.
• Related Resources for Success Criterion 1.2.2:
  • Understanding WCAG 2.0: Heading and Labels

1.3.1 Highlighted Items:

The user can specify that the following classes be highlighted so that each is uniquely distinguished: (Level A)## DONE 5 April 2012## DONE 4 June 2012

1. selection
2. active keyboard focus (indicated by focus cursors and/or text cursors)
3. recognized enabled input elements (distinguished from disabled elements)
4. elements with alternative content
5. recently visited links

• 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 working. On some pages controls may be difficult to discern amid a large amount of other content, or may 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 may 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: 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: Platform conventions will dictate whether or not keyboard focus in an inactive viewport is visually indicated by an inactive cursor.
  Note: the definition of visited and unvisited links is up to the user agent. Visited links may be links visited during the current session or in the browser's history.
• Examples of Success Criterion 1.3.1:
  • Jerry has low vision. He goes to a website that uses styles 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 the author styles so visited links are indicated.
  • Jerry 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 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.
• 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

1.3.2 Highlighting Options:

When highlighting classes specified by 1.3.1 Highlighted Items, the user can specify highlighting options that include at least: (Level AA) ## DONE 12 April 2012

1. foreground colors,
2. background colors, and
3. borders (configurable color, style, and thickness)

• 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 of 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

1.4.1 Configure Rendered Text:

The user can globally set any or all of the following characteristics of visually rendered text content, overriding any specified by the author or user agent defaults: (Level A) ## DONE TPAC

1. text scale (the general size of text)
2. font family
3. text color (foreground and background)
4. line spacing
5. character spacing

• Intent of Success Criterion 1.4.1:
  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 may increase font size to make text more legible, while other users may reduce the font size to decrease the need to scroll the content.
• Examples of Success Criterion 1.4.1:
  • Lee has low vision from albinism and has difficulty with screen resolution and brightness. She chooses to have all text displayed in Palatino font, with white text on a black background, and at least 16-points. The serif Palatino font has character spacing that resolves better for her vision, while the white on black reduces glare and the larger size allows her to distinguish fine detail more clearly.
  • Lee uses a browser on her mobile phone that supports only 3 font sizes: small, medium, and large. Lee needs to use a font size of 16 pt, which is between the medium and large sizes. The mobile phone settings provide an option to override the 3 font sizes with the operating system font range, so that Lee can select the 16 pt font size she needs.
  • Mike has a reading disability. A website uses a fancy script font for the headings that he cannot understand. He chooses to have all text displayed in a plain font that he can read.
  • $$ Ben has low vision. In the mobile settings dialog box, he chooses to large text for font size. All applications on the mobile phone display text in large font.
• Related Resources for Success Criterion 1.4.1:
  • Guideline 1.7 Enable Configuration of User Stylesheets

1.4.2 Preserving Size Distinctions:

The user can specify whether or not distinctions in the size of rendered text are preserved when that text is rescaled (e.g. headers continue to be larger than body text). (Level A) ## DONE TPAC

• Intent of Success Criterion 1.4.2:
  The relative size of text provides visual cues that help in understanding and navigating web content. Some content may be authored in a way that makes it difficult or impossible to understand when font distinctions were hidden, such as headlines that are 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. It is also important that magnification users who find that text size distinction greatly increases scrolling and fatigue be able to display all text at the same size.
• Examples of Success Criterion 1.4.2:
  • Lee 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. She needs the headlines to scale proportionally (e.g. 24 pt) in order to preserve headline prominence.
  • 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.
• Related Resources for Success Criterion 1.4.2:
  • Guideline 1.7 Enable Configuration of User Stylesheets

1.5.1 Global Volume:

The user can independently adjust the volume of all audio tracks, relative to the global volume level set through operating environment mechanisms. (Level A) ## DONE 3 May 2012

• Intent of Success Criterion 1.5.1:
  User agents can render audio tracks from a variety sources, and in some cases, multiple audio tracks may 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 of Success Criterion 1.5.1:
  • An operating system provides a master audio volume control that applies to all audio tracks rendered within the environment, including the user agent. The user may define a default volume level through a preferences dialog that is retained across sessions.
  • A user encounters a page with two advertisements and one video which begins playback on page load complete. A global mute command, supported via a mute key on the user's keyboard, allows the user to immediately silence the playing audio tracks.
• Related Resources for Success Criterion 1.5.1:
  • None

1.6.1 Speech Rate, Volume, and Voice:

If synthesized speech is produced, the user can specify the following: (Level A) ## DONE TPAC

1. speech rate,
2. speech volume (independently of other sources of audio), and
3. voice, when more than one voice option is available

1.6.2 Speech Pitch and Range:

If synthesized speech is produced, the user can specify the following if offered by the speech synthesizer: (Level AA)## DONE TPAC. Updated 4 October 2012

1. pitch (average frequency of the speaking voice), and
2. pitch range (variation in average frequency)

Note: Because the technical implementations of text to speech engines vary (e.g., formant-based synthesis or concatenative synthesis), a specific engine may not support varying pitch or pitch range. A user agent will expose the availability of pitch and pitch range control if the currently selected or installed text to speech engine offers this capability.

1.6.3 Advanced Speech Characteristics:

The user can adjust all of the speech characteristics offered by the speech synthesizer. (Level AAA)## DONE TPAC

• Intent of Success Criterion 1.6.1, 1.6.2, 1.6.3:
  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 of Success Criterion 1.6.1, 1.6.2, 1.6.3:
  • 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 a 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 Criterion 1.6.1, 1.6.2, 1.6.3:
  • None

1.6.4 Synthesized Speech Features:

If synthesized speech is produced, the following features are provided: (Level AA) ## DONE TPAC

1. user-defined extensions to the synthesized speech dictionary,
2. "spell-out", where text is spelled one character at a time, or according to language-dependent pronunciation rules,
3. at least two ways of speaking numerals: spoken as individual digits and punctuation (e.g. "one two zero three point five" for 1203.5 or "one comma two zero three point five" for 1,203.5), and spoken as full numbers are spoken (e.g. "one thousand, two hundred and three point five" for 1203.5),
4. at least two ways of speaking punctuation: spoken literally, and with punctuation understood from natural pauses.

• Intent of Success Criterion 1.6.4:
  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 of Success Criterion 1.6.4:
  • Penny has a reading disabililty. 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's 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.4:
  • None

1.7.1 Support User Stylesheets:

If the user agent supports a mechanism for authors to supply stylesheets, the user agent also provides a mechanism for users to supply stylesheets. (Level A)

1.7.2 Apply User Stylesheets:

If user style sheets are supported, then the user can enable or disable user stylesheets for: (Level A)## DONE 9 August 2012

1. all pages on specified websites, or
2. all pages

1.7.3 Author Style Sheets:

If the user agent supports a mechanism for authors to supply stylesheets, the user can disable the use of author style sheets on the current page. (Level A)## DONE 9 August 2012

• Intent of Success Criterion 1.7.1, 1.7.2 & 1.7.3:
  CSS stylesheets allow users and authors to customize the rendering of web content. 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 of Success Criterion 1.7.1, 1.7.2 & 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.
  • Tanya 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 text 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 ADHD and finds text easiest to read text if text is highlighted in blue as it is being read out loud. 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 Criterion 1.7.1, 1.7.2 & 1.7.3:
  • CSS 2 Recommendation: cascade weight rules
  • Custom Styles for IOS
  • STylish for FF and Chrome
  • Web Developer for Firefox and Chrome

1.7.4 Save Copies of Stylesheets:

The user can save copies of the stylesheets referenced by the current page, in order to edit and load the copies as user stylesheets. (Level AA)

• 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 CSS 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.
• Examples of 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 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

1.8.1 Highlight Viewport:

The viewport with the input focus is highlighted and the user can customize attributes of the highlighting mechanism (e.g. shape, size, stroke width, color, blink rate). The viewport can include nested viewports and containers. (Level A) ## DONE TPAC - edited by K & J 30 August 2012.

• 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. These users need to customize highlighting of viewport frames using color, contrast, and border thickness to provide multiple visual cues.
• Examples of 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:
  • None

1.8.2 Move Viewport to Selection and Focus:

When a viewport's selection or input focus changes, the viewport's content moves as necessary to ensure that the new selection or input focus location is at least partially in the visible portion of the viewport. (Level A) ## DONE TPAC

• 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 of 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, requiring George to scroll vertically to view the complete form content. When George completes each form entry, if the next form is not already visible in the viewport, it scrolls into view.
  • $$ Lee typically views web content on her mobile phone at a high level of zoom, frequently positioning elements outside the viewport. When moving between focusable elements, the viewport automatically scrolls to the element currently in focus.
• Related Resources for Success Criterion 1.8.2:
  • 1.8.7 Maintain point of regard

1.8.3 Resize Viewport:

The user can resize graphical viewports within the limits of the display, overriding any values specified by the author. (Level A) ## DONE 26 April

• Intent of Success Criterion 1.8.3:
  If a graphical 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 full image to be displayed without scrolling. This benefits keyboard users who may find it difficult to scroll content, and users with cognitive or learning disabilities whose understanding of the content is aided by viewing the complete image.
• Examples of Success Criterion 1.8.3:
  • 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.
• Related Resources for Success Criterion 1.8.3:
  • W3C: Fullscreen (not complete at this writing)

1.8.4 Viewport Scrollbars:

When the rendered content extends beyond the viewport dimensions, users can have graphical viewports include scrollbars, overriding any values specified by the author. (Level A) ## DONE 26 April

• Intent of Success Criterion 1.8.4:
  When rendered content exceeds the bounds of a graphical viewport, horizonal 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 of Success Criterion 1.8.4:
  • Tanya has low vision. She is reading a receipe 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.4:
  • None

1.8.5 Indicate Viewport Position [was 1.8.5]:

The user can determine the viewport's position relative to the full extent of the rendered content. (Level A)## DONE TPAC

• Intent of Success Criterion 1.8.5:
  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 of Success Criterion 1.8.5:
  • 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.5:
  • None

1.8.6: Zoom [was 1.8.X]:

The user can rescale content within graphical viewports as follows: (Level A)## DONE 26 April

1. Zoom in: to at least 500% of the default size; and
2. Zoom out: to at least 10% of the default size, so the content fits within the height or width of the viewport.

• Intent of Success Criterion 1.8.6:
  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.
• Examples of Success Criterion 1.8.6:
  • Tanya has low vision. She opens a web application that uses small text fonts, mixed with graphical elements. She tries increasing the text size alone, but the graphical elements remain at their original sizes. She can't interpret the small graphical elements and the text flows improperly. However, when Tanya uses the zoom feature, the graphical elements are legible, and the page flows correctly.
  • $$ When Tanya views a web site 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.
  • $$ 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 larger map.
• Related Resources for Success Criterion 1.8.6:
  • 1.8.3 Resize Viewport
  • 1.8.7 Maintain point of regard
  • 1.8.12: Reflowing Zoom

1.8.7 Maintain point of regard [was 1.8.Z]

: To the extent possible, the point of regard remains visible and at the same location within the viewport when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed. (Level A) ## DONE 31 May 2012

• Intent of Success Criterion 1.8.7:
  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 of Success Criterion 1.8.7:
  • Jorge has low vision. While viewing a webpage 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 bowser content area. Jorge uses the zoom feature to make the content smaller. The text is reduced to a confortable 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.7:
  • 1.8.2 Move Viewport to Selection and Focus

1.8.8 Viewport History [was 1.8.5]:

For user agents that implement a viewport history mechanism (e.g. "back" button), the user can return to any state in the viewport history that is allowed by the content, including a restored point of regard, input focus and selection. (Level AA) ## DONE 5 April 2012

1.8.9 Open on Request [was 1.8.6]:

The user can specify whether author content can open new top-level viewports (e.g. windows or tabs). (Level AA) ## DONE TPAC

1.8.10 Do Not Take Focus:

If new top-level viewports (e.g. windows or tabs) are configured to open without explicit user request, the user can specify whether or not top-level viewports take the active keyboard focus when they open. (Level AA) ## DONE TPAC

• Intent of Success Criteria 1.8.8, 1.8.9 & 1.8.10:
  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 of Success Criteria 1.8.8, 1.8.9 & 1.8.10:
  • Justin has an attention deficit disorder. He is studying an online college course and finds a word that he 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 remains the same 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 popups 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.8, 1.8.9 & 1.8.10:
  • 3.4.1 Avoid unpredictable focus
  • 3.2.2 Back button

1.8.11 Same UI:

The user can specify that all top-level viewports (e.g. windows or tabs) follow the defined user interface configuration. (Level AA) ## DONE TPAC

• Intent of Success Criterion 1.8.11:
  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 of Success Criterion 1.8.11:
  • Robert 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.11:
  • 2.7.3 Multiple Sets of Preference Settings

1.8.12: Reflowing Zoom:

The user can request that when reflowable content in a graphical viewport is rescaled, it is reflowed so that one dimension of the content fits within the height or width of the viewport. (Level AA) ## DONE 26 April 2012 ## IER DONE 4 June 2012

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

• Intent of Success Criterion 1.8.12:
  It's important that reflowed content remains easily usable. Content is not easily usable if the user has to scroll back and forth to see a single line of text. 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.
• Examples of Success Criterion 1.8.12:
  • Frank has repetitive strain injuries and uses speech input. As he's gotten older he sometimes needs to increase the font size to comfortably read text on his computer screen. If the text does not flow properly, he overuses his voice to carry out multiple speech commands, or uses the mouse, which exacerbates his injuries, or simply gives up.
  • $$ When Frank is using his mobile phone to read a web page, he will zoom in to read a article on a web site. He configures his mobile phone so that the text reflows to always display zoomed content to fit in one column.
  • Maggie has cognitive issues that make it difficult for her to reorient when the computer screen changes. She occasionally zooms in to read small text. She finds it easier to reorient after zooming when at least one dimension of the content fits within the height or width of the viewport.
• Related Resources for Success Criterion 1.8.12:
  • 1.8.6 Zoom

1.8.13 Webpage Bookmarks [was 1.8.m, 1.8.13]:

The user can mark items in a webpage, then use shortcuts to navigate back to marked items. The user can specify whether a navigation mark disappears after a session, or is persistent across sessions. (Level AAA) ## DONE 31 May 2012

• Intent of Success Criterion 1.8.13:
  This success criterion is crucial for users who have trouble navigating a webpage. People who use speech input, have memory problems, or use small screens may be able to go from one area of a webpage 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 of Success Criterion 1.8.13:
  • 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 iPhone 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 professer 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.13:
  • None

1.9.1 Outline View:

Users can view a navigable outline of rendered content composed of labels for important elements, and can move focus efficiently to these elements in the main viewport. (Level AA) ## DONE 26 April

Note: The important structural elements depend on the web content technology, but may include headings, table captions, and content sections.

• Intent of Success Criterion 1.9.1:
  Outline views allow users 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 of 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
  • 2.3.1 Direct Navigation to Important Elements
  • 2.5.3 Configure Elements for Structural Navigation

1.9.2 Source View:

The user can view all source text that is available to the user agent. (Level AAA) ## DONE TPAC

• 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 of Success Criterion 1.9.2:
  • George 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 will also use 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

1.10.1 Access Relationships:

The user can access explicitly-defined relationships based on the user's position in content (e.g. show the label of a form control, show the headers of a table cell). (Level AA)## DONE 31 May 2012

• 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 a recognizable manner, such as relationships with 'id' attributes and child elements (e.g. Ajax widgets and with form elements). This allows users to better understand these relationships even if the elements are not adjacent on the screen or the DOM.
• Examples of Success Criterion 1.10.1:
  • John has low vision and uses a screen magnifier to access his browser. 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. She mouses over a 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:
  • WAI-ARIA: 6.5.4 Relationship Attributes
  • WAI-ARIA Authoring Practices: 4. Relationships
  • 2.5.1 Location in Hierarchy

1.10.2 Access to Element Hierarchy:

The user can determine the path of element nodes going from the root element of the element hierarchy to the currently focused or selected element. (Level AAA)
## DONE 5 June 2012

• Intent of Success Criterion 1.10.2:
  Users who have difficulty working with a web page or document can use user style sheets 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 of Success Criterion 1.10.2:
  • Jack has low vision. 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

2.1.1 Keyboard Operation:

All functionality can be operated via the keyboard using sequential or direct keyboard commands that do not require specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (e.g. free hand drawing). This does not forbid and should not discourage providing other input methods in addition to keyboard operation including mouse, touch, gesture and speech. (Level A) ## DONE 9 April 2012

• 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 ndash; 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 functionalities. 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 of 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.
    • Amal, Jeremy and Jamie use the graphical user interface menus even though they cannot use the mouse.
    • Fill out forms.
    • Access documentation.
  • Amal 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 container. 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 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 visble focus indicator.
• Related Resources for Success Criterion 2.1.1:
  • Microsoft Keyboard accessibility document [@@ find the link to these documents @@]
  • Apple keyboard
  • Unix
  • Modality Independence Principle
  • 2.1.3 No Keyboard Trap

2.1.2 Keyboard Focus (former 1.9.2):

Every viewport has an active or inactive keyboard focus at all times. (Level A) ## DONE 9 April 2012

• 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.6.
• Examples of Success Criterion 2.1.2:
  • Amal has a medical condition which 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 Alan 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 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 webpage using a speech command. The webpage 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 fieldbefore 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 visble 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.6 Expose Accessible Properties ensures that the focus location is available to assistive technology.

2.1.3 No Keyboard Trap (former 2.1.5):

If keyboard focus can be moved to a component using a keyboard interface (including nested user agents), then focus can be moved away from that component using only a keyboard interface. If this requires more than unmodified arrow or tab keys (or other standard exit methods), users are advised of the method for moving focus away. (Level A)## DONE TPAC

• 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 of 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 moves the focus to a toolbar extension 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:
  • Compound documents [@@ which W3C document does this refer to? There are many@@]

2.1.4 Separate Selection from Activation (former 2.1.4):

The user can specify that focus and selection can be moved without causing further changes in focus, selection, or the state of controls, by either the user agent or author content. (Level A) ## DONE 8 March 2012

• 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 of Success Criterion 2.1.4:
  • Murray 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.
  • $$ Ari uses Voiceover on his iPhone to navigate a webpage. 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.10 Do Not Take Focus

2.1.5 Follow Text Keyboard Conventions (former 2.1.7):

The user agent follows keyboard conventions for the operating environment. (Level A) ## DONE TPAC ## DONE 4 June 2012

• 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 of 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).
  • Jack's user agent uses a custom tree control showing a hierarchal outline view of the document headings. He 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 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

2.1.6 Efficient Keyboard Access:

The user agent user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access. (Level A)## DONE 9 April 2012

• 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 diffcult 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: A embedded media player provides shortcut keys for commonly used functions (e.g. pause and play).
• Examples of 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

2.1.9 [deleted] Allow Override of User Interface Keyboard Commands:

## DONE TPAC ## Merged with 2.3.5 on 2 August 2012

2.4.1 Text Search:

The user can perform a search within rendered content (e.g. not hidden with a style), including rendered text alternatives and rendered generated content, for any sequence of printing characters from the document character set. (Level A)

• 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 of 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, who has low vision, is attempting to create a user stylesheet for a site. She need 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, a user with a distraction disorder, 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 has images off and the alternative content for images  is revealed. He wants to send the flow chart image on the page to a collegue. 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 a colleague.
  • Agnes is deaf. She is watching a video with captions turned on. Agnes uses the search function to seach 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

2.4.2 Find Direction:

The user can search forward or backward in rendered content. (Level A)## DONE 23 March 2012

• 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 of Success Criterion 2.4.2:
  • A user has been reading through a web page and wants to quickly locate a phrase previously read. When opening the browser's page search feature, the user has options to search forward and backward from the current location. If the search reaches an endpoint in the document, the user is notified that the search has wrapped around, such as with an alert box or other indication.
• Related Resources for Success Criterion 2.4.2:
  • None

2.4.3 Match Found:

When a search operation produces a match, the matched content is highlighted, the viewport is scrolled if necessary so that the matched content is within its visible area, and the user can search from the location of the match. (Level A) ## DONE 23 March 2012 ## DONE 5 June 2012

• 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 of Success Criterion 2.4.3:
  • Jules is 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

2.4.4 Alert on Wrap or No Match:

The user can be notified when there is no match to a search operation. The user can be notified when the search continues from the beginning or end of content. (Level A) ## DONE 23 March 2012

• 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 of Success Criterion 2.4.4:
  • Dennis uses a screen reader. As soon as he gets a message that there is no match he goes on to search for something else. If he does not get a message he wastes time retrying the search to make sure the entire document has been searched.
• Related Resources for Success Criterion 2.4.4:
  • None

2.4.5 Search alternative content:

The user can perform text searches within textual alternative content (e.g. text alternatives for non-text content, captions) even when the textual alternative content is not rendered onscreen. (Level AA) ## DONE 23 March 2012

• Intent of Success Criterion 2.4.5: Authors frequently provide alternative content to meet web content accessibility guidelines, which users with disabilities will experience 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 may not be visibly rendered.
• Examples of Success Criterion 2.4.5:
  • Ronda typically browses the web with images turned off so she sees the alternative text for images rendered in place of images. She visits a favorite website on a friend's computer and knows she wants to find a link to her favorite artist's photo gallery. On her computer this is the artist's name so she searches for that word on her friend's computer. The alt text is not displayed in this case but the artist's image is highlighted because her 'text search' command has associated the alt text with the image.
  • Dennis 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

2.6.1 Access to input methods:

The user can discover recognized input methods explicitly associated with an element, and activate those methods in a modality independent manner. (Level AA) ## DONE 23 March 2012

• Intent of Success Criterion 2.6.1 :
  Users interacting with a web browser may be doing so by using one or more input technologies including keyboard, mouse, speech, touch, and gesture. Sometimes a web page is scripted so that it assumes and requires an input method that is not available to the user, such as handling drag events for a user relying solely on the keyboard. In those cases, the user needs to determine what methods are available and activate that element with a modality independent method.
  
  In addition, any one input method should not hold back another. For instance, people who don't use a mouse shouldn't have to map their input methods to the same steps a mouse user would take. The user agent can constrain steps such as not allowing a mouseup before a mousedown.
• Examples of Success Criterion 2.6.1 :
  • Jeremy cannot use a mouse. He needs to activate a flyout menu that appears when one hovers the mouse over a button. He navigates to the button and pulls up its context menu, which includes an "Inputs" submenu that lists the available input methods (e.g. events that were registered for this element: click, double-click, swipe left, and hover) and from that he chooses the "Hover" command. .
  • Ken is a speech input user. In order to get his work done in a reasonable amount of time and without overtaxing his voice he uses a single speech command phrase to move the mouse up, left and click.
  • Karen cannot use a mouse. She clicks a single key to activate both events for link that has an onmousedown and an onmouseup event link.
  • $$ Ingrid has low vision. When navigating a page with a smartphone, she can use both keyboard and gestures to operate all of the controls within the page.
• Related Resources for Success Criterion 2.6.1:
  • The Modality Independence Principle
  • 1.3.1 Highlighted Items

2.7.1 Persistent Accessibility Settings [was 2.7.2]:

User agent accessibility preference settings persist between sessions. (Level A)## DONE TPAC

• Intent of Success Criterion 2.7.1 :
  When a user has customized settings within the user agent to maximize accessibility, this success criteria ensures that customization is saved between browsing sessions. The user can then have those settings automatically used in subsequent browsing sessions.
• Examples of Success Criterion 2.7.1 :
  • Lynn has moderately low vision, and 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 has to adjust some settings in his browser to make it fully compatible with his speech input system. It's difficult for him to get it set up, since he can't fully operate the browser until it's done, so once it's configured this way he relies on it staying in that configuration even if he upgrades the browser, restarts his system and so forth.
  • $$ Betty has low vision and customizes her mobile browser's color and font settings to make make text much easier to read. Her browser incorporates a cloud-based profile so that her settings are retained across browsing sessions, and also available on her desktop and tablet browsers.
• Related Resources for Success Criterion 2.7.1 :
  • None

2.7.2 Restore all to default [was 2.7.3]:

The user can restore all preference settings to default values. (Level A)## DONE TPAC

• Intent of Success Criterion 2.7.2 :
  For some users, it may be difficult to easily recall all modified settings while others may find it difficult to navigate to each modified setting, especially if a particular setting may have impacted 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 their default values. This success criteria provides a means for a user to easily restore all preference settings to their default values using a single function or action.
• Examples of Success Criterion 2.7.2 :
  • Ron accidentally changes a browser setting that makes his browser incompatible with his screen reader, preventing him from changing it back. He instead restarts his browser using a command line option that starts it in the default configuration, which he's able to use, and from there he can change the setting that caused him problems.
  • Kathy 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.7.2 :
  • 3.2.5 Settings Change Confirmation

2.7.3 Multiple Sets of Preference Settings [was 2.7.4]:

The user can save and retrieve multiple sets of user agent preference settings. (Level AA)## DONE TPAC

• Intent of Success Criterion 2.7.3 :
  Some users may need to change their setting preferences under different circumstances such as varying levels of user fatigue or changes in environmental noise or lighting conditions. Providing an easy method for saving and switching between a set of preferences helps the user complete intended tasks in different situations.
• Examples of Success Criterion 2.7.3 :
  • When Hiroki is carrying his tablet computer he operates it with the built-in touchscreen, but when at his desk he links it to a Bluetooth keyboard and mouse, and redirects the display to a full-size computer monitor. The browser allows him to quickly switch between two completely different configurations for these different environments.
  • Davy has moderately low vision and prefers to adjust the contrast of media differently during the day than at night. Because this requires a number of different steps, for different types of media and aspects of the browser's display, he has two user profiles, one for each environment.
  • Aaron usually uses a keyboard and mouse, but when his repetitive strain injury is bothering him he prefers to use the mouse and avoid using the keyboard as much as possible. At those times he users his browser's user preference profiles to load a different configuration that’s optimized for the mouse, including custom toolbars that make most of the commands he uses available as toolbar buttons.
• Related Resources for Success Criterion 2.7.3 :
  • None

2.7.4 Change preference settings outside the user interface [was 2.7.6]:

The user can adjust any preference settings required to meet the User Agent Accessibility Guidelines (UAAG) 2.0 from outside the user agent user interface. (Level AA)## DONE TPAC## DONE 5 June 2012

• Intent of Success Criterion 2.7.4 :
  Users with a disability may find that they cannot use a user agent with its current preference settings. This can occur when they are initially setting up the product and its default settings don't meet their needs, or after they, or another product or user, change an option from the setting they need. In these cases they may not be able to user the user agent's own user interface to adjust the settings, and so need a way to adjust or reset those options from outside the user agent. There are multiple ways this can be accomplished 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 of Success Criterion 2.7.4 :
  • Aosa is blind, and 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 mobile phone to use the high contrast mode. When she launches her mobile 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, then finds he accidentally sets his background and font color to white on white. He cannot 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 then 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. But, 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.7.4 :
  • None

2.7.5 Portable Preference Settings [was 2.7.7]:

The user can transfer all compatible user agent preference settings between computers. (Level AAA) ## DONE 4 June 2012

• Intent of Success Criterion 2.7.5 :
  Configuring a user agent may 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 easily migrate preference setting to another compatible device. Schools and universities also need to maintain accessibility settings across multiple machines.
• Examples of Success Criterion 2.7.5 :
  • Lori is a rehabilitation specialist who works with clients to customize their 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 backup 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 the voice application on his phone. He sets up the web-based email application accessibility preferences on a mobile device. These preferences are automatically reflected in the desktop version of that web-based email application.
  • Trisha is a 4th grader with low vision. When she goes to different classrooms in her school, she carries a USB stick with her accessibility settings so she and her teachers do not have to use class-time customizing her computer.
  • $$ Betty is a low vision user and has a highly customized color palette defined in her browser. By saving her customizations to a cloud-based storage service, her preferences can easily be transferred to other desktop and mobile browsers that she uses.
• Related Resources for Success Criterion 2.7.5 :
  • None

2.8.1 Configure Toolbars:

The user can add, remove, reorder, show, and hide any toolbars and similar containers, and the items within them. (Level AA)

• Intent of Success Criterion 2.8.1:
  This success criterion is about giving the user control over which user interface elements are visible and usable, where they are visually located on the screen, and where they fall in the navigation order. In some cases adjusting whether an element is visible and usable may involve installing/uninstalling a component, or merely showing/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 may have problems making the large movements required to select between non-adjacent controls which they need to use frequently. Similarly users with low vision may have to excessively move their magnified view-port to see frequently used controls. Enabling these controls to be situated together removes much of the strain faced by these users, and increases productivity as task completion times are decreased.
• Examples of Success Criterion 2.8.1:
  • Martin accesses the computer by pressing keys with a stick held in his mouth known as a mouthstick and gets around the user agent with taps on the tab and arrow keys. The designers of a user agent have decided to place a button for printing a web page as the last button on a toolbar. This button requires six presses of a right arrow key to reach for Carl and is the only button he 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 presses he must issue with his mouthstick to one.
  • Laura has one hand, the left. When she holds her mobile phone, 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 with her thumb.
• Related Resources for Success Criterion 2.8.1:
  • WAI-ARIA

2.8.2 Reset Toolbar Configuration:

The user can restore all toolbars and similar containers to their default configuration. (Level AAA)

• Intent of Success Criterion 2.8.2:
  Mistakes happen. If a user has modified the toolbar incorrectly it can often be difficult to return to a stable state so that these errors can be corrected. There are additional pressures in this regard for people with learning difficulties who make more use of toolbars than they do of textual menus. Building an easily selectable mechanism to restore these defaults saves user time and reduces stress.
• Examples of Success Criterion 2.8.2:
  • Jack is an 80 year old web surfer who is intellectually very sharp but experiences tremors in his hands when required to make fine movements with the mouse. To help himself he is setting up the toolbar so that 'spacers' are placed between each component to prevent accidental selection of adjacent buttons. Today his tremors are particularly bad and Jack makes a number of mistakes becoming increasingly frustrated that while trying to correct these errors he begins to make many more. Jack just wants to start over. Luckily the browser manufacturer has included an easy mechanism to restore the default toolbar configuration. Jack chooses this option and successfully starts over the next day.
• Related Resources for Success Criterion 2.8.2:
  • WAI-ARIA

2.9.1 Adjustable Timing:

Where time limits for user input are recognized and controllable by the user agent, the user can extend the time limits. (Level A)## DONE 26 March 2012

• Intent of Success Criterion 2.9.1 :
  Users of assistive technology, such as screen readers, and those who may require more time to read or understand and 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/author imposed presentation / interaction time limits.
• Examples of Success Criterion 2.9.1 :
  • News Alerts: A news organizations website has a region of the home page which presents featured stories, cycled every 3 seconds. A user with low vision, using a screen magnifier, requires more than three seconds to read the news item and select it. The user agent provides the user with a global option to freeze all timed events using a keyboard command. Another keyboard command resumes the timed presentation.
  • Session Inactivity Timeouts: A screen reader user is logged into a financial services website and is reading the site's detailed privacy policy. Because of security policy, the site will terminate the session of any user who has been inactive for 5 minutes. A prompt will appear warning of the impending log off without further action. This user is able to select an option in her non-visual user agent that automatically responds to those prompts if the user agent is currently reading the content.
• Related Resources for Success Criterion 2.9.1 :
  • None

2.10.1 Three Flashes or Below Threshold:

In its default configuration, the user agent does not display any user interface components or recognized content that flashes more than three times in any one-second period, unless the flash is below the general flash and red flash thresholds. (Level A)## DONE 9 April 2012

• Intent of Success Criterion 2.10.1 :
  The intent of this Success Criterion is to guard against inducing seizures due to photosensitivity, which can occur when there is a rapid series of general flashing, or red flash. A potentially harmful flash occurs when there is a pair of significantly opposing changes in luminance, or irrespective of luminance, a transition to or from a saturated red occurs.
• Examples of Success Criterion 2.10.1 :
  • A single, double, or triple flash -- as long as it does not include changes to or from a saturated red -- may be used to attract a user's attention, or as part of an interface animation.
  • An error condition is indicated by flashing that continues until acknowledged by the user. 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.10.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

2.10.2 Three Flashes:

In its default configuration, the user agent does not display any user interface components or recognized content that flashes more than three times in any one-second period (regardless of whether not the flash is below the general flash and red flash thresholds). (Level AAA) ## DONE 9 April 2012

• Intent of Success Criterion 2.10.2 :
• The intent of this Success Criterion is to guard against inducing seizures due to photosensitivity, which can occur when there is a rapid series of general flashing, or red flash. A potentially harmful flash occurs when there is a pair of significantly opposing changes in luminance, or irrespective of luminance, a transition to or from a saturated red occurs. 2.10.2 has the same effect as 2.10.1, only goes further to ensure that more sensitive users can traverse the Web without potentially harmful effects.
• Examples of Success Criterion 2.10.2 :
  • refer to 2.10.1
• Related Resources for Success Criterion 2.10.2 :
  • WCAG 2.0: 2.3.2 Three Flashes
  • 2.11.2 Time-Based Media Load-Only
  • 2.11.6 Stop/Pause/Resume Time-Based Media

3.1.2 Reduce Interruptions:

The user can avoid or defer recognized non-essential or low priority messages and updating/changing information in the user agent user interface and rendered content.(Level AA)## DONE 5 June 2012

• Intent of Success Criterion 3.1.2:
  It's important that users be able to avoid unnecessary messages. Messages designed to inform the user can be a burden to users for whom pressing keys is time-consuming, tiring, or painful. Similarly, users with some cognitive impairments find it difficult to deal with constant distractions caused by updating visual or audio information, and would prefer to hide unnecessary updates.
• Examples of Success Criterion 3.1.2:
  • The browser has an update ready. The user should have the option to be informed of an update or, instead, only get update information when the user actively requests it.
  • A web page has a stock market ticker that is marked as having a low priority level using the WAI-ARIA aria-live:polite value. Shirley has a cognitive disability and is distracted by the page flicker, so she changes the browser's preference setting to indicate that regions with low priority level should not be automatically updated.
• Related Resources for Success Criterion 3.1.2:
  • WAI-ARIA

3.2.1 Form Submission:

The user can specify whether or not recognized form submissions must be confirmed. (Level AA)## DONE 15 March 2012

• Intent of Success Criterion 3.2.1:
  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 the form. Those users need to be able to disable the ability to submit on Enter.
• Examples of Success Criterion 3.2.1:
  • Upon installation of a web browser, a screenreader user selects an option to disable form submission on Enter. This is a preference option that can be easily discovered and changed by the user in the future. This allows the user to complete forms from the banking website knowing that the submit button must be selected in order to submit the form.
  • 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.2.1:
  • 2.1.1 Keyboard Operation
  • 3.2.4 Text Entry Undo

3.2.2 Back Button

: The user can reverse recognized navigation between web addresses (e.g. standard "back button" functionality). (Level AA) ## DONE 15 March 2012 & 19 July 2012

• Intent of Success Criterion 3.2.2:
  Being able to retrace a navigation step is important for users with cognitive issues that involve memory and attention. It's also important for users whose means of input is not 100% accurate, such as speech input users or users with fine motor challenges. and it's 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.
• Examples of Success Criterion 3.2.2:
  • Joe 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 says "Go Back" 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.
  • Etta has low vision and frequently clicks on the wrong link, and when she does so, she simply clicks the Back button in order to get back to where she had been.
  • Bessie enters text with difficulty, so when she wants to navigate to a page she's already been to, it's much easier for her to click on its title in her History menu than it would be to enter its URL or navigate through it through a long series of links.
• Related Resources for Success Criterion 3.2.2:
  • 1.8.8 Viewport History

3.2.3 Provide spell checking functionality:

User agents provide spell checking functionality for text created inside the user agent. (Level AA)## DONE 5 June 2012

• Intent of Success Criterion 3.2.3:
  Users with various disabilities benefit from the features found in spell checkers when composing text. It is commonplace to create enter significant amounts of content inside a user agent for tasks such as email, social networking and web-based productivity applications such as word processors. The intent of this success criteria is to ensure that users with disabilities can easily correct spelling errors when composing text. This particularly important for users with dyslexia and other disabilities that significantly increase their chance of misspelling words.
• Examples of Success Criterion 3.2.3:
  • 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.2.3:
  • None

3.2.4 Text Entry Undo:

The user can reverse recognized text entry actions prior to submission. (Level A)

Note: Submission can be triggered in many different ways, such as clicking a submit button, typing a key in a control with an onkeypress event, or by a script responding to a timer.

## DONE 19 July 2012 (was 3.2.X)

• Intent of Success Criterion 3.2.4:
  Users who are blind or have some visual impairments or cognitive disabilities have difficulty determining the location of the keyboard focus, and therefore are at risk of entering text in an undesired window or location. Users with mobility problems may have difficulty selecting the correct form field and may not realize it until they have entered text information.  These users need to be able to reverse a text entry ("Undo") prior to submission.
  
• Examples of Success Criterion 3.2.4:
  • Billie is a paraplegic who uses speech input. When she is working from the main office, she is in a noisy location which can interfere with her speech input.   She is writing a blog entry and is almost finishes when her speech input software incorrectly interprets some background noise as a "select all" command causing her to overwrite her entire blog entry with a small phrase.  She 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.2.4:
  • None

3.2.5 Settings Change Confirmation:

If the user agent provides mechanisms for changing its user interface settings, it either allows the user to reverse the setting changes, or the user can require user confirmation to proceed. (Level A)
## DONE 19 July 2012 (was 3.2.Y)

• Intent of Success Criterion 3.2.5:
  The description of some user interface settings can be confusing to less-technical users; settings changes can have unintended consequences; or 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 of Success Criterion 3.2.5:
  • 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, so all the labels of the icons 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 carefully changes the background to a color with sufficient contrast for comfortable reading.
• Related Resources for Success Criterion 3.2.5:
  • Guideline 2.7 Preference settings

3.3.1 Accessible documentation:

The product documentation is available in a format that meets success criteria of WCAG 2.0 Level "A" or greater. (Level A)## DONE TPAC

• Intent of Success Criterion 3.3.1:
  User agents will provide documentation in a format that is accessible. If provided as Web content, it must conform to WCAG 2.0 Level "A" and if not provided as Web content, it must be in conformance to a published accessibility benchmark and identified in any conformance claim for the user agent. This benefits all users who utilize assistive technology or accessible formats.
• Examples of Success Criterion 3.3.1:
  • A user agent installs user documentation in HTML format conforming to WCAG 2.0 Level "A". This documentation is viewed within the user agent and is accessible in accordance with the conformance of the user agent to UAAG 2.0.
  • A user agent provides documentation in HTML format conforming to WCAG 2.0 Level "AA" and is available online. In addition, the user agent provides user documentation in a locally installed digital talking book content format in conformance with a recognized, published format.
• Related Resources for Success Criterion 3.3.1:
  • None

3.3.2 Document Accessibility Features:

All features of the user agent that meet User Agent Accessibility Guidelines 2.0 success criteria are documented. (Level A)## DONE TPAC

• Intent of Success Criterion 3.3.2:
  Users with disabilities that need to use the accessibility features of the user agent user interface can easily find descriptions of how to use and configure the features, including assistive technology. These descriptions can be provided in the documentation or user interface of the user agent or by the underlying platform, if the feature is in fact a service of that platform. It is strongly recommended that the documentation be easily available to end users, and without charge.
  
• Examples of Success Criterion 3.3.2:
  • In a section entitled "Browser Features Supporting Accessibility", a vendor provides a detailed description of user agent features which provide accessibility, describing how they function, and listing any supported third party assistive technologies that may be supported or required.
  • A user is exploring the menus of a user agent and finds a feature named Use My Style Sheet. Activating help the user quickly learns 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 specialize command, she can pull up a list of all the gestures commands available with descriptions on how they function.
• Related Resources for Success Criterion 3.3.2:
  • 3.3.4 Centralized View

3.3.3 Changes Between Versions:

Changes to features that meet UAAG 2.0 success criteria since the previous user agent release are documented. (Level AA)## DONE TPAC

• Intent of Success Criterion 3.3.3:
  As accessibility features are implemented in new versions it is important for users to be able to be informed about these new features and how to operate them. The user should not have to discover which new features were implemented in the new version.
• Examples of Success Criterion 3.3.3:
  • Martha goes to an app store on her computer and notices that an update for the web browser she uses is available. When she installs it she finds a welcome page talking about the new features in this release, and one of the links on that page says "What's New For Accessibility". Following this link Martha reads about the accessibility improvements added and discovers this update had added a feature allowing 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.3.3:
  • None

3.3.4 Centralized View:

There is a dedicated section of the documentation that presents a view of all features of the user agent necessary to meet the requirements of User Agent Accessibility Guidelines 2.0. (Level AAA)## DONE TPAC

• Intent of Success Criterion 3.3.4:
  Specific accessibility features are important for users to know about and how to operate. The user should not have to discover where the accessibility features are documented in context (although that too is very useful). A specific section devoted to only accessibility features (e.g. keyboard shortcuts, how to zoom the viewport, where to find accessibility configuration settings), would make it easier for user to become more functional more quickly with the user agent. This is on a per-product basis. Nested user agents or addons may provide separate centralized documentation.
• Examples of Success Criterion 3.3.4:
  • Bob downloads a new web browser on his mobile phone. He's never used this software before and also uses a screen reader that is part of his phone's operating system. The browser's online help includes a section on accessiblity that point him to pages discussing non-visual access, such as interaction with screen readers, as well as helpful hints such as an explanation of the screen layout and a list of supported touch gestures.
  • A specific section in the documentation (local or online) detailing accessibility features of the user agent.
• Related Resources for Success Criterion 3.3.4:
  • None

Implementing Guideline 3.4 - The user agent must behave in a predictable fashion. [Return to Guideline]

Summary: Users can prevent non-requested focus changes (3.4.1).

3.4.1 Avoid unpredictable focus [formerly 3.4.2, before that 5.4.2, and 1.9.20, broadened]:

The user can prevent focus changes that are not a result of explicit user request. (Level A) ## DONE TPAC

• Intent of Success Criterion 3.4.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 may not realize they have skipped over some content, especially if they can only see a small portion of the page at a time. Similar problems may occur if the content or user agent automatically moves the focus while the user is reading or entering data on a page. If the focus moves without the user recognizing it, they can easily end up entering data in an incorrect field or taking other unintentional actions. Users can also become confused or disoriented when a window scrolls when they haven't requested it. This is particularly problematic for users who can only see a small portion of the document, and thus have to use more effort to determine their new context. Such users also are more likely to continue typing, not immediately realizing that the context has changed. Users for whom navigation is time consuming, tiring, or painful (including those using screen readers or with impaired dexterity) may also need more steps to return to the area where they want to work. While we recognize it may improve accessibility for some users on some pages to have the page to set focus to specific link or field when the page loads, it can also be detrimental for some users, and therefore users needs to be in control of this behavior.
• Examples of Success Criterion 3.4.1:
  • Jerome has loaded a page that sets its default focus to a search box. Because he wants to read the content of the page, rather than starting by entering data, it takes him additional scrolling to get to the content that was not in the search box. To prevent this, he adjusts his browser's settings to disable the automatic focus change on this page.
  • Jessica uses a screen enlarger, and 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 uses speech recognition. He speaks his credit card number by saying several digits and, if needed, Tab keys, in a single phrase. He needs to know ahead of time whether it is necessary to include the Tab command in the phrase.
  • Joey is filling in a Web form that asks for his 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. This can be a problem for two reasons, first because if Joey is not looking at the screen she does not realize that the focus has moved for her, and so 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. It can also pose a problem if Joey realizes that she typed one digit incorrectly in the area code field, because when she presses Shift+Tab to return and edit that field, the browser or content script checks the number of digits that have been entered, and seeing that it is three, automatically moves the focus once again, preventing her from editing the number. To avoid these problems, Joey goes to her browser's Preferences dialog box and checks the option that prevents focus changes that she has not explicitly requested.
  • Justine uses a keyboard macro to execute a multistep command at a specific location. The focus changes without her control, so the command fails or executes with unpredictable results.
• Related Resources for Success Criterion 3.4.1:
  • 1.3.1 Highlighted Items
  • 1.8.9 Open on request
  • 1.8.10 Do not take focus

5.1.1 WCAG Compliant [was 5.2.1]:

Web-based authoring tool user interfaces meet the WCAG 2.0 success criteria: Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria. (Level AAA)

Note: This success criterion does not apply to non-Web-based user agent user interfaces, but does include any parts of non-Web-based user agents that are Web-based (e.g. help systems).

• Intent of Guideline 5.2:
  Web-based applications which are intended to replace or enhance a desktop user agent or its functionality, but are in-fact built and rendered using standard Web technologies, are becoming increasingly common. These Web applications, windowless browsers, rich internet applications, HTML5 canvas, etc., perform similar functions to their desktop cousins and so must also conform to the accessibility requirements placed on a desktop user agent.
• Examples of Guideline 5.2:
  • Success criteria 2.7.1 requires that a user agent enable a user to change settings that impact accessibility. In this case we would expect that a Web-Based user agent should also enable a user to change accessibility settings specific to its functionality, which may in some cases enhance or override that of the platform on which it is executing: window-less browser, native operating system, etc.
• Related Resources for Guideline 5.2:
  • WAI-ARIA 1.0 User Agent Implementation Guide
  • W3C Web Design and Applications Activity

5.1.2 Implement accessibility features of content specs [was 5.3.1]:

Implement and cite in the conformance claim the accessibility features of content specifications. Accessibility features are those that are either (Level A):

1. identified as such in the specification or
2. allow authors to satisfy a requirement of WCAG.

• Intent of Success Criterion 5.1.2:
  
• Most content specifications include features important to users with disabilities, and users may find it difficult or impossible to use a product that fails to support those features. Users should be able to easily discover detailed information about the user agent's adherence to accessibility standards, including those related to content such as HTML and WAI-ARIA, and should be able to do so without installing and testing the accessibility features. This will allow them to make informed decisions about whether or not to they will be able to use, and therefore should install, a new product or version of that product.
  
  
• Examples of Success Criterion 5.1.2:
  • Jordy uses a website which uses WAI-ARIA to identify the functions of custom controls. If he used a web browser that didn't support this aspect of WAI-ARIA and expose that information to assistive technology, the website would be unusable with his web browser. Therefore Jordy needs to choose a web browser that he knows fully supports WAI-ARIA, and he determines this by reading product documentation and UAAG conformance claims posted on the Web
• Related Resources for Success Criterion 5.1.2:

  WCAG

  HTML

  CSS

  WAI-ARIA

5.1.3 Implement Accessibility Features of platform:

If the user agent contains non-web-based user interfaces, then those user interfaces follow user interface accessibility guidelines for the platform. (Level A)

• Intent of Success Criterion 5.1.3:
  
• The intent of this success criterion is to ensure that user agent user interfaces that are not web applications are more accessible to authors with disabilities. Existing platform accessibility guidelines are referenced because accessibility guidelines already exist for many platforms and this wording allows developers the flexibility to conform with accessibility legislation in their markets.
• Most operating systems have conventions and expectations that aid accessibility, such as keyboard behavior, support of an accessibility API, user interface design, and other standards related to accessibility. The intent of this success criteria is to ensure that user agents comply with the basic accessibility requirements of the platform in use.
  
  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: Developers should see the documents listed in the "Related Resources for Success Criterion A.1.2.1" section. Unless special circumstances exist (e.g., a document has been superseded, the platform has undergone major architectural changes), the listed resources should be assumed to be relevant to the platforms listed.
  
  
• Examples of Success Criterion 5.1.3:
  • If you are developing for the Gnome platform, consult 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. " If your program controls focus, make sure you conform to this accessibility guideline for focus.
  • Mobile browser: The developer of a browser app for the iPhone platform follows the guidance provided in the "Accessibility Programming Guide for iPhone OS".
    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, this explanations can be general and cover several sections at once.
• Related Resources for Success Criterion 5.1.3:

  [APPLE-ACCESS]

  "Introduction to Accessibility Overview," Apple Computer Inc.

  [CARBON-ACCESS]

  "Introduction to Accessibility Programming Guidelines for Carbon," Apple Corporation.

  [COCOA-ACCESS]

  "Introduction to Accessibility Programming Guidelines for Cocoa," Apple Corporation.

  [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.

  [SUN-DESIGN]

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

  [Editors' Note: Resource links from Jim - compare and expand]

  http://www.microsoft.com/windowsxp/using/accessibility/default.mspx

  http://www.apple.com/accessibility/

  http://www.linux.org/docs/ldp/howto/Accessibility-HOWTO/linuxos.html

  http://www.linuxfoundation.org/collaborate/workgroups/accessibility/iaccessible2

  http://developer.apple.com/ue/accessibility/

  http://msdn.microsoft.com/en-us/library/dd373592%28VS.85%29.aspx

  http://msdn.microsoft.com/en-us/windows/ee815673.aspx

5.1.4 Handle Unrendered Technologies:

If the user agent does not render a technology, the user can choose a way to handle content in that technology (e.g. by launching another application or by saving it to disk). (Level A)

• Intent of Success Criterion 5.1.4:
  Users who have disabilities may have fewer options in terms of how they access the information. Information is made available in a variety of ways on the Internet, and at times a specific format may be the only way in which information is available. If the user agent cannot render that format it should let the user access that content through alternate means, such as invoking a third-party renderer or saving the file to the user's hard drive.
• Examples of Success Criterion 5.1.4:
  • Tracy has low vision and finds it much more convenient to access her bank statement electronically than on paper, even though the electronic version is in a TIFF image, a format that her browser cannot render. In this case, the browser lets her save the image to her hard drive so she can open it in another program.
• Related Resources for Success Criterion 5.1.4
  • None

5.1.5 Alternative content handlers:

The user can select content elements and have them rendered in alternative viewers. (Level AA)## DONE TPAC## DONE 28 June

• Intent of Success Criterion 5.1.5:
  When accessing media or specialized content (e.g. MathML) on the Web, users with disabilities sometimes find they have a richer or more accessible experience using a third-party application, plug-in, or extension, than using the browser's built-in facilities. In these cases they want to be able to navigate to content in their browser and then enable or activate a browser plug-in or extension to interact with the content. Alternately, they may elect to save that content to their disk and launch it in a third- party application.In the case of streaming video that cannot be saved to disk, the browser launches the external viewer, passing it the URL to the online video.
• Examples of Success Criterion 5.1.5:
  • A 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 in the browser's cache folder. The browser saves the video to a temporary location on the user's disks (or uses one already in its cache folder), then launches the player to show that file.
  • Jukka is visually impaired and a scientist whose work involves mathematical models for speech recognition. Many of the journals he reads online are beginning to include 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 plugin via a context menu to make the MathML understandable to his screen reader.
    
• Related Resources for Success Criterion 5.1.5
  • None

5.1.6 Enable Reporting of User Agent Accessibility Faults:

The user agent provides a mechanism for users to report user agent accessibility issues.(Level AAA)
## DONE 12 July 2012

• Intent of Success Criterion 5.1.6:
  People who use assistive technologies such as screen readers may find that a technology isn't fully compatible with a Web browser, or that the browser doesn't accessibly render content authored in compliance with WCAG. This causes information loss and inconvenience. When this happens, users with disabilities will benefit from being able to easily file a report with the user agent vendor to report the incompatibility, similar the way users can file bug reports or provide feedback. A contact link on a website is not sufficient to satisfy this success criterion.
• Examples of Success Criterion 5.1.6:
  • Alice is a visually impaired college student who frequently uses a refreshable braille display with her Web browser. Occasionally she experiences difficulty with Web content containing elements such as drop-down list boxes or complex menus, where the text is only partially rendered on the braille display. Alice notices this incompatibility and navigates to the feedback section of her browser. After providing some basic information (such as AT software and computer hardware used), Alice is able to describe the problem she encountered and submit 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 selects to include the current URL 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 may contact him for further details or to provide a workaround.
• Related Resources for Success Criterion 5.1.6:
  • none