1.1.1 (former 3.1.2) Configurable Default Rendering: The user can specify which types of alternative content to render by default. (Level A)

• Intent of Success Criterion 1.1.2 (former 3.1.2):
  When the author provides alternative content, it is wasted if the user agent doesn't render it for users who need it. This is a global option because it would be an unreasonable burden for the user to have to change the rendering options every time they visit a new page.
• Examples of Success Criterion 1.1.2 (former 3.1.2):
  • In the browser's preferences dialog box, a user specifies that they want 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.
  • In the browser's preferences dialog box, a user chooses to always display the alternative ("fallback") content for embedded objects, such as videos.
  • The user 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 (former 3.1.2):
  • To be written

1.1.2 (former 3.1.3) Browse and Render: When a rendered element has alternative content, the user can render alternatives according to the following: (Level A)

• synchronized alternatives for time-based media (e.g., captions, audio descriptions, sign language) can be rendered at the same time as their associated audio tracks and visual tracks, and
• non-synchronized alternatives (e.g., short text alternatives, long descriptions) can be rendered as replacements for the original rendered content.

• Intent of Success Criterion 1.1.3 (former 3.1.3):
  a. There are times when a user cannot gain meaningful information from images, charts, graphs, etc. (non-time-based media element).The author may have provided synchronized alternatives for the media. The user should be able to easily discover the synchronized alternatives provided, and have them render synchronously with the default media.
  
  b. There are times when a user cannot gain meaningful information from a non-time-based media element (images, charts, graphs, etc.). The author may have provided alternatives for this. The user should be able to easily discover the alternatives provided, and have them render in place of the default media.
• Examples of Success Criterion 1.1.3 (former 3.1.3):
  1. Sam is deaf. He is watching a video on a web page. He cannot hear the audio. The author has provided captions for the video. The user agent detecting that captions exist, makes the caption button visible. The caption button toggles the captions on/off.
     Sue is blind. She is watching a video on a web page. She cannot see the action on the screen. The author has provided audio-descriptions for the video. The user agent detecting that audio-descriptions exist, makes the AD button visible. The button toggles the audio-descriptions on/off.
  2. Mary has a learning disability. She is reading a page with many images. The images are distracting. Mary is able to turn the images off, and reveal the alternative text (@alt) that the author provided. The alternative text is rendered in place of the images. Mary has the option of having the size of the image remain same or fit the size of the text.
     Some of the images are graphs. She cannot make sense of the graphs. The author has provided long descriptions for the graphs. Sue toggles the long-discription feature. The browser detects the presence of valid @long-descriptions and renders an actionable icon inline after an image. Mary can click on the icon, opening the long-description for that particular graph.
• Related Resources for Success Criterion 1.1.3 (former 3.1.3):
  • See Success Criterion 4.1.2 (former 2.1.2) : Name, Role, State, Value, Description

1.1.3 (former 3.1.1) Identify Presence of Alternative Content: The user can specify that alternative content indicators be rendered along with elements that have alternative content (e.g. an icon to indicate an image has a short text alternative). (Level A)

• Intent of Success Criterion 1.1.1 (former 3.1.1):
  When the author provides alternative content, it is wasted if the user cannot find it. Thus it becomes the responsibility of the user agent to make the presence of alternative content evident to the user. The user 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 (former 3.1.1):
  • Distinct visual icons are rendered in proximity of content which has short text alternatives, long descriptions, captions. If the icon forces the text to extend beyond a fixed size container the user agent handles this using its global preference settings to determine whether it expands the container, provides scroll bars, or truncates the content.
  • When rendering a Web page using synthesized speech, the browser generates an audible tone to signify the word being read is an acronym, and the user can press the * key to hear the expansion. When the phrase being read is the Alt text for an image, another tone indicates that the user can press + to hear the longdesc.
  • A button is displayed beneath the playing video to indicate that captions are available and to let the user toggle their display.
• Related Resources for Success Criterion 1.1.1 (former 3.1.1):
  • (Refer to the SC about handling layout/reflow options.)

1.1.4 (former 3.1.4) Rendering Alternative (Enhanced): The user can specify the fallback order in which to render alternative content. If the alternative content has a different height or width, the user agent will reflow the viewport.(Level AA)

• Intent of Success Criterion 1.1.4 (former 3.1.4):
  For a give piece of non-text content the author may have provide one or several 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, audio descriptions in different languages. There may be others. The user is able to choose which item(s) to render by default, and specify the order of the cascade of alternatives to be rendered if the author did not provide a type of alternative.
• Examples of Success Criterion 1.1.4 (former 3.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 have the long description rendered in place of the image. If the long description does not exit, she wants the ‘alt text’ to be rendered. If neither is available, Mary wants the file name rendered.
    
    Added functionality would allow Mary to right click (context menu) on an image to list and select the rendering of the available alternatives (thumbnail, original size, full screen, low resolution, high resolution, alt text, long description, file name)
  • @@ Editors' Note: where do we put the ability for the user to individually pick an image and have the image displayed. It should not have to be an all or nothing. @@
  • Juan is hard of hearing. He wants to always see video on the page. Also, Juan would like the Spanish language track used if available, along with 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 the the video and English audio.
    
    Added functionality would allow Juan to right click (context menu) on an video to list and select the rendering of the available alternatives (still image, caption languages, audio languages, audio-description languages)
• Related Resources for Success Criterion 1.1.4 (former 3.1.4):
  • To be written

1.2.1 (former 3.4.1) Repair Missing Alternatives: The user can specify whether or not the user agent should generate and render repair text (e.g. file name) when it recognizes that author has not provided alternative content. (Level A) The user can receive generated repair text when the user agent recognizes that the author has not provided alternative content required by the technology specification (e.g. short text alternative for an image). (Level A)

• Intent of Success Criterion 1.2.1 (former 3.4.1):
  When alternative content is missing, it is sometimes useful for the user agent to provide alternative information that is available, such as the filename. The user needs to be able to control the flow of this information, because it can be distracting and time-consuming. This is particularly important for users with some disabilities, who may not be able to use some forms of content (e.g. images) or may even need to avoid some forms of content (e.g. animations) and therefore choose to replace them with alternative content.
  
  The user needs to be able to control the flow of the content when this information is added, because in some cases cases truncating the content to fit its container will make the document unusable (e.g. if important information becomes hidden), while in other cases expanding the container will make the document unusable (e.g. when important cues no longer line up correctly).
• Examples of Success Criterion 1.2.1 (former 3.4.1):
  • 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.
  • A video does not have captions. The user selects a caption button, and the user 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 (former 3.4.1):
  • Evaluating Web Sites for Accessibility: Overview

1.2.2 (former 3.4.2) Repair Empty Alternatives: The user can specify whether or not the user agent should generate and render repair text (e.g. file name) when it recognizes that the author has provided empty alternative content. (Level AA) The user has the option of receiving generated repair text when the user agent recognizes that the author has provided empty alternative content. (Level AA)

• Intent of Success Criterion 1.2.2 (former 3.4.2):
  When an author has chosen to code web content for alternative text but not provide any text information (e.g. an empty alt) the user may still need to know any information available about that web content. Some authoring tools may insert empty alternative text by default, even though this is is contrary to accessibility guidelines, and this can prevent users from getting useful information about the element.
• Examples of Success Criterion 1.2.2 (former 3.4.2):
  • A user wanting additional information on an image can right click on an image to get a context menu, then choose properties to get available information about the image without have to find the image in the source code.
  • A photo-sharing web site automatically generates web content with text alternatives. When the photos are initially uploaded, or if the person posting the photos chooses not to caption a photo, an empty text alternative is automatically generated. A person with visual impairments uploads a batch of photos and needs to know which photo is which in order to provide the photo description. The user agent provides a menu option that displays all known information about that file including filename and selected camera info (date, time, size, type, etc.).
• Related Resources for Success Criterion 1.2.2 (former 3.4.2):
  • To be written

1.3.1 (former 3.5.1) Highlighted items: The user can specify that the following be highlighted so that each is uniquely distinguished The user has the option to highlight the following classes of information so that each is uniquely distinguished. (Level A):

• (a) selection,
• (b) content focus,
• (c) recognized enabled elements
• (d) presence of alternative content
• (e) recently visited links

• Intent of Success Criterion 1.3.1 (former 3.5.1):
  Users need to be able to easily discover what web content they can interact with. Users with low vision need to be able to highlight selection, content focus, enabled elements and links (including recently visited links) in order to successfully discover and interact with the web content.
• Examples of Success Criterion 1.3.1 (former 3.5.1):
  • A web site uses styles to override visited link color. A low vision user 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.
  • An author has created a web site with CSS styles that removes the content focus outline. The user agent provides a dialog box for setting overrides to authors CSS focus outline declaration.
• Related Resources for Success Criterion 1.3.1 (former 3.5.1):
  • UAAG 1.3.2 (former 3.5.2) Highlighting Options

1.3.2 (former 3.5.2) Highlighting options: The user can specify highlighting options that include at least: (Level A) The highlighting options (with the same configurable range as the operating environment's conventional selection utilities) include at least (Level A):

• (a) foreground colors,
• (b) background colors, and
• (c) border (configurable color, style, and thickness)

• Intent of Success Criterion 1.3.2 (former 3.5.2):
  A low vision user needs control over what visual properties work best for highlighting. 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 (former 3.5.2):
  • A low vision wants to know where the text boxes are on a web form. The user wants to set a thick black border around all text boxes. The user agent provides a dialog box allowing the user to override any author settings.
  • @@ Editors' Note: provide more than 2 options of highlighting options @@
• Related Resources for Success Criterion 1.3.2 (former 3.5.2):
  • To be written

1.4.1 (former 3.6.1) Configure Text: The user can globally set the following characteristics of visually rendered text content, overriding any specified by the author or user agent defaults: (Level A)

• (a) text scale (i.e., the general size of text) ,
• (b) font family, and
• (c) text color (i.e., foreground and background).

• Intent of Success Criterion 1.4.1 (former 3.6.1):
  Users need to able to access a wide range of font sizes, styles, colors, and other attributes in order to find the combination that works best for their particular needs. For example, some users want to increase font size to make text more legible, while other users want to reduce the font size to decrease the need to scroll the content. In providing these preferences, it is important to avoid making assumptions. For example, some users want to reduce the font size to decrease the need to scroll the content.
• Examples of Success Criterion 1.4.1 (former 3.6.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 tall. 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.
  • Tomas has extremely low vision and 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. He chooses not to have headings be proportionately larger than normal text because that would make them taller than his screen and so unreadable.
  • Browser A supports only 3 font sizes: Small, Medium, and Large. Lee, who has low vision, needs to use a font size of 16 pt, which is between the medium and large sizes. Browser A provides 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.
• Related Resources for Success Criterion 1.4.1 (former 3.6.1):
  • To be written

1.4.2 (former 3.6.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)

• Intent of Success Criterion 1.4.2 (former 3.6.2):
  The relative size of text provides visual cues that help in understanding and navigating web content and because some content may be authored in a way that would make it difficult or impossible to understand when if font distinctions were hidden. For example, headlines in a larger font than the body text. Users who set preferences to enlarge or reduce the text size need to have these visual cues preserved.
• Examples of Success Criterion 1.4.2 (former 3.6.2): Lee finds text easiest to read at 16 pt Palatino, but can chooses to have her browser display all in the Palatino font and at least 16 pt in size. She needs the headlines to scale proportionally (e.g. 24 pt) in order to preserve headline prominence.
• Related Resources for Success Criterion 1.4.2 (former 3.6.2):
  • To be written

1.4.3 (former 3.6.3) Option Range: The range of options for each text characteristic includes at least (Level A):

• (a) the range offered by global preference settings supported by the operating environment (i.e. configured though the Control Panel or System) utility, or
• (b) if no such utility is available, the range supported by the conventional APIs of the operating environment for drawing text.

• Intent of Success Criterion 1.4.3 (former 3.6.3):
  Users need to be able to access the full range of text characteristics that the operating system supports. The full range may be determined by the operating environment (as determined by the settings). If platform does not provide a range of text characteristics in the control panel, then whatever text characteristics are supported by drawing programs for that operating environment, must be made available to the user.
• Examples of Success Criterion 1.4.3 (former 3.6.3):
  • Browser A supports only 3 font sizes: Small, Medium, and Large. Lee, who has low vision, needs to use a font size of 16 pt, which is between the medium and large sizes. Browser A provides 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.
    
• Related Resources for Success Criterion 1.4.3 (former 3.6.3):
  • To be written

1.5.1 (former 3.7.1) Global Volume: The user can independently adjust the volume of all audio tracks the user agent renders, relative to the global volume level set through operating environment mechanisms. However, the user agent may only override a global mute on explicit user request and if the user has been cautioned about the implication. However, if audio is muted at the global level the user agent should not override this unless the behavior is optional, not enabled by default, and the user is cautioned as to its implications. (e.g. the alarm clock application on a mobile device has an option to play the alarm even if the system is muted, provided the check box is normally unchecked and is accompanied by text cautioning the user about this behavior. (Level A) The user can globally set volume of all audio tracks it renders (including a "mute" setting) through available operating environment mechanisms. (Level A)

• Intent of Success Criterion 1.5.1 (former 3.7.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 (former 3.7.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 (former 3.7.1):
  • To be written

1.5.2 (former 3.7.2) Speech Volume: The user can adjust the volume of all audio tracks the user agent renders, independently or relative to the volume level at the operating environment. (Level A)

• Intent of Success Criterion 1.5.2 (former 3.7.2):
  Users of a screen reader or self voicing browser may encounter content where the presentation volume of an audio track makes it difficult to hear the text-to-speech synthesis of their screen reader or browser. Users should be able to set the individual volume of audio tracks rendered by the user agent, including text-to-speech synthesis, independent of the operating environment's volume settings.
• Examples of Success Criterion 1.5.2 (former 3.7.2):
  • A self-voicing user agent provides separate audio volume controls the speech synthesizer and audio tracks rendered from content. The user may define default volume levels through a preferences dialog that is retained across browsing sessions.
  • A user encounters a page a video which begins playback on page load complete. A volume control for rendered audio tracks allows the user to immediately silence the audio track, while leaving their screen reader's text-to-speech synthesizer volume at their preferred level. @@ Editors' Note: New examples are needed that are platform specific. @@
• Related Resources for Success Criterion 1.5.2 (former 3.7.2):
  • To be written

1.6.1 (former 3.8.1) Speech Rate and Volume: The user can specify the following for synthesized speech: (Level A)

• speech rate and
• speech volume (independently of other sources of audio).

1.6.2 (former 3.8.2) Speech Pitch and Range: The user can specify the following for synthesized speech: (Level AA):

• (a) pitch ("pitch" refers to the average frequency of the speaking voice), and
• (b) pitch range ("pitch range" specifies a variation in average frequency),

1.6.3 (former 3.8.3) Advanced Speech Characteristics: The user can specify all of the speech characteristics offered by the speech synthesizer. (Level AAA)

• Intent of Success Criterion 1.6.1 (former 3.8.1), 1.6.2 (former 3.8.2), 1.6.3 (former 3.8.3):
  The objective of these success criteria is to allow the user to customize the specified speech characteristics to settings that allow the user to perceive and understand the audio information.
  
  Users may need to increase the volume to a level within their range of perception for example. Users may also wish to increase the rate of synthesized speech presentation because they can understand it at a rate faster than the default setting of the user agent.
  
  Success criterion 1.6.1 (former 3.8.1) covers the characteristics that users most commonly need to adjust and that are adjustable in most technologies, while success criterion 1.6.2 (former 3.8.2) covers characteristics that are less widely altered and less widely supported.
• Examples of Success Criterion 1.6.1 (former 3.8.1), 1.6.2 (former 3.8.2), 1.6.3 (former 3.8.3):
  • A telephone-based web browser starts reading back a web page. The user can press a key to increase the rate at which the information is read back. Similarly, the user may be using this telephone browser in a noisy environment such as a crowded subway. With a key press the user can quickly increase the volume of the speech being heard.
  • @@ Editors' Note: Add an example for 1.6.2 (former 3.8.2) @@
• Related Resources for Success Criterion 1.6.1 (former 3.8.1), 1.6.2 (former 3.8.2), 1.6.3 (former 3.8.3):
  • To be written

1.6.4 (former 3.8.4) Synthesized Speech Features: For synthesized speech, the following features are provided: (Level AA)

• (a) user-defined extensions to the synthesized speech dictionary,
• (b) "spell-out", where text is spelled one character at a time, or according to language-dependent pronunciation rules,
• (c) at least two ways of speaking numerals: one where numerals are 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 one where full numbers are spoken (e.g. "one thousand, two hundred and three point five").
• (d) at least two ways of speaking punctuation: one where punctuation is spoken literally, and one where punctuation is rendered as natural pauses.

• Intent of Success Criterion 1.6.4 (former 3.8.4):
  The synthetic speech presentation of text can be difficult to understand at times. Success criteria here are aimed at giving the user the ability to adjust the way in which the speech synthesizer presents text to improve understandability.
  @@ Editors' Note: Add text on treatment of currency and international customs for reading currency numbers. @@
• Examples of Success Criterion 1.6.4 (former 3.8.4):
  • The speech synthesizer incorrectly pronounces technical terms employed in the user's organization. These terms are consistently mispronounced in a way that makes it difficult for the audio user to distinguish them, even though they are instantly distinguishable when displayed as text.. A dictionary allows the user to enter a spelling of the name that produces the correct pronunciation from the synthetic speech.
  • A speech synthesizer is repeating a phone number. The user wishes to easily copy this number so switches to a mode where each digit is spoken as a unique word e.g. five, five, five and so on.
• Related Resources for Success Criterion 1.6.4 (former 3.8.4):
  • To be written

1.7.1 (former 3.9.1) Author Style Sheets: If one or more author style sheets are defined, the user has the following options: (Level A)

• (a) select and apply one or more author style sheets, or
• (b) turn off author style sheets.

1.7.2 (former 3.9.2) User Style Sheets: If one or more user style sheets are defined, the user has the following options: (Level A)

• (a) select and apply one or more user style sheets, or
• (b) turn off user style sheets.

• Intent of Success Criterion 1.7.1 (former 3.9.1) & 1.7.2 (former 3.9.2):
  CSS stylesheets allow for extensive customization of 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 of web browsers can fully take advantage of the stylesheets offered by web authors or that the users have created.
• Examples of Success Criterion 1.7.1 (former 3.9.1) & 1.7.2 (former 3.9.2):
  • A user finds yellow text on a black background easiest to read. When a web site is loaded, the user agent provides a menu where the user can select between several stylesheets that the web author has created for the web site. The user selects a stylesheet named yellow on black from a menu in the user agent listing all available stylesheets. The web content is then rendered using this stylesheet.
  • On a shared computer a web site is rendered with black text on a white background that is normally in full color. The user agent provides a menu where the user can de-select a user-defined stylesheet has been applied to the web page and the user easily disables this stylesheet. The web site is now rendered in full color.
• Related Resources for Success Criterion 1.7.1 (former 3.9.1) & 1.7.2 (former 3.9.2):
  • CSS 2 Recommendation: cascade weight rules

1.8.1 (former 3.10.1) Highlight Viewport: The viewport with the input focus (including nested viewports and their containers) is highlighted, and the user is able to customize attributes of the highlighted mechanism, including, but not limited to, shape, size, stroke width, color, and blink rate (if any). (Level A)

• Intent of Success Criterion 1.8.1 (former 3.10.1):
  When a user agent presents content using multiple viewports, users benefit from a clear indication of which viewport has focus. Simply relying upon text foreground and background colors to indicate focus may not provide sufficient, visually perceivable indication for users with low vision. Highlighting of viewport frames using both color, with sufficient contrast, and increase in viewport border thickness can provide multiple visual cues that indicate focus.
• Examples of Success Criterion 1.8.1 (former 3.10.1):
  • A music Web site allows the user to select which of the top 10 songs are available for listening. Each song is presented in a graphical viewport providing a music player. Using a keyboard based screen magnification tool, a low vision user tabs between songs, with the currently selected player viewport highlighted with a thick, yellow border against a dark gray background.
• Related Resources for Success Criterion 1.8.1 (former 3.10.1):
  • To be written

1.8.2 (former 3.10.2) Move Viewport to Selection and Focus: When a viewport's selection or input focus changes, the viewport moves as necessary to ensure that the new selection or input focus location is at least partially in the visible portion of the viewport.When a viewport's selection or input focus changes, the viewport moves as necessary to ensure that the new selection or input focus location is at least partially in the viewport. (Level A)

• Intent of Success Criterion 1.8.2 (former 3.10.2):
  When content is presented within a viewport and the content extends horizontally or vertically beyond the visible bounds of the viewport, the user must be able to move to a selectable element or elements which may be out of view, and to have the selected content automatically move into view. For keyboard based users and users of screen magnification tools, this allows users an efficient means to view selected content without having to utilize scrolling controls to locate and view the selection.
• Examples of Success Criterion 1.8.2 (former 3.10.2):
  • A screen magnification user is performing a spell check of a blog posting that is contained within a scrollable viewport. The text of the blog posting exceeds the vertical size of the viewport. The blogging software provides a key to move to the first, and then any subsequent, unrecognized words. With two unrecognized words in the posting, the user ignores the first selected word, and presses the keystroke to move to the next which is currently out of view in the last sentence of the posting. As the key is pressed, the viewport scrolls to show the selected word.
  • A user of a screen reader is showing a sighted colleague how to complete a registration form contained within a viewport. The form exceeds the vertical bounds of the viewport, requiring vertical scrolling to view the complete form content. As the screen reader completes each form entry and presses the tab key, the next form control in the tab order scrolls into view if it is not already visible in the viewport.
• Related Resources for Success Criterion 1.8.2 (former 3.10.2):
  • To be written

1.8.3 (former 3.10.4) Resizable: The user has the option to make graphical viewports resizable, within the limits of the display, overriding any values specified by the author. (Level A)

• Intent of Success Criterion 1.8.3 (former 3.10.4):
  If a graphical viewport contains content that exceeds the dimensions of the viewport, users should have the option to increase the size of the viewport to allow the full image to be displayed without scrolling, within the limits of the physical display screen. 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 being able to view the complete image.
• Examples of Success Criterion 1.8.3 (former 3.10.4):
  • A viewport is used to display an image depicting an organization chart. A user with a learning disability has difficulty maintaining a mental representation of the organizational linkages for items out of view. In order to facilitate their understanding of the organization, the user drags the sizing icon on the corners of the viewport to allow the entire chart to be displayed.
• Related Resources for Success Criterion 1.8.3 (former 3.10.4):
  • To be written

1.8.4 (former 3.10.5) Scrollbars: Graphical viewports include scrollbars if the rendered content (including after user preferences have been applied) extends beyond the viewport dimensions, overriding any values specified by the author. (Level A)

• Intent of Success Criterion 1.8.4 (former 3.10.5):
  When rendered content exceeds the horizontal or vertical bounds of a graphical viewport, scrollbars provide a visible indication that not all of the rendered content is currently visible within the viewport. The scrollbars provide indication to users who may not be able to otherwise recognize that the rendered content is not fully visible.
• Examples of Success Criterion 1.8.4 (former 3.10.5):
  • A Web site presents a recipe within a viewport, and the length of the recipe exceeds the vertical and horizontal dimension of the viewport, though the step by step graphical depiction of the recipe does not make this obvious. A user following the recipe, uses the scroll bar to recognize that additional steps may be present, and scrolls them into view.
• Related Resources for Success Criterion 1.8.4 (former 3.10.5):
  • To be written

1.8.5 (former 3.10.6) Viewport History: For user agents that implement a viewport history mechanism (e.g. "back" button), the user can return to any state in the viewport history, restoring the prior point of regard, input focus and selection.If the user agent maintains a viewport history mechanism (e.g., via the "back button") that stores previous "viable" states (i.e., that have not been negated by the content, user agent settings or user agent extensions). It maintains information about the page and embedded controls, including viewport scrolling, selection and keyboard focus. It restores the saved values when the user returns to a state in the history. (Level A)

1.8.6 (former 3.10.7) Open on Request: The user can specify whether or not top-level viewports (e.g. windows or tabs) open only with an explicit user request or confirmation. The user has the option of having top-level viewports (e.g., windows) only open on explicit user request. In this mode, instead of opening a viewport automatically, notify the user and allow the user to open it with an explicit request (e.g., by confirming a prompt or following a link generated by the user agent). (Level AA)

1.8.7 (former 3.10.8) 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. When configured to allow top-level viewports to open without explicit user request, the user has the option to specify that if a top-level viewport opens, it does not take the active keyboard focus . (Level AA)

• Intent of Success Criteria 1.8.5 (former 3.10.6), 1.8.6 (former 3.10.7) & 1.8.7 (former 3.10.8):
  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.5 (former 3.10.6), 1.8.6 (former 3.10.7) & 1.8.7 (former 3.10.8):
  • A web page is loaded in the browser that triggers a secondary page (typically known as a pop-up) to open. The user agent presents the user with the initial page requested and an alert that additional content is available. The user can choose to have this pop-up content shown or not, remaining in control of what is displayed in the user agent's viewport. A user agent may also be configured so that pop-ups do open automatically because the user has chosen to automatically have this content available. The user has a setting however to configure pop-ups such that they open in the background. Hence when visiting a web page with this secondary content, focus remains in the primary viewport with the initial page content requested. The user agent alerts the user that secondary content is available in another viewport and the user can activate this viewport on request, perhaps with a click on the notification mechanism.
• Related Resources for Success Criteria 1.8.5 (former 3.10.6), 1.8.6 (former 1.8.6 (former 3.10.7)) & 1.8.7 (former 3.10.8):
  • To be written

1.8.9 (former 3.10.10) Close Viewport: The user can close any top-level viewports (e.g. windows or tabs) . (Level AA)
Note: Dialog boxes or other special purpose viewports that provide limited functionality, do not have to spawn all the user-requested features that do not apply to that special function.

• Intent of Success Criterion 1.8.9 (former 3.10.10):
  Put the user in control of what viewports the user agent has opened. This reduces distractions from undesired viewports being opened for the user.
• Examples of Success Criterion 1.8.9 (former 3.10.10):
  • @@ Editors' Note: Add example of "An advertisement opens which has no close button". @@
  • A user has multiple viewports open such as from a user agent that supports tabbed browsing and is finished viewing content in one or many of them. The user activates a close button on the viewports that are to be closed and they are closed by the user agent.
• Related Resources for Success Criterion 1.8.9 (former 3.10.10):
  • To be written

1.8.10 (former 3.10.11) Same UI: The user can specify that all top-level viewports (e.g. windows or tabs) follow the current user interface configuration. The user has the option of having all top-level viewports (e.g. windows or tabs) follow the same user interface configuration as the current or spawning viewport. (Level AA)

• Intent of Success Criterion 1.8.10 (former 3.10.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.10 (former 3.10.11):
  • An individual using magnification software may know that web content begins one inch from the top of the screen in the user agent and has magnification software configured to present content starting at this location. Offering the ability to have all viewports open with the same user interface means the user can quickly focus on the web content of interest without having to orient to different UI configurations each time a viewport opens.
  • @@ Editors' Note: Add example of a user with cogitive issues wanting a limited UI and configures it once, and wants all spawned windows to follow that configuration. @@
• Related Resources for Success Criterion 1.8.10 (former 3.10.11):
  • To be written

1.8.11 (former 3.10.12) Indicate Viewport Position: The user can determine the viewport's position relative to the full extent of the rendered content. (Level AA) Indicate the viewport's position relative to rendered content (e.g., the proportion along an audio or video timeline, the proportion of a Web page before the current position ), and what proportion of the content is currently visible in the viewport along either vertical or horizontal dimension. (Level AAA)

• Intent of Success Criterion 1.8.11 (former 3.10.12):
  This criteria targets the ability for a user to easily understand where they are located relative to the total content available for rendering and the amount of content relative to the total being displayed.
• Examples of Success Criterion 1.8.11 (former 3.10.12):
  • A user navigates to a lengthy web page and begins paging through the content. A scroll bar visually indicates the position within the content as the user pages and also that with each paging action only a small portion of the content is being rendered. Another user accesses this web page with a screen reader and has the percentage that the page is scrolled communicated by the screen reader because the user agent makes information from the scroll bar available programmatically.
• Related Resources for Success Criterion 1.8.11 (former 3.10.12):
  • To be written

• Intent of Guideline 1.9 (former 3.11)
  Understanding and controlling focus is key to successful interaction with a user agent and its content. The overall purpose of Guideline 1.9 is to ensure that the user can reliably identify the focus location, and use it to navigate through and manipulate both the content and user interfaces of the user agent, its plug-ins and extensions.

1.9.1 (former 3.11.1) Keyboard Focus: At least one keyboard focus is provided for each viewport (including frames), where enabled elements are part of the rendered content. (Level A)

• Intent of Success Criterion 1.9.1 (former 3.11.1):
  Users need to be able to tell where the keyboard focus is in order to navigate or manipulate content; without it, a user cannot be sure what effect their next keystroke will have. Cursors are the visual indication of this location, and their locations are also conveyed to assistive technology for users not relying on sight (see success criterion _._._). When the sighted user expects a cursor and does not see one, they can assume that it's in a portion of the content that has scrolled outside the visible portion of the viewport.
• Examples of Success Criterion 1.9.1 (former 3.11.1):
  • A user launches a web browser and navigates to a web page. The user starts pressing the tab key and focus begins moving through the links on the webpage.
• Related Resources for Success Criterion 1.9.1 (former 3.11.1):
  • To be written

1.9.2 (former 3.11.2) Current Focus: The user can make the keyboard focus of each viewport the active input focus. (Level A)

• Intent of Success Criterion 1.9.2 (former 3.11.2):
  T
• Examples of Success Criterion 1.9.2 (former 3.11.2):
  • A .
• Related Resources for Success Criterion 1.9.2 (former 3.11.2):
  • To be written

1.9.3 (former 3.11.3) User Interface Focus: An active input focus is provided. (Level A)

• Intent of Success Criterion 1.9.3 (former 3.11.3):
  T
• Examples of Success Criterion 1.9.3 (former 3.11.3):
  • A user agent has several menus, toolbars and other controls. As the user presses a key to move to each item on one of the toolbars, the fact that this toolbar item is the active control is made clear through a focus rectangle. When the user switches to a menu, highlighting indicates the active menu element.
• Related Resources for Success Criterion 1.9.3 (former 3.11.3):
  • To be written

1.9.4 (former 3.11.4) Extensions Focusable: The keyboard focus can navigate within extensions to the user interface. (Level A)

• Intent of Success Criterion 1.9.4 (former 3.11.4):
  T
• Examples of Success Criterion 1.9.4 (former 3.11.4):
  • A developer creates an extension to a user agent that allows the user to add notes about each web page being visited. A user can press a key to move focus to the user interface of this extension and interact with the funtionality offered by the extension. Similarly, the user presses another key to move focus back to the main viewpoert forthe user agent.
• Related Resources for Success Criterion 1.9.4 (former 3.11.4):
  • To be written

1.9.5 (former 3.11.5) Hand-Off Focus: The user agent programmatically notifies any nested user agent(s) (e.g., plug-ins) when active input focus moves to a nested agent. (Level A)

• Intent of Success Criterion 1.9.5 (former 3.11.5):
  T
• Examples of Success Criterion 1.9.5 (former 3.11.5):
  • A browser plug-in is installed to play a popular media format. When the user tabs to the controls for the plug-in, the user agent notifies the plug-in to handle keyboard interaction.
• Related Resources for Success Criterion 1.9.5 (former 3.11.5):
  • To be written

1.9.6 (former 3.11.6) Retrieve Focus: At any time, the user agent is able to retrieve input focus from a nested viewport (including nested viewports that are user agents). (Level A)

• Intent of Success Criterion 1.9.6 (former 3.11.6):
  T
• Examples of Success Criterion 1.9.6 (former 3.11.6):
  • A .
• Related Resources for Success Criterion 1.9.6 (former 3.11.6):
  • To be written

1.9.7 (former 3.11.7) Return Focus: An embedded user agent is responsible for notifying the embedding user agent that active input focus should move back to it. (Level A)

• Intent of Success Criterion 1.9.7 (former 3.11.7):
  T
• Examples of Success Criterion 1.9.7 (former 3.11.7):
  • A .
• Related Resources for Success Criterion 1.9.7 (former 3.11.7):
  • To be written

1.9.8 (former 3.11.8) Bi-Directional: The user can move the keyboard focus forward or backward to any enabled element in the viewport. (Level A)

• Intent of Success Criterion 1.9.8 (former 3.11.8):
  T
• Examples of Success Criterion 1.9.8 (former 3.11.8):
  • A .
• Related Resources for Success Criterion 1.9.8 (former 3.11.8):
  • To be written

1.9.9 (former 3.11.9) Sequential Navigation: If the author has not specified a navigation order, the default is sequential navigation, in document order. (Level A)

• Intent of Success Criterion 1.9.9 (former 3.11.9):
  T
• Examples of Success Criterion 1.9.9 (former 3.11.9):
  • A .
• Related Resources for Success Criterion 1.9.9 (former 3.11.9):
  • To be written

1.9.10 (former 3.11.10) Only on User Request: The user can specify that the keyboard focus of a viewport only change on explicit user request. (Level A)

• Intent of Success Criterion 1.9.10 (former 3.11.10):
  T
• Examples of Success Criterion 1.9.10 (former 3.11.10):
  • A .
• Related Resources for Success Criterion 1.9.10 (former 3.11.10):
  • To be written

1.9.11 (former 3.11.11) On Focus: The user can ensure that moving the keyboard focus to or from an enabled element does not cause the user agent to take any further action. (Level A)

• Intent of Success Criterion 1.9.11 (former 3.11.11):
  T
• Examples of Success Criterion 1.9.11 (former 3.11.11):
  • A .
• Related Resources for Success Criterion 1.9.11 (former 3.11.11):
  • To be written

1.10.1 (former 3.12.1) Text View: The user can view all text source that is available to the user agent. For content authored in text formats, a view of the text source is provided. (Level AA)

• Intent of Success Criterion 1.10.1 (former 3.12.1):
  The source view is the ultimate fallback 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.10.1 (former 3.12.1):
  • When the content author failed to provide alt text or longdesc for an image, the user can, as a last resort, try to get some information by examining the source to see the image's URI, class, and similar attributes.
  • When the user wants to create a customized style sheet for a Web site, they need to identify the style, class, and id attributes it uses.
• Related Resources for Success Criterion 1.10.1 (former 3.12.1):
  • To be written

1.10.2 (former 3.12.2) Outline View: An "outline" view of rendered content is provided, composed of labels for important structural elements (e.g. heading text, table titles, form titles, and other labels that are part of the content). (Level AA)

Note: The constitutes the important structural elements by the user (See 1.10.3). What constitutes a label is defined by each markup language specification. For example, in HTML, a heading (H1-H6) is a label for the section that follows it, a CAPTION is a label for a table, and the title attribute is a label for its element.

• Intent of Success Criterion 1.10.2 (former 3.12.2):
  Outline views can help all users get a simplified view or overview of a document. They are particularly useful for users with memory or cognitive disabilities, as well as users with serial access to content or who navigate sequentially. The outline view is a type of summary view and should reduce orientation time. A navigable outline view will add further benefits for these users.
• Examples of Success Criterion 1.10.2 (former 3.12.2):
  • A Web browser provides an optional panel displaying a hierarchical list of the headers and tables in the current document. The user is able to expand or shrink portions of the outline view for faster access to important parts of content.
  • A Web browser provides a command to use CSS display and visibility properties to hide all content other than important structural elements such as titles, headings, and table headings.
  • A Web browser provides a structured view of form controls (e.g., those grouped by LEGEND or OPTGROUP in HTML) along with their labels.
  • Amaya table of contents view @@ Editors' Note: Insert photo@@
    This image shows the table of contents view provided by Amaya [AMAYA]. This view is coordinated with the main view so that users may navigate in one viewport and the focus follows in the other. An entry in the table of contents with a target icon means that the heading in the document has an associated anchor.
• Related Resources for Success Criterion 1.10.2 (former 3.12.2):
  • This Success Criterion (1.10.2 (former 3.12.2)) deals with making document structure perceivable to the user. It is complimentary to Guideline 4.7 which deals with making document structure navigable.

1.10.3 (former 3.12.3) Configure Set of Important Elements: The user can configure the set of important elements for the hierarchical view, including by element type (e.g., headers). (Level AAA)The user can be presented with a hierarchical view of the rendered content that conveys associations implied by author-specified presentation attributes (i.e. position and appearance). (Level AA)

• Intent of Success Criterion 1.10.3 (former 3.12.3):
  Sometimes authors will visually convey relationships between elements by spatially grouping them, by giving them the same coloration or background, and so forth. Users may not be able to perceive those attributes, such as when using a screen reader, or when strong magnification makes it difficult to make a mental model of the screen layout. In those cases the user agent can assist by providing a view of the data that groups elements that that user agent perceives as implying relationships.
• Examples of Success Criterion 1.10.3 (former 3.12.3):
  • To be written
• Related Resources for Success Criterion 1.10.3 (former 3.12.3):
  • To be written

1.11.2 (former 3.13.2) Extended Link Information: The following information is provided for each link (Level AAA):

• link title,
• technology type (of the linked Web resource)
• internal/external: (whether the link is internal to the resource e.g., the link is to a target in the same Web page)

• Intent of Success Criterion 1.11.2 (former 3.13.2):
  To be written
• Examples of Success Criterion 1.11.2 (former 3.13.2):
  • To be written
• Related Resources for Success Criterion 1.11.2 (former 3.13.2):
  • To be written

2.1.1 (former 4.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 mouse input or other input methods in addition to keyboard operation. (Level A)

• Intent of Success Criterion 2.1.1 (former 4.1.1):
  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. Therefore, ensure that the user can 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), and
  • 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. Furthermore, the user agent should satisfy this checkpoint by offering 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 (former 4.1.1) :
  • The user must be able to do the following through the keyboard alone (or pointing device alone or voice alone):
    • Select content and operate on it. For example, if the user can select rendered text with the mouse and make it the content of a new link by pushing a button, they also need to be able to do so through the keyboard and other supported devices. Other operations include cut, copy, and paste.
    • Set the focus on viewports and on enabled elements.
    • Install, configure, uninstall, and update the user agent software.
    • Use the graphical user interface menus. Some users may wish to use the graphical user interface even if they cannot use or do not wish to use the pointing device.
    • Fill out forms.
    • Access documentation.
  • An author uses the CSS overflow property to constrain the size of a block of content. The user agent provides scroll bars to display text that overflows the container. The user can use the keyboard to enter the element and operate the scrollbars to visually access the content. The user can return to the main flow of the next element on the page (see SC 2.1.3 (former 4.1.3))
  • The author codes a volume control slider widget. The user can focus on the widget, and using the arrow keys to increase or decrease the volume, and then hit another key to move to the next element in the content.
• Related Resources for Success Criterion 2.1.1 (former 4.1.1):
  • Microsoft Keyboard accessibility document
  • Apple keyboard
  • Unix

2.1.2 (former 4.1.2) Specify preferred keystrokes:: The user can override any keyboard shortcut including recognized author supplied shortcuts (e.g accesskeys) and user interface controls, except for conventional bindings for the operating environment (e.g., for access to help). (Level A)

• Intent of Success Criterion 2.1.2 (former 4.1.2):
  Some users may be able to hit certain keys on the keyboard with greater ease than others. Assistive technology software typically has extensive keyboard commands as well. The goal of this SC is to enable the user to be in control of what happens when a given key is pressed and use the keyboard commands that meet his or her needs.
  
• Examples of Success Criterion 2.1.2 (former 4.1.2):
  • Laura types with one hand and finds keys on the left side of the keyboard easier to press. She browses to a web page and notices that the author has assigned access keys using keys from the right side of the keyboard. She opens a dialog in the user agent and reassigns the access keys from the web page to the left side of the keyboard home row.
  • Elaine's screen magnification program uses alt+m to increase the size of the magnified area of the screen. She notices that in her web browser, alt+m is a hotkey for activating a home button that stops her from being able to control her magnification software. She opens a hotkey reassignment feature in the user agent, and sets alt+o to be the new hotkey for the home button. Her screen magnification software now works correctly.
    
• Related Resources for Success Criterion 2.1.2 (former 4.1.2):
  • To be written

2.1.3 (former 4.1.3) No Keyboard Trap (Minimum): The user agent prevents keyboard traps as follows (Level A):

• (a) in the UI: if keyboard focus can be moved to a component using the keyboard, then focus can be moved away from that component using standard sequential keyboard commands (e.g., TAB key)
• (b) in the rendered content: provides a documented direct keyboard command that will always restore keyboard focus to a known location (e.g., the address bar).
• (c) in the rendered content: provides a documented direct keyboard command that will always move keyboard focus to a subsequent focusable element

• Intent of Success Criterion 2.1.3 (former 4.1.3):
  Intent: If the user can put focus on an element, that they can remove focus and move on to the next element. This is often a problem 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 be able to take control back from the embedded object, no matter what it is.
  
• Examples of Success Criterion 2.1.3 (former 4.1.3):
  1. The user can press tab to put focus on an embedded object and can press shift-tab to move focus to the previous object and tab to move focus to the next object.
  2. The user has moved the focus to a toolbar extension that does not relinquish control back to the user agent. The user can press Alt-D to move focus to the address bar.
  3. The user has moved the focus to an embedded scripted application that was poorly programmed. the user can press alt-N (or any documented key combination) that overrides the scripting and moves the focus to the next element in the content.
• Related Resources for Success Criterion 2.1.3 (former 4.1.3):
  • Compound documents
  • Other SC in UAAG.

2.1.4 (former 4.1.4) Separate Selection from Activation: The user can specify that selection is separate from activation (e.g., navigating through a set of radio buttons without changing which is the active/selected option). (Level A)

• Intent of Success Criterion 2.1.4 (former 4.1.4):
  This is a repair function for when an author violates WCAG, but the user still needs to be able to read a page without necessarily activating any controls.
  
• Examples of Success Criterion 2.1.4 (former 4.1.4):
  • when a user opens a drop down menu from the keyboard, they must be able to use the arrow keys to move up and down the list, without triggering an action from the items they are moving past.
  • A list of radio buttons where putting the focus on the radio button to read it causes the radio button to be selected. The user should be able to arrow or tab through the list of radio buttons without causing any one to be selected. Selection is a separate discrete operation like spacebar. This overrides any author provided scripting behavior.
    
• Related Resources for Success Criterion 2.1.4 (former 4.1.4):
  • ARIA
  • WCAG

2.1.5 (former 4.1.5) Standard Text Area Navigation Conventions: Views that render text support the standard text area conventions for the operating environment, including, but not necessarily limited to: character keys, Backspace/Delete, Insert, arrow key navigation (e.g., caret browsing), Page Up/Page Down, navigate to start/end, navigate by paragraph, shift-to-select mechanism. (Level A)

• Intent of Success Criterion 2.1.5 (former 4.1.5) :
  Providing a full set of keyboard inputs allows users to efficiently--or at all--perform necessary tasks. Making these inputs consistent within and across programs greatly reduces learning curve, cognitive load, and errors.
• Examples of Success Criterion 2.1.5 (former 4.1.5) :
  • Directional keys, letter keys, and the Enter key function should allow navigation within and activation of drop-down menus.
  • Ctrl+C or Command+C should copy selected text to the clipboard, allowing the user to avoid manually retyping, and possibly needing to memorize, large amounts of data.
    @@ Editors' Note: comment - what happens when things are not consistent. closing dialog boxes are inconsistent ESC or ALT-F4, might be text area keyboard conventions/controls, not just navigation. @@
• Related Resources for Success Criterion 2.1.5 (former 4.1.5) :
  • To be written

2.1.6 (former 4.1.6) Present Direct Commands in Rendered Content: The user can have any recognized direct commands (e.g. accesskey) in rendered content be presented with their associated elements (e.g. "[Ctrl+t]" displayed after a link whose accesskey value is "t", or an audio browser reading the value or label of a form control followed by "accesskey control plus t"). (Level A)

• Intent of Success Criterion 2.1.6 (former 4.1.6) :
  Make it easy to for users to discover or be reminded of keyboard shortcuts and similar commands without leaving the context in which they're working. Easy keyboard access is especially important for people who cannot easily use a mouse.
• Examples of Success Criterion 2.1.6 (former 4.1.6) :
  • "[Ctrl+t]" displayed after a link whose accesskey value is "t".
  • An audio browser reading the value or label of a form control followed by "accesskey control plus t").
  • Mnemonic letters in menu titles are shown with an underline. @@ Editors' Note: comment - applicable shortcut indicated or otherwise highlighted@@
• Related Resources for Success Criterion 2.1.6 (former 4.1.6) :
  • To be written

2.1.7 (former 4.1.7) Present Direct Commands in User Interface: The user has the option to have any direct commands (e.g. keyboard shortcuts) in the user agent user interface be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). (Level AA)

• Intent of Success Criterion 2.1.7 (former 4.1.7) :
  For many users, including those who use the keyboard or and input method such as speech, the keyboard is often a primary method of user agent control. It is important that direct keyboard commands assigned to user agent functionality be discoverable as the user is exploring the user agent.
• Examples of Success Criterion 2.1.7 (former 4.1.7) :
  • The speech input user who sees a button on a toolbar needs to be able to determine that ctrl+p is the keyboard equivalent for activating the print button. If such key assignments are not displayed as part of the user interface by default, a user agent should have an option to alter UI display to include all direct hotkey assignments visually as part of the controls the hotkeys activate.
• Related Resources for Success Criterion 2.1.7 (former 4.1.7) :
  • To be written

2.1.8 (former 4.1.8) Keyboard Navigation: The user can use the keyboard to navigate from group to group of focusable items and to traverse forwards and backwards all of the focusable elements within each group. Groups include, but are not limited to, toolbars, panels, and user agent extensions. (Level AA)

• Intent of Success Criterion 2.1.8 (former 4.1.8) :
  Let the user navigate between sections without having to sequentially navigate through everything in every section. Efficient keyboard navigation is especially important for people who cannot easily use a mouse.
• Examples of Success Criterion 2.1.8 (former 4.1.8) :
  • Ctrl+Tab moves the focus to the first navigable item in the next frame.
  • The Tab key moves the focus to or away from a group of radio buttons, and then directional keys move between buttons within that group.
• Related Resources for Success Criterion 2.1.8 (former 4.1.8):
  • To be written

2.1.9 (former 2.1.9 (former 4.1.9) ) Important Command Functions: Important command functions (e.g. related to navigation, display, content, information management) are available using a single or sequence of keystrokes or key combinations. (Level AA)

• Intent of Success Criterion 2.1.9 (former 4.1.9) :
  Let the user access commonly used functions as efficiently as possible. Efficient keyboard navigation is especially important for people who cannot easily use a mouse.
• Examples of Success Criterion 2.1.9 (former 4.1.9):
  • The user can open a document by pressing Ctrl+O or Command+O.
  • The user can temporarily enlarge the rendered content by pressing Ctrl+Plus, rather than having to invoke a menu, choose a command to display a dialog box, select a tab, etc.
• Related Resources for Success Criterion 2.1.9 (former 4.1.9) :
  • Links to 1.1. Comply with applicable specifications and conventions

2.1.10 (former 4.1.10) Override of UI Keyboard Commands: The user can override any keyboard shortcut binding for the user agent user interface except for conventional bindings for the operating environment (e.g. access to help). The rebinding options must include single-key and key-plus-modifier keys if available in the operating environment. (Level AA)

• Intent of Success Criterion 2.1.10 (former 4.1.10) :
  Users need to be in control of how they interact with the user agent. Assistive technology and physical keyboard input needs mean that certain keyboard combinations are easier for a user to enter.
• Examples of Success Criterion 2.1.10 (former 4.1.10) :
  • Ctrl+f may be a command in a screen reader to read the item with focus and this is also typically a user agent find command. The user agent should allow the user to reassign the find command to a non-conflicting key binding. To allow this level of user control, the user agent could provide a list of user interface features and default keyboard assignments with options for the user to assign new key combinations. User keyboard customizations should be saved similar to other user preferences by the user agent.
  • @@ Editors' Note: another example - one handed keyboardist needs to map all keys to the left side of the keyboard @@
• Related Resources for Success Criterion 2.1.10 (former 4.1.10) :
  • To be written

2.1.11 (former 4.1.11) User Override of Accesskeys: The user can override any recognized author supplied content keybinding (i.e. access key). The user must have an option to save the override of user interface keyboard shortcuts so that the rebinding persists beyond the current session. (Level AA)

• Intent of Success Criterion 2.1.11 (former 4.1.11)
  Content authors may utilize the Accesskey attribute to define short cut keys which allow quick access to specific elements, actions, or parts of their Web content. The author-selected short cuts may utilize keystrokes that are unique to their site, differing from conventions used, and or familiar, to users of other similar sites, or sites offering similar functionality. Users of assistive technologies who rely upon keyboard input may wish to have a consistent mapping of shortcut keys to similar, or common actions or functions across the sites they visit.
  
  User agents should allow users to define a preferred key combination for specific instances of author defined accesskeys. The user should have the option to make any defined override to be persistent across browsing sessions.
  
  User agents may also offer the user the option to automatically apply preferred key combinations for content which has author supplied accesskey bindings, based upon the associated text, label, or ARIA role, and which override any author specified keybinding for that page content.
• Examples of Success Criterion 2.1.11 (former 4.1.11) :
  • A speech recognition user has defined standard commands to access commonly used parts of a Web site. For example, speaking the the command "site search" will take the user to a Web site's search function. A site author may assign an access key to set focus to the search input field, basing the accesskey on the first letter of the search engine used (e.g., G for Google or B for Bing, rather than the mnemonic S for search). The speech user has specified an override key mapping of S, which is consistent with the keystroke issued by the speech recognizer they are using.
  • A mobile device user, whose primary keyboard interface is their phone's numeric keypad, maps common Web site actions to numeric shortcut keys. For example, the user prefers to have the 1 key to activate a site's "skip to content" function. An author of a site visited daily by this user defines "S" as the accesskey for the skip to content function. The user overrides the author defined accesskey of "S" with "1".
  • @@ Editors' Note: good place to add i18n example, accesskey - o umlaut, but not on local keyboard@@
• Related Resources for Success Criterion 2.1.11 (former 4.1.11) :
  • To be written

2.1.12 (former 4.1.12) Specify preferred keystrokes: The user can override any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and user interface controls, except for conventional bindings for the operating environment (e.g. access to help). (Level AA)

• Intent of Success Criterion 2.1.12 (former 4.1.12)
  N/A
• Examples of Success Criterion 2.1.12 (former 4.1.12) :
  • To be written
• Related Resources for Success Criterion 2.1.12 (former 4.1.12) :
  • To be written

2.2.1 (former 4.2.1) List event handlers: The user can, through keyboard input alone, call up a list of input device event handlers explicitly associated with the keyboard focus element. (Level A)

• Intent of Success Criterion 2.2.1 (former 4.2.1) :
  Users interacting with a web browser may be doing so by voice, keyboard, mouse or another input technology or a combination of any of these. No matter how the user is controlling the user agent, he or she need to know all the input methods assigned to a particular piece of content.
• Examples of Success Criterion 2.2.1 (former 4.2.1) :
  • A user may tab to a link that has a flyout menu that appears OnMouseOver. The User agent needs to notify the user of this menu so he or she can know the menu is available. Other success criteria ensure the keyboard user here can interact with this menu.
• Related Resources for Success Criterion 2.2.1 (former 4.2.1) :
  • To be written

2.2.2 (former 4.2.2) Activate any event handler: The user can, through keyboard input alone, activate any input device event handlers explicitly associated with the keyboard focus element. (Level A)

• Intent of Success Criterion 2.2.2 (former 4.2.2) :
  Although it should not do so, some Web content is designed to work only with certain input devices, such as a mouse, and make functionality available only through event handlers for those devices. Some users interacting with a web browser may be doing so by voice, keyboard, mouse or another input technology or a combination of any of these. No matter how the user is controlling the user agent, he or she must be able to activate any of the event handlers regardless of the interaction technology being used.
• Examples of Success Criterion 2.2.2 (former 4.2.2) :
  • A user who cannot use a mouse needs to activate a flyout menu that normally appears OnMouseOver. The user should be able to navigate to a link and activate it using keyboard shortcuts.
• Related Resources for Success Criterion 2.2.2 (former 4.2.2) :
  • To be written

2.2.3 (former 4.2.3) Activate all event handlers: The user can, through keyboard input alone, simultaneously activate all input device event handlers explicitly associated with the content focus element. (Level A)

• Intent of Success Criterion 2.2.3 (former 4.2.3) :
  One input method should not hold back another. People who don't use a mouse shouldn't necessarily have to map their input methods to the same steps a mouse user would take.
• Examples of Success Criterion 2.2.3 (former 4.2.3) :
  • Speech input users may combine moving the mouse up, left and clicking in a single command phrase.
  • A link has an onmousedown and an onmouseup event link. The keyboard user can use 1 key click to activate both events.
• Related Resources for Success Criterion 2.2.3 (former 4.2.3) :
  • To be written

2.3.1 (former 4.3.1) Timing Adjustable: Where time limits for user input are recognized and controllable by the user agent, the user can extend the time limit. (Level A)

• Intent of Success Criterion 2.3.1 (former 4.3.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.3.1 (former 4.3.1) :
  • News Alerts: A news organizations Web site 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 Web site 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.3.1 (former 4.3.1) :
  • To be written

2.4.1 (former 4.4.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)

• Intent of Success Criterion 2.4.1 (former 4.4.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.4.1 (former 4.4.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.4.1 (former 4.4.1) :
  • ITC Guidance Note for Licensees on Flashing Images and Regular Patterns in Television: http://www.ofcom.org.uk/tv/ifi/guidance/legacy/vrs_code_notes/flsh_imgs/gn_flash.pdf

2.4.2 (former 4.4.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) [WCAG 2.0]

• Intent of Success Criterion 2.4.2 (former 4.4.2) :
  
• Examples of Success Criterion 2.4.2 (former 4.4.2) :
• Related Resources for Success Criterion 2.4.2 (former 4.4.2) :

2.5.1 (former 4.5.1) Change Preference Settings The user can change settings that impact accessibility. (Level A)

2.5.2 (former 4.5.2) Persistent Accessibility Settings: User agent accessibility preference settings persist between sessions. (Level A)

2.5.3 (former 4.5.6) Restore all to default: The user can restore all preference settings to default values. (Level A)

2.5.4 (former 4.5.3) Multiple Sets of Preference Settings: The user can save and retrieve multiple sets of user agent preference settings. (Level AA)

2.5.5 (former 4.5.7) Restore related preferences to default: The user can restore groups of related preference settings to default values (e.g. reset keyboard shortcuts, reset colors and sizes of rendered content). (Level AA)

2.5.6 (former 4.5.8) Change preference setting outside the UI: The user can adjust preference settings from outside the user agent user interface. (Level AA)

2.5.7 (former 4.5.4) Portable Preference Settings:The user can transfer preference settings across locations onto a compatible system. (Level AAA)

2.5.8 (former 4.5.5) Preferences Wizard: A wizard helps the user to configure the accessibility-related user agent preferences (at least). (Level AAA)

• Intent of Success Criterion 2.5 (former 4.5) :
  Users who rely on accessibility settings do so for multiple reasons and may want to adjust software settings in many differing fashions. It is key to allow software settings that impact accessibility to be configured to meet these differing needs. The easier such settings are to discover, the more rapidly the user looking for such settings can tailor the software to suit his or her needs. Saving such configuration changes between browsing sessions allows the software to work the way the user wants each time the application is used.
• Examples of Success Criterion 2.5 (former 4.5) :
  • A user who relies on larger text sizes when browsing web pages, locates a text adjustment setting in a browser's menus. The user sets the text size to the size that makes web content readable. .
  • A user locates a control in a web browser called options. Activating this control leads to a series of tabs for adjusting multiple browser settings. One tab is listed as accessibility and has settings such as text size, use custom style sheet, display alternative text in place of images, enable caret browsing and other settings determined to be of benefit to users with disabilities.
  • A user is exploring settings for a web browser and locates an option called accessibility. The user is then guided through a series of questions asking about how he or she prefers to use software. Questions such as color preference, text size, ability to view images, the need for captions on videos and such are asked. When the user completes these questions, appropriate browser options are configured and stored.
  • A user who has configured accessibility settings in a browser needs to use that application in the same browser on another computer. The browser allows the user to transfer such settings from one computer to another, saving the need to reconfigure the second machine.
  • @@ Editors' Note: add another example of persistence@@
• Related Resources for Success Criterion 2.5 (former 4.5) :
  • SCORM Editors' Note: (Jutta's work) - find current reference @@

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

• Intent of Success Criterion 2.6.1 (former 4.6.1) :
  To provide a function that allows the user to easily locate desired information in rendered or alternative text. Give the option of searching the alternative content. In the case of an embedded user agent, (e.g. media player), the embedded user agent provides the search for its content. @@ Editors' Note: Is this even necessary? Who does the search in an embedded video player?"@@
• Examples of Success Criterion 2.6.1 (former 4.6.1) :
  • A user wants to locate a text string in a long document. The user agent provides a mechanism for entering the desired text string, such as a text box with a search button.
  • A user wants to search for text in all views of the document, including views of the text source (source view)
  • A user wants to search the element content of form elements (where applicable) and any label text.
  • @@ Editors' Note: searching video captions??@@
  • @@ Editors' Note: Searching embedded SVG?@@
• Related Resources for Success Criterion 2.6.1 (former 4.6.1) :
  • WCAG
  • 2.6.2 (former 4.6.2) ,3,4,5

2.6.2 (former 4.6.2) Find Direction: The user can search forward or backward from the focused location in content. The user is notified of changes in search direction. The user is notified when the search reaches the upper or lower extent of the content based on the search direction. (Level A)

• Intent of Success Criterion 2.6.2 (former 4.6.2) :
  Searching in any direction from the current point of focus allows for maximum flexibility in allowing the user to easily locate the text used in the search. Users for who reading is difficult can greatly reduce the amount of reading required to find the information needed. Searching improves navigation efficiency which is especially important for people with dexterity issues where every keystroke can be time consuming, tiring or painful. It is recommended that the user also has the ability to search forward or backward within any selected content. @@ Editors' Note: needs some explanation. how to keep searching within the selected content
• Examples of Success Criterion 2.6.2 (former 4.6.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.6.2 (former 4.6.2) :
  • To be written

2.6.3 (former 4.6.3) Match Found: When there is a match, the user is alerted and the viewport moves so that the matched text content is at least partially within it. The user can search for the next instance of the text from the location of the match. (Level A)

• Intent of Success Criterion 2.6.3 (former 4.6.3) :
  It is important for the user to easily recognize where a search will start from.
  @@ Editors' Note: If the caret has been moved, from its new location.@@
• Examples of Success Criterion 2.6.3 (former 4.6.3) :
  • Example: 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.6.3 (former 4.6.3) :
  • To be written

2.6.4 (former 4.6.4) Alert on No Match: The user is notified when there is no match or after the last match in content (i.e., prior to starting the search over from the beginning of content). (Level A)

• Intent of Success Criterion 2.6.4 (former 4.6.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.6.4 (former 4.6.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 there is not a match.
• Related Resources for Success Criterion 2.6.4 (former 4.6.4) :
  • To be written

2.6.5 (former 4.6.5) Advanced Find: The user agent provides an accessible advanced search facility, with a case-sensitive and case-insensitive search option, and the ability for the user to perform a search within all content (including hidden content and captioning) for text and text alternatives, for any sequence of characters from the document character set. (Level AA)

• Intent of Success Criterion 2.6.5 (former 4.6.5) : Searching is much more useful when the user can specify whether case matters in a search and when the user can search alternative text.
  
  
• Examples of Success Criterion 2.6.5 (former 4.6.5) :
  • Dennis uses a screen reader. He wants to find all the instances of his friend Bill in a blog post about finances. He needs to specify case in order to avoid stopping at instances of "bill". Later, he searches for his friend's name in a blog post about poetry where the author never uses capital letters. In this instance he specifies that case does not matter.
  • Dennis he remembers a portion of a caption for something he had seen before that he wants to find. He needs to be able to search on the caption.
• Related Resources for Success Criterion 2.6.5 (former 4.6.5) :
  • To be written

2.8.1 (former 4.8.1) Configure Position: When graphical user agent user interfaces have toolbars, the user can add, remove and configure the position of user agent user interface controls on those toolbars from a pre-defined set of controls. (Level AAA)

• Intent of Success Criterion 2.8.1 (former 4.8.1) :
  Not yet drafted
• Examples of Success Criterion 2.8.1 (former 4.8.1) :
  • To be written
• Related Resources for Success Criterion 2.8.1 (former 4.8.1) :
  • WAI-ARIA

2.8.2 (former 4.8.2) Restore Default Toolbars: The user can restore the default toolbar configuration. (Level AAA)

• Intent of Success Criterion 2.8.2 (former 4.8.2) :
  Not yet drafted
• Examples of Success Criterion 2.8.2 (former 4.8.2) :
  • To be written
• Related Resources for Success Criterion 2.8.2 (former 4.8.2) :
  • WAI-ARIA

@@ Editors' Note: Add SC based on this note from IRC of 10 November 2010: We could consider adding to this section a recommendation that messages have a checkbox that lets the user avoid getting the message again. But I'm not sure how we could write it to have an appropriate scope, that is only apply to messages where it's appropriate. AND when you do have those check boxes, it's also useful to have something in the application's settings that allows the user to reset those to their default, thus making all the messages visible again.@@

3.1.2 (former 5.1.1) Option to Ignore: The user can turn off rendering of non-essential or low priority text messages or updating/changing information in the content based on priority properties defined by the author or the user agent. (e.g., ignoring updating content marked "polite"). (Level AA)

• Intent of Success Criterion 3.1.2 (former 5.1.1) :
  Messages designed to inform the user can be a burden to users for whom keypress is time-consuming, tiring, or painful. It's important that these users be able to avoid unnecessary messages.
• Examples of Success Criterion 3.1.2 (former 5.1.1) :
  • 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 display. A user with cognitive disabilities is distracted by the page flicker and wishes to turn off the update. The browser has an menu option to set the level of interruptions, that the user sets to off. @@ Editors' Note: add this example @@
• Related Resources for Success Criterion 3.1.2 (former 5.1.1) :
  • WAI-ARIA

3.2.1 (former 5.2.1) Form Submission: The user can specify whether or not recognized form submissions must be confirmed. The user can redefine keyboard shortcuts for submitting and canceling recognized forms. (Level AA)

• Intent of Success Criterion 3.2.1 (former 5.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 (former 5.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.
• Related Resources for Success Criterion 3.2.1 (former 5.2.1) :
  • @@ Editors' Note: link to section 2.1, especially 2.1.2 and 2.1.10 @@

3.3.1 (former 5.3.1) Accessible documentation: The product documentation is available in a format that conforms to WCAG 2.0 Level "A" or greater. (Level A)

• Intent of Success Criterion 3.3.1 (former 5.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 (former 5.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 (former 5.3.1) :
  • To be written

3.3.2 (former 5.3.2) Document Accessibility Features: All user agent features that benefit accessibility are documented. (Level A) @@ Editors' Note: write a definition of "benefit accessibility" - as contributing to conforming to these guidelines or a feature specifically added to improve accessibility @@

• Intent of Success Criterion 3.3.2 (former 5.3.2) :
  User agent documentation that includes listings and descriptions of features supporting or benefiting accessibility permits users to have access to a description of accessibility and compatibility features. This benefits all users with disabilities who may require assistance in identifying which accessibility features may be present or how to configure those features to work with assistive technology.
  
  The user 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, 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.
• Examples of Success Criterion 3.3.2 (former 5.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.
• Related Resources for Success Criterion 3.3.2 (former 5.3.2) :
  • To be written

3.3.3 (former 5.3.3) Changes Between Versions: Changes to features that benefit accessibility since the previous user agent release are documented. @@Editors' Note: Link to the definition to benefit accessibility from previous 3.3.2 @@ Changes to features that affect accessibility since the previous version of the user agent are documented. (Level AA)

• Intent of Success Criterion 3.3.3 (former 5.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 (former 5.3.3) :
  • Sample text: "In this version, we added the ability to display tooltips on elements with a title attribute when using the keyboard. With caret browsing turned on simply arrowing onto an element with a title the tooltip will remain visible while the caret is within the element."
• Related Resources for Success Criterion 3.3.3 (former 5.3.3) :
  • N/A

3.3.4 (former 5.3.4) Centralized View: There is a centralized view of all features of the user agent that benefit accessibility, in a dedicated section of the documentation. (Level AAA) @@ Editors' Note: Link to new definition of "benefit accessibility" @@

• Intent of Success Criterion 3.3.4 (former 5.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 (eg. 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.
• Examples of Success Criterion 3.3.4 (former 5.3.4) :
  • A specific section in the documentation (local or online) detailing accessibility features of the user agent.[@@ Editor's Note: what about accessibility features of plugins, extensions, etc. they are not user agents by them selves. how do user find out about accessibility features if any in the extension?@@]
• Related Resources for Success Criterion 3.3.4 (former 5.3.4) :
  • N/A

3.3.5 (former 5.3.5) Context Sensitive Help: There is context-sensitive help on all user agent features that benefit accessibility. (Level AAA)

• Intent of Success Criterion 3.3.5 (former 5.3.5) :
  The purpose of this criteria is to help maximize the discovery of user agent features that benefit accessibility.
• Examples of Success Criterion 3.3.5 (former 5.3.5) :
  • 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.
• Related Resources for Success Criterion 3.3.5 (former 5.3.5) :
  • N/A

Implementing 3.4 (former 5.4) The user agent must behave in a predictable fashion. [Implementing 3.4] [Return to Guideline]

3.4.1 (former 5.4.1) Control default focus: The user agent provides a mechanism for setting global configuration of default focus.

• Intent of Success Criterion 3.4.1 (former 5.4.1) :
  Users need to know that navigation in a web page is going to start in a predictable location. While we recognize that it may be desirable for accessibility to set focus to specific link on a page other than the first link, the user needs to be in control of this feature.
• Examples of Success Criterion 3.4.1 (former 5.4.1) :
  • Example: the page has a default focus to search box, the user has to take additional scrolling to get to the content that was not in the search box. The user may want to set their page so it starts at the first link, not the search box.
• Related Resources for Success Criterion 3.4.1 (former 5.4.1) :
  • NA

3.4.2 (former 5.4.2) Unpredictable focus: The user is informed when the user agent changes focus. The user agent provides a global option to block uninitiated focus changes.

• Intent of Success Criterion 3.4.2 (former 5.4.2) :
  Not yet drafted
• Examples of Success Criterion 3.4.2 (former 5.4.2) :
  • A speech user issues a command to execute at a specific location, and the focus changes without the user's control, so the command fails or executes with unpredictable results.
  • Moving the focus in an form, where the field advances without the user hitting tab, and the user hits tab (telephone number fields) so that the focus moves to the next field. It can give an error message that the skipped field is left blank.
• Related Resources for Success Criterion 3.4.2 (former 5.4.2) :
  • UAAG 2.0 1.8.7 (former 3.10.8) Don't Move Focus

@@ Editors' Note: Missing: Greater ease in interpreting security messaging. Should be cross-referenced with the security working group. @@

5.1.1 (former 1.1.1) Non-Web-Based Accessible (Level A): Non-Web-based user agent user interfaces comply with and cite the "Level A" requirements of standards or operating environment conventions that benefit accessibility. The "Level A" requirements are those that are functionally equivalent to WCAG Level A success criteria. (Level A)

• Intent of Success Criterion 5.1.1 (former 1.1.1):
  The user should be able to easily discover detailed information about the user agent's adherence to accessibility standards of the operating environment or adherence to external accessibility requirements without installing and testing the accessibility features.
• Examples of Success Criterion 5.1.1 (former 1.1.1) :
  • User agent X lists the platform accessibility tools (high contrast, show sounds, sticky keys, etc) supported. Additionally, the user agent lists all of the platform accessibility APIs or other APIs that are supported. "Google Chrome supports the Windows Accessibility API (MSAA) to display accessibility information and events for its features and web content. http://www.google.com/support/chrome/bin/answer.py?hl=en&answer==96831"
• Related Resources for Success Criterion 5.1.1 (former 1.1.1):
  • 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

1.1.2 Non-Web-Based Accessible (Level AA): Non-Web-based user agent user interfaces comply with and cite the "Level AA" requirements of standards or operating environment conventions that benefit accessibility. The "Level AA" requirements are those that are functionally equivalent to WCAG Level AA success criteria. (Level AA)

1.1.3 Non-Web-Based Accessible (Level AAA): Non-Web-based user agent user interfaces comply with and cite the "Level AAA" requirements of standards or operating environment conventions that benefit accessibility. The "Level AAA" requirements are those that are functionally equivalent to WCAG Level AAA success criteria. (Level AAA)

5.2.1 (former 1.2.1) Web-Based Accessible (Level A): User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "A". (Level A)

• Intent of Success Criterion 5.2.1 (former 1.2.1):
  Not yet drafted
• Examples of Success Criterion 5.2.1 (former 1.2.1) :
  • To be written
• Related Resources for Success Criterion 5.2.1 (former 1.2.1):
  • To be written

5.2.2 (former 1.2.2) Web-Based Accessible (Level AA): User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "AA". (Level AA)

• Intent of Success Criterion 5.2.2 (former 1.2.2):
  Not yet drafted
• Examples of Success Criterion 5.2.2 (former 1.2.2) :
  • To be written
• Related Resources for Success Criterion 5.2.2 (former 1.2.2):
  • To be written

5.2.3 (former 1.2.3) Web-Based Accessible (Level AAA): User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "AAA". (Level AAA)

• Intent of Success Criterion 5.2.3 (former 1.2.3):
  Not yet drafted
• Examples of Success Criterion 5.2.3 (former 1.2.3) :
  • To be written
• Related Resources for Success Criterion 5.2.3 (former 1.2.3):
  • To be written

5.3.1 (former 1.3.1) Accessibility Features: Implement and cite in the conformance claim the accessibility features of content and platform technology specifications. Accessibility features are those that are either (Level A):

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

• Intent of Success Criterion 5.3.1 (former 1.3.1):
  
• @@ Editors' Note: add a sentence about the importance of content standards @@
  If browsers and players don't seamlessly conform to platform accessibility features, then users can't easily take advantage of those features. Software that has versions for different platforms, may have to handle accessibility differently on different platforms or operating systems. In order to show that you have implemented the accessibility features of the platform correctly, these features are identified in the conformance claim.
  
  The user 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, 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.
  
  
• Examples of Success Criterion 5.3.1 (former 1.3.1) :
  • If you are developing for the Gnome platform, consult the Gnome Accessibility Developers Guide. For example, the Keyboard Focus [link: http://library.gnome.org/devel/accessibility-devel-guide/nightly/id2594568.html.en] 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.
    
    In the conformance claim [link to conformance section], 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.3.1 (former 1.3.1):

  5.3.2 Document Accessibility Features:

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

  "Accessibility for Applications Designers," 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

  WCAG

  HTML

  CSS

  WAI-ARIA

5.4.1 (former 1.4.1) Follow Specifications: Render content according to the technology specification, except where it would actually harm overall accessibility. (Level A)

• Intent of Success Criterion 5.4.1 (former 1.4.1):
  End users and assistive technology products assume that content will be rendered in a predictable fashion. This success criterion ensures that user agents provide this level of predictability. It may be necessary to ignore aspects of the technology specification where they would actually harm, rather than improve, overall accessibility. In these cases user agent developers are encouraged to deviate from those aspects of the standard, and document the decision in their conformance claim. For example, the CSS spec says generated content should not appear in the DOM, which may mean that generated content would not be exposed to assistive technology and thus may not be accessible to blind users. User agents should instead expose the generated content through the DOM, and document their decision to ignore that aspect of the specification.
• Examples of Success Criterion 5.4.1 (former 1.4.1) :
  • A user agent implements the WAI-ARIA (Accessible Rich Internet Applications) standard, and the developer follows the "Implementing ARIA" document by mapping ARIA roles and events to the supported platform accessibility infrastructure (MSAA, UIA, ____, etc.). This allows a screen reader that supports the platform infrastructure to correctly support ARIA in the user agent.
  • An organization creates an optional style sheet that enlarges fonts and adapts all colors for maximum contrast. They can be confident that when their Web site uses this style sheet it will work with any browser because those browsers have implemented CSS according to the CSS specification.
• Related Resources for Success Criterion 5.4.1 (former 1.4.1):
  • Guideline 5.3

5.4.2 (former 1.4.2) Handle Unrendered Technologies: If the user agent does not render a technology, it allows the user to 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.4.2 (former 1.4.2):
  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.4.2 (former 1.4.2) :
  • 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.4.2 (former 1.4.2)
  • To be written

5.4.3 (former 1.4.3) Alternative content handlers: The user has the ability to select content elements and have them rendered in alternative viewers. (Level AA)

• Intent of Success Criterion 5.4.3 (former 1.4.3):
  When accessing media content on the Web, users with disabilities sometimes find they have a richer or more accessible experience in a third-party application than using the browser's built-in facilities. In these cases they want to be able to navigate to content in their browser, then save that content to their disk or launch it in a third-party application.
• Examples of Success Criterion 5.4.3 (former 1.4.3) :
  • 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.
    
    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.
• Related Resources for Success Criterion 5.4.3 (former 1.4.3)
  • To be written