Based on "ED-UAAG20-20130222-SC-raw.txt" dated Thu Mar 7 17:55:38 2013.
| ID | Line Number | Canonical ID | Type | Title | Text | Priority | Whole Line |
|---|---|---|---|---|---|---|---|
| 1 | 1 | 01 | h1 | Ensure that the user interface and rendered content are perceivable | Ensure that the user interface and rendered content are perceivable | PRINCIPLE 1 - Ensure that the user interface and rendered content are perceivable | |
| 1.1 | 2 | 01.01 | h2 | Provide access to alternative content | Provide access to alternative content. | Guideline 1.1 - Provide access to alternative content. | |
| 1.1-N1 | 3 | 01.01-N01 | note | Provide access to alternative content | Summary: The user can choose to render any type of alternative content available. (1.1.1). The user can also choose at least one alternative such as alt text to be always displayed (1.1.2), but it's recommended that users also be able to specify a cascade (1.1.4), such as alt text if it's there, otherwise longdesc, otherwise filename, etc. It's recommended that the user can configure the caption text and that text or sign language alternative cannot obscure the video or the controls (1.1.3). The user can configure the size and position of media alternatives (1.1.5). | Summary: The user can choose to render any type of alternative content available. (1.1.1). The user can also choose at least one alternative such as alt text to be always displayed (1.1.2), but it's recommended that users also be able to specify a cascade (1.1.4), such as alt text if it's there, otherwise longdesc, otherwise filename, etc. It's recommended that the user can configure the caption text and that text or sign language alternative cannot obscure the video or the controls (1.1.3). The user can configure the size and position of media alternatives (1.1.5). | |
| 1.1.1 | 4 | 01.01.01 | h3 | Render Alternative Content | For any content element, the user can choose to render any types of recognized alternative content that are present. | A | 1.1.1 Render Alternative Content: For any content element, the user can choose to render any types of recognized alternative content that are present. (Level A) |
| 1.1.1-N1 | 5 | 01.01.01-N01 | note | Render Alternative Content | It is recommended that the user agent allow the user to choose whether the alternative content replaces or supplements the original content element. | Note: It is recommended that the user agent allow the user to choose whether the alternative content replaces or supplements the original content element. | |
| 1.1.x | 6 | 01.01.x | h3 | Replace Non-Text Content | The user can have all recognized non-text content replaced by alternative content or placeholders. | A | 1.1.x Replace Non-Text Content: The user can have all recognized non-text content replaced by alternative content or placeholders. (Level A) |
| 1.1.x-N1 | 7 | 01.01.x-N01 | note | Replace Non-Text Content | At Level A, the user agent can choose which type of alternative content or placeholder is used to replace the non-text content. However, at Level AA success criterion 1.1.2 will require that the user be allowed to specify one format or placeholder that will be used, and at Level AAA success criterion 1.1.4 will require the user be allowed to specify a cascade order of formats to be rendered. | Note: At Level A, the user agent can choose which type of alternative content or placeholder is used to replace the non-text content. However, at Level AA success criterion 1.1.2 will require that the user be allowed to specify one format or placeholder that will be used, and at Level AAA success criterion 1.1.4 will require the user be allowed to specify a cascade order of formats to be rendered. | |
| 1.1.2 | 8 | 01.01.02 | h3 | Configurable Alternative Content Defaults | For each type of non-text content, the user can specify a type of alternative content that, if present, will be rendered by default. | AA | 1.1.2 Configurable Alternative Content Defaults: For each type of non-text content, the user can specify a type of alternative content that, if present, will be rendered by default. (Level AA) |
| 1.1.3 | 9 | 01.01.03 | h3 | Display of Time-Based Media Alternatives | For recognized on-screen alternatives for time-based media (e.g. captions, sign language video), the following are all true: a. Do not obscure primary media: The user can specify that displaying media alternatives doesn't obscure the primary time-based media; and b. Do not obscure controls: The user can specify that the displaying media alternatives doesn't obscure recognized controls for the primary time-based media; and c. Configurable text: The user can configure recognized text within media alternatives (e.g. captions) in conformance with 1.4.1. | AA | 1.1.3 Display of Time-Based Media Alternatives: For recognized on-screen alternatives for time-based media (e.g. captions, sign language video), the following are all true: (Level AA) a. Do not obscure primary media: The user can specify that displaying media alternatives doesn't obscure the primary time-based media; and b. Do not obscure controls: The user can specify that the displaying media alternatives doesn't obscure recognized controls for the primary time-based media; and c. Configurable text: The user can configure recognized text within media alternatives (e.g. captions) in conformance with 1.4.1. |
| 1.1.3-N1 | 10 | 01.01.03-N01 | note | Display of Time-Based Media Alternatives | Depending on the screen area available, the display of the primary time-based media may need to be reduced in size to meet this requirement. | Note: Depending on the screen area available, the display of the primary time-based media may need to be reduced in size to meet this requirement. | |
| 1.1.4 | 11 | 01.01.04 | h3 | Default Rendering of Alternative Content (Enhanced) | For each type of non-text content, the user can specify the cascade order in which to render different types of alternative content when preferred types are not present. | AAA | 1.1.4 Default Rendering of Alternative Content (Enhanced): For each type of non-text content, the user can specify the cascade order in which to render different types of alternative content when preferred types are not present. (Level AAA) |
| 1.1.5 | 12 | 01.01.05 | h3 | Size and Position of Time-Based Media Alternatives | The user can configure recognized on-screen alternatives for time-based media (e.g. captions, sign language video) as follows: a. The user can resize the media alternatives up to the size of the user agent's viewport. b. The user can reposition the media alternatives to at least above, below, to the right, to the left, and overlapping the primary time-based media. | AAA | 1.1.5 Size and Position of Time-Based Media Alternatives: The user can configure recognized on-screen alternatives for time-based media (e.g. captions, sign language video) as follows: (Level AAA) a. The user can resize the media alternatives up to the size of the user agent's viewport. b. The user can reposition the media alternatives to at least above, below, to the right, to the left, and overlapping the primary time-based media. |
| 1.1.5-N 1 | 13 | 01.01.05-N01 | note | Size and Position of Time-Based Media Alternatives | Depending on the screen area available, the display of the primary time-based media may need to be reduced in size or hidden to meet this requirement. | Note 1: Depending on the screen area available, the display of the primary time-based media may need to be reduced in size or hidden to meet this requirement. | |
| 1.1.5-N 2 | 14 | 01.01.05-N02 | note | Size and Position of Time-Based Media Alternatives | Implementation may involve displaying media alternatives in a separate window, but this is not required. | Note 2: Implementation may involve displaying media alternatives in a separate window, but this is not required. | |
| 1.2 | 15 | 01.02 | h2 | Repair missing content | Repair missing content. | Guideline 1.2 - Repair missing content. | |
| 1.2-N1 | 16 | 01.02-N01 | note | Repair missing content | Summary: The user can request useful alternative content when the author fails to provide it. For example, showing metadata in place of missing or empty (1.2.1) alt text. The user can ask the browser to predict missing structural information, such as field labels, table headings or section headings (1.2.2). | Summary: The user can request useful alternative content when the author fails to provide it. For example, showing metadata in place of missing or empty (1.2.1) alt text. The user can ask the browser to predict missing structural information, such as field labels, table headings or section headings (1.2.2). | |
| 1.2.1 | 17 | 01.02.01 | h3 | Support Repair by Assistive Technologies | If text alternatives for non-text content are missing or empty then both of the following are true: a. the user agent does not attempt to repair the text alternatives with text values that are also available to assistive technologies. b. the user agent makes metadata related to the non-text content available programmatically (and not via fields reserved for text alternatives). | AA | 1.2.1 Support Repair by Assistive Technologies: If text alternatives for non-text content are missing or empty then both of the following are true: (Level AA) a. the user agent does not attempt to repair the text alternatives with text values that are also available to assistive technologies. b. the user agent makes metadata related to the non-text content available programmatically (and not via fields reserved for text alternatives). |
| 1.2.2 | 18 | 01.02.02 | h3 | Repair Missing Structure | The user can specify whether or not the user agent should attempt to insert the following types of structural markup on the basis of author-specified presentation attributes (e.g.. position and appearance): a. Labels b. Headers (e.g. heading markup, table headers) | AAA | 1.2.2 Repair Missing Structure: The user can specify whether or not the user agent should attempt to insert the following types of structural markup on the basis of author-specified presentation attributes (e.g.. position and appearance): (Level AAA) a. Labels b. Headers (e.g. heading markup, table headers) |
| 1.3 | 19 | 01.03 | h2 | Provide highlighting for selection, keyboard focus, enabled elements, visited links | Provide highlighting for selection, keyboard focus, enabled elements, visited links. | Guideline 1.3 - Provide highlighting for selection, keyboard focus, enabled elements, visited links. | |
| 1.3-N1 | 20 | 01.03-N01 | note | Provide highlighting for selection, keyboard focus, enabled elements, visited links | Summary: The user can visually distinguish selected, focused, and enabled items, and recently visited links (1.3.1), with a choice of highighting options that at least include foreground and background colors, and border color and thickness (1.3.2). | Summary: The user can visually distinguish selected, focused, and enabled items, and recently visited links (1.3.1), with a choice of highighting options that at least include foreground and background colors, and border color and thickness (1.3.2). | |
| 1.3.1 | 21 | 01.03.01 | h3 | Highlighted Items | The user can specify that the following classes be highlighted so that each is uniquely distinguished: a. selection b. active keyboard focus (indicated by focus cursors and/or text cursors) c. recognized enabled input elements (distinguished from disabled elements) d. elements with alternative content e. recently visited links | A | 1.3.1 Highlighted Items: The user can specify that the following classes be highlighted so that each is uniquely distinguished: (Level A) a. selection b. active keyboard focus (indicated by focus cursors and/or text cursors) c. recognized enabled input elements (distinguished from disabled elements) d. elements with alternative content e. recently visited links |
| 1.3.2 | 22 | 01.03.02 | h3 | Highlighting Options | When highlighting classes specified by 1.3.1 Highlighted Items, the user can specify highlighting options that include at least: a. foreground colors, b. background colors, and c. borders (configurable color, style, and thickness) | AA | 1.3.2 Highlighting Options: When highlighting classes specified by 1.3.1 Highlighted Items, the user can specify highlighting options that include at least: (Level AA) a. foreground colors, b. background colors, and c. borders (configurable color, style, and thickness) |
| 1.4 | 23 | 01.04 | h2 | Provide text configuration | Provide text configuration. | Guideline 1.4 - Provide text configuration. | |
| 1.4-N1 | 24 | 01.04-N01 | note | Provide text configuration | Summary: The user can control text font, color, and size (1.4.1), including whether all text should be the shown the same size (1.4.2). | Summary: The user can control text font, color, and size (1.4.1), including whether all text should be the shown the same size (1.4.2). | |
| 1.4.1 | 25 | 01.04.01 | h3 | Configure Rendered Text | The user can globally set any or all of the following characteristics of visually rendered text content, overriding any specified by the author or user agent defaults: a. text scale (the general size of text) b. font family c. text color (foreground and background) d. line spacing e. character spacing | A | 1.4.1 Configure Rendered Text: The user can globally set any or all of the following characteristics of visually rendered text content, overriding any specified by the author or user agent defaults: (Level A) a. text scale (the general size of text) b. font family c. text color (foreground and background) d. line spacing e. character spacing |
| 1.4.2 | 26 | 01.04.02 | h3 | 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). | A | 1.4.2 Preserving Size Distinctions: The user can specify whether or not distinctions in the size of rendered text are preserved when that text is rescaled (e.g. headers continue to be larger than body text). (Level A) |
| 1.5 | 27 | 01.05 | h2 | Provide volume configuration | Provide volume configuration. | Guideline 1.5 - Provide volume configuration. | |
| 1.5-N1 | 28 | 01.05-N01 | note | Provide volume configuration | Summary: The user can adjust the volume of each audio track relative to the global volume level (1.5.1). | Summary: The user can adjust the volume of each audio track relative to the global volume level (1.5.1). | |
| 1.5.1 | 29 | 01.05.01 | h3 | Global Volume | The user can independently adjust the volume of all audio tracks, relative to the global volume level set through operating environment mechanisms. | A | 1.5.1 Global Volume: The user can independently adjust the volume of all audio tracks, relative to the global volume level set through operating environment mechanisms. (Level A) |
| 1.6 | 30 | 01.06 | h2 | Provide synthesized speech configuration | Provide synthesized speech configuration. | Guideline 1.6 - Provide synthesized speech configuration. | |
| 1.6-N1 | 31 | 01.06-N01 | note | Provide synthesized speech configuration | Summary: If synthesized speech is produced, the user can specify speech rate and volume (1.6.1), pitch and pitch range (1.6.2), and synthesizer speech characteristics like emphasis (1.6.3) and features like spelling (1.6.4). | Summary: If synthesized speech is produced, the user can specify speech rate and volume (1.6.1), pitch and pitch range (1.6.2), and synthesizer speech characteristics like emphasis (1.6.3) and features like spelling (1.6.4). | |
| 1.6.1 | 32 | 01.06.01 | h3 | Speech Rate, Volume, and Voice | If synthesized speech is produced, the user can specify the following: a. speech rate, b. speech volume (independently of other sources of audio), and c. voice, when more than one voice option is available | A | 1.6.1 Speech Rate, Volume, and Voice: If synthesized speech is produced, the user can specify the following: (Level A) a. speech rate, b. speech volume (independently of other sources of audio), and c. voice, when more than one voice option is available |
| 1.6.2 | 33 | 01.06.02 | h3 | Speech Pitch and Range | If synthesized speech is produced, the user can specify the following if offered by the speech synthesizer: a. pitch (average frequency of the speaking voice), and b. pitch range (variation in average frequency) | AA | 1.6.2 Speech Pitch and Range: If synthesized speech is produced, the user can specify the following if offered by the speech synthesizer: (Level AA) a. pitch (average frequency of the speaking voice), and b. pitch range (variation in average frequency) |
| 1.6.2-N1 | 34 | 01.06.02-N01 | note | Speech Pitch and Range | Because the technical implementations of text to speech engines vary (e.g., formant-based synthesis or concatenative synthesis), a specific engine may not support varying pitch or pitch range. A user agent will expose the availability of pitch and pitch range control if the currently selected or installed text to speech engine offers this capability. | Note: Because the technical implementations of text to speech engines vary (e.g., formant-based synthesis or concatenative synthesis), a specific engine may not support varying pitch or pitch range. A user agent will expose the availability of pitch and pitch range control if the currently selected or installed text to speech engine offers this capability. | |
| 1.6.3 | 35 | 01.06.03 | h3 | Advanced Speech Characteristics | The user can adjust all of the speech characteristics offered by the speech synthesizer. | AAA | 1.6.3 Advanced Speech Characteristics: The user can adjust all of the speech characteristics offered by the speech synthesizer. (Level AAA) |
| 1.6.4 | 36 | 01.06.04 | h3 | Synthesized Speech Features | If synthesized speech is produced, the following features are provided: 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: spoken as individual digits and punctuation (e.g. "one two zero three point five" for 1203.5 or "one comma two zero three point five" for 1,203.5), and spoken as full numbers are spoken (e.g. "one thousand, two hundred and three point five" for 1203.5), d. at least two ways of speaking punctuation: spoken literally, and with punctuation understood from natural pauses. | AA | 1.6.4 Synthesized Speech Features: If synthesized speech is produced, 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: spoken as individual digits and punctuation (e.g. "one two zero three point five" for 1203.5 or "one comma two zero three point five" for 1,203.5), and spoken as full numbers are spoken (e.g. "one thousand, two hundred and three point five" for 1203.5), d. at least two ways of speaking punctuation: spoken literally, and with punctuation understood from natural pauses. |
| 1.7 | 37 | 01.07 | h2 | Enable Configuration of User Stylesheets | Enable Configuration of User Stylesheets. | Guideline 1.7 - Enable Configuration of User Stylesheets. | |
| 1.7-N1 | 38 | 01.07-N01 | note | Enable Configuration of User Stylesheets | Summary: The user agent shall support user stylesheets (1.7.1) and the user can choose which if any user-supplied (1.7.2) and author-supplied (1.7.3) stylesheets to use. The user agent will allow users to save user stylesheets (1.7.4). | Summary: The user agent shall support user stylesheets (1.7.1) and the user can choose which if any user-supplied (1.7.2) and author-supplied (1.7.3) stylesheets to use. The user agent will allow users to save user stylesheets (1.7.4). | |
| 1.7.1 | 39 | 01.07.01 | h3 | Support User Stylesheets | If the user agent supports a mechanism for authors to supply stylesheets, the user agent also provides a mechanism for users to supply stylesheets. | A | 1.7.1 Support User Stylesheets: If the user agent supports a mechanism for authors to supply stylesheets, the user agent also provides a mechanism for users to supply stylesheets. (Level A) |
| 1.7.2 | 40 | 01.07.02 | h3 | Apply User Stylesheets | If user style sheets are supported, then the user can enable or disable user stylesheets for: a. all pages on specified websites, or b. all pages | A | 1.7.2 Apply User Stylesheets: If user style sheets are supported, then the user can enable or disable user stylesheets for: (Level A) a. all pages on specified websites, or b. all pages |
| 1.7.3 | 41 | 01.07.03 | h3 | Author Style Sheets | If the user agent supports a mechanism for authors to supply stylesheets, the user can disable the use of author style sheets on the current page. | A | 1.7.3 Author Style Sheets: If the user agent supports a mechanism for authors to supply stylesheets, the user can disable the use of author style sheets on the current page. (Level A) |
| 1.7.4 | 42 | 01.07.04 | h3 | Save Copies of Stylesheets | The user can save copies of the stylesheets referenced by the current page, in order to edit and load the copies as user stylesheets. | AA | 1.7.4 Save Copies of Stylesheets: The user can save copies of the stylesheets referenced by the current page, in order to edit and load the copies as user stylesheets. (Level AA) |
| 1.8 | 43 | 01.08 | h2 | Help users to use and orient within windows and viewports | Help users to use and orient within windows and viewports. | Guideline 1.8 - Help users to use and orient within windows and viewports. | |
| 1.8-N1 | 44 | 01.08-N01 | note | Help users to use and orient within windows and viewports | Summary: The user agent provides programmatic and visual cues to keep the user oriented. These include highlighting the viewport (1.8.1), keeping the focus within the viewport (1.8.2 & 1.8.7), resizing the viewport (1.8.3), providing scrollbar(s) that identify when content is outside the visible region (1.8.4) and which portion is visible (1.8.5), changing the size of graphical content with zoom (1.8.6 & 1.8.12), restoring the focus and point of regard when the user returns to a previously viewed page (1.8.8). Users can set a preference whether new windows or tabs open automatically (1.8.9) or get focus automatically (1.8.10). Additionally, the user can specify that all view ports have the same user interface elements (1.8.11), if and how new viewports open (1.8.9), and whether the new window automatically gets focus (1.8.10). The user can mark items in a webpage and use shortcuts to navigate back to marked items. (1.8.13). | Summary: The user agent provides programmatic and visual cues to keep the user oriented. These include highlighting the viewport (1.8.1), keeping the focus within the viewport (1.8.2 & 1.8.7), resizing the viewport (1.8.3), providing scrollbar(s) that identify when content is outside the visible region (1.8.4) and which portion is visible (1.8.5), changing the size of graphical content with zoom (1.8.6 & 1.8.12), restoring the focus and point of regard when the user returns to a previously viewed page (1.8.8). Users can set a preference whether new windows or tabs open automatically (1.8.9) or get focus automatically (1.8.10). Additionally, the user can specify that all view ports have the same user interface elements (1.8.11), if and how new viewports open (1.8.9), and whether the new window automatically gets focus (1.8.10). The user can mark items in a webpage and use shortcuts to navigate back to marked items. (1.8.13). | |
| 1.8.1 | 45 | 01.08.01 | h3 | Highlight Viewport | The viewport with the input focus is highlighted and the user can customize attributes of the highlighting mechanism (e.g. shape, size, stroke width, color, blink rate). The viewport can include nested viewports and containers. | A | 1.8.1 Highlight Viewport: The viewport with the input focus is highlighted and the user can customize attributes of the highlighting mechanism (e.g. shape, size, stroke width, color, blink rate). The viewport can include nested viewports and containers. (Level A) |
| 1.8.2 | 46 | 01.08.02 | h3 | Move Viewport to Selection and Focus | When a viewport's selection or input focus changes, the viewport's content moves as necessary to ensure that the new selection or input focus location is at least partially in the visible portion of the viewport. | A | 1.8.2 Move Viewport to Selection and Focus: When a viewport's selection or input focus changes, the viewport's content moves as necessary to ensure that the new selection or input focus location is at least partially in the visible portion of the viewport. (Level A) |
| 1.8.3 | 47 | 01.08.03 | h3 | Resize Viewport | The user can resize graphical viewports within the limits of the display, overriding any values specified by the author. | A | 1.8.3 Resize Viewport: The user can resize graphical viewports within the limits of the display, overriding any values specified by the author. (Level A) |
| 1.8.4 | 48 | 01.08.04 | h3 | Viewport Scrollbars | When the rendered content extends beyond the viewport dimensions, users can have graphical viewports include scrollbars, overriding any values specified by the author. | A | 1.8.4 Viewport Scrollbars: When the rendered content extends beyond the viewport dimensions, users can have graphical viewports include scrollbars, overriding any values specified by the author. (Level A) |
| 1.8.5 | 49 | 01.08.05 | h3 | Indicate Viewport Position | The user can determine the viewport's position relative to the full extent of the rendered content. | A | 1.8.5 Indicate Viewport Position: The user can determine the viewport's position relative to the full extent of the rendered content. (Level A) |
| 1.8.6 | 50 | 01.08.06 | h3 | Zoom | The user can rescale content within graphical viewports as follows: a. Zoom in: to at least 500% of the default size; and b. Zoom out: to at least 10% of the default size, so the content fits within the height or width of the viewport. | A | 1.8.6: Zoom: The user can rescale content within graphical viewports as follows: (Level A) a. Zoom in: to at least 500% of the default size; and b. Zoom out: to at least 10% of the default size, so the content fits within the height or width of the viewport. |
| 1.8.7 | 51 | 01.08.07 | h3 | Maintain point of regard | To the extent possible, the point of regard remains visible and at the same location within the viewport when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed. | A | 1.8.7 Maintain point of regard: To the extent possible, the point of regard remains visible and at the same location within the viewport when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed. (Level A) |
| 1.8.8 | 52 | 01.08.08 | h3 | 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 that is allowed by the content, including a restored point of regard, input focus and selection. | AA | 1.8.8 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 that is allowed by the content, including a restored point of regard, input focus and selection. (Level AA) |
| 1.8.9 | 53 | 01.08.09 | h3 | Open on Request | The user can specify whether author content can open new top-level viewports (e.g. windows or tabs). | AA | 1.8.9 Open on Request: The user can specify whether author content can open new top-level viewports (e.g. windows or tabs). (Level AA) |
| 1.8.10 | 54 | 01.08.10 | h3 | 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. | AA | 1.8.10 Do Not Take Focus: If new top-level viewports (e.g. windows or tabs) are configured to open without explicit user request, the user can specify whether or not top-level viewports take the active keyboard focus when they open. (Level AA) |
| 1.8.11 | 55 | 01.08.11 | h3 | Same UI | The user can specify that all top-level viewports (e.g. windows or tabs) follow the defined user interface configuration. | AA | 1.8.11 Same UI: The user can specify that all top-level viewports (e.g. windows or tabs) follow the defined user interface configuration. (Level AA) |
| 1.8.12 | 56 | 01.08.12 | h3 | Reflowing Zoom | The user can request that when reflowable content in a graphical viewport is rescaled, it is reflowed so that one dimension of the content fits within the height or width of the viewport. | AA | 1.8.12: Reflowing Zoom: The user can request that when reflowable content in a graphical viewport is rescaled, it is reflowed so that one dimension of the content fits within the height or width of the viewport. (Level AA) |
| 1.8.12-N1 | 57 | 01.08.12-N01 | note | Reflowing Zoom | User agents are encouraged to allow users to override author instructions not to wrap content (e.g., nowrap). | Note: User agents are encouraged to allow users to override author instructions not to wrap content (e.g., nowrap). | |
| 1.8.13 | 58 | 01.08.13 | h3 | Webpage Bookmarks | The user can mark items in a webpage, then use shortcuts to navigate back to marked items. The user can specify whether a navigation mark disappears after a session, or is persistent across sessions. | AAA | 1.8.13 Webpage Bookmarks: The user can mark items in a webpage, then use shortcuts to navigate back to marked items. The user can specify whether a navigation mark disappears after a session, or is persistent across sessions. (Level AAA) |
| 1.9 | 59 | 01.09 | h2 | Provide alternative views | Provide alternative views. | Guideline 1.9 - Provide alternative views. | |
| 1.9-N1 | 60 | 01.09-N01 | note | Provide alternative views | Summary: The user can view the source of content (1.9.2), or an outline view of important elements. (1.9.1). | Summary: The user can view the source of content (1.9.2), or an outline view of important elements. (1.9.1). | |
| 1.9.1 | 61 | 01.09.01 | h3 | Outline View | Users can view a navigable outline of rendered content composed of labels for important elements, and can move focus efficiently to these elements in the main viewport. | AA | 1.9.1 Outline View: Users can view a navigable outline of rendered content composed of labels for important elements, and can move focus efficiently to these elements in the main viewport. (Level AA) |
| 1.9.1-N1 | 62 | 01.09.01-N01 | note | Outline View | The important elements depend on the web content technology, but may include headings, table captions, and content sections. | Note: The important elements depend on the web content technology, but may include headings, table captions, and content sections. | |
| 1.9.2 | 63 | 01.09.02 | h3 | Source View | The user can view all source text that is available to the user agent. | AAA | 1.9.2 Source View: The user can view all source text that is available to the user agent. (Level AAA) |
| 1.10 | 64 | 01.10 | h2 | Provide element information | Provide element information. | Guideline 1.10 - Provide element information. | |
| 1.10-N1 | 65 | 01.10-N01 | note | Provide element information | Summary:The user agent presents information about content relationships (e.g. form labels, table headers)(1.10.1), and extended link information (e.g. title, internal vs. external) (1.10.2) | Summary:The user agent presents information about content relationships (e.g. form labels, table headers)(1.10.1), and extended link information (e.g. title, internal vs. external) (1.10.2) | |
| 1.10.1 | 66 | 01.10.01 | h3 | Access Relationships | The user can access explicitly-defined relationships based on the user's position in content (e.g. show the label of a form control, show the headers of a table cell). | AA | 1.10.1 Access Relationships: The user can access explicitly-defined relationships based on the user's position in content (e.g. show the label of a form control, show the headers of a table cell). (Level AA) |
| 1.10.2 | 67 | 01.10.02 | h3 | Access to Element Hierarchy | The user can determine the path of element nodes going from the root element of the element hierarchy to the currently focused or selected element. | AAA | 1.10.2 Access to Element Hierarchy: The user can determine the path of element nodes going from the root element of the element hierarchy to the currently focused or selected element. (Level AAA) |
| 2 | 68 | 02 | h1 | Ensure that the user interface is operable | Ensure that the user interface is operable | PRINCIPLE 2. Ensure that the user interface is operable | |
| 2.1 | 69 | 02.01 | h2 | Ensure full keyboard access | Ensure full keyboard access. | Guideline 2.1 - Ensure full keyboard access. | |
| 2.1-N1 | 70 | 02.01-N01 | note | Ensure full keyboard access | Summary: Users can operate all functions (2.1.1), and move focus (2.1.2) using just the keyboard. Users can activate important or common features with shortcut keys, (2.1.6), override keyboard shortcuts in content and user interface (2.1.4), escape keyboard traps (2.1.3), specify that selecting an item in a dropdown list or menu not activate that item or move to that new web page (2.1.4) and use standard keys for that platform (2.1.5). | Summary: Users can operate all functions (2.1.1), and move focus (2.1.2) using just the keyboard. Users can activate important or common features with shortcut keys, (2.1.6), override keyboard shortcuts in content and user interface (2.1.4), escape keyboard traps (2.1.3), specify that selecting an item in a dropdown list or menu not activate that item or move to that new web page (2.1.4) and use standard keys for that platform (2.1.5). | |
| 2.1.1 | 71 | 02.01.01 | h3 | Keyboard Operation | All functionality can be operated via the keyboard using sequential or direct keyboard commands that do not require specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (e.g. free hand drawing). This does not forbid and should not discourage providing other input methods in addition to keyboard operation including mouse, touch, gesture and speech. | A | 2.1.1 Keyboard Operation: All functionality can be operated via the keyboard using sequential or direct keyboard commands that do not require specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (e.g. free hand drawing). This does not forbid and should not discourage providing other input methods in addition to keyboard operation including mouse, touch, gesture and speech. (Level A) |
| 2.1.2 | 72 | 02.01.02 | h3 | Keyboard Focus | Every viewport has an active or inactive keyboard focus at all times. | A | 2.1.2 Keyboard Focus: Every viewport has an active or inactive keyboard focus at all times. (Level A) |
| 2.1.3 | 73 | 02.01.03 | h3 | No Keyboard Trap | If keyboard focus can be moved to a component using a keyboard interface (including nested user agents), then focus can be moved away from that component using only a keyboard interface. If this requires more than unmodified arrow or tab keys (or other standard exit methods), users are advised of the method for moving focus away. | A | 2.1.3 No Keyboard Trap: If keyboard focus can be moved to a component using a keyboard interface (including nested user agents), then focus can be moved away from that component using only a keyboard interface. If this requires more than unmodified arrow or tab keys (or other standard exit methods), users are advised of the method for moving focus away. (Level A) |
| 2.1.4 | 74 | 02.01.04 | h3 | Separate Selection from Activation | The user can specify that focus and selection can be moved without causing further changes in focus, selection, or the state of controls, by either the user agent or author content. | A | 2.1.4 Separate Selection from Activation: The user can specify that focus and selection can be moved without causing further changes in focus, selection, or the state of controls, by either the user agent or author content. (Level A) |
| 2.1.5 | 75 | 02.01.05 | h3 | Follow Text Keyboard Conventions | The user agent follows keyboard conventions for the operating environment. | A | 2.1.5 Follow Text Keyboard Conventions: The user agent follows keyboard conventions for the operating environment. (Level A) |
| 2.1.6 | 76 | 02.01.06 | h3 | Efficient Keyboard Access | The user agent user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access. | A | 2.1.6 Efficient Keyboard Access: The user agent user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access. (Level A) |
| 2.2 | 77 | 02.02 | h2 | Provide sequential navigation | Provide sequential navigation | Guideline 2.2 - Provide sequential navigation | |
| 2.2-N1 | 78 | 02.02-N01 | note | Provide sequential navigation | Summary: Users can use the keyboard to navigate sequentially (2.2.3) to all the operable elements (2.2.1) in the viewport as well as between viewports (2.2.2). Users can optionally disable wrapping or request a signal when wrapping occurs (2.2.4). | Summary: Users can use the keyboard to navigate sequentially (2.2.3) to all the operable elements (2.2.1) in the viewport as well as between viewports (2.2.2). Users can optionally disable wrapping or request a signal when wrapping occurs (2.2.4). | |
| 2.2.1 | 79 | 02.02.01 | h3 | Sequential Navigation Between Elements | The user can move the keyboard focus backwards and forwards through all recognized enabled elements in the current viewport. | A | 2.2.1 Sequential Navigation Between Elements: The user can move the keyboard focus backwards and forwards through all recognized enabled elements in the current viewport. (Level A) |
| 2.2.2 | 80 | 02.02.02 | h3 | Sequential Navigation Between Viewports | The user can move the keyboard focus backwards and forwards between viewports, without having to sequentially navigate all the elements in a viewport. | A | 2.2.2 Sequential Navigation Between Viewports: The user can move the keyboard focus backwards and forwards between viewports, without having to sequentially navigate all the elements in a viewport. (Level A) |
| 2.2.3 | 81 | 02.02.03 | h3 | Default Navigation Order | If the author has not specified a navigation order, the default sequential navigation order is the document order. | A | 2.2.3 Default Navigation Order: If the author has not specified a navigation order, the default sequential navigation order is the document order. (Level A) |
| 2.2.4 | 82 | 02.02.04 | h3 | Options for Wrapping in Navigation | The user can prevent sequential navigation from wrapping the focus at the beginning or end of a document, and can request notification when such wrapping occurs. | AA | 2.2.4 Options for Wrapping in Navigation: The user can prevent sequential navigation from wrapping the focus at the beginning or end of a document, and can request notification when such wrapping occurs. (Level AA) |
| 2.3 | 83 | 02.03 | h2 | Provide direct navigation and activation | Provide direct navigation and activation | Guideline 2.3 - Provide direct navigation and activation | |
| 2.3-N1 | 84 | 02.03-N01 | note | Provide direct navigation and activation | Summary: Users can navigate directly (e.g. keyboard shortcuts) to important elements (2.3.1) with the option of immediate activation of the operable elements (2.3.3). Display commands with the elements to make it easier for users to discover the commands (2.3.2 & 2.3.4). The user can remap and save direct commands (2.3.5). | Summary: Users can navigate directly (e.g. keyboard shortcuts) to important elements (2.3.1) with the option of immediate activation of the operable elements (2.3.3). Display commands with the elements to make it easier for users to discover the commands (2.3.2 & 2.3.4). The user can remap and save direct commands (2.3.5). | |
| 2.3.1 | 85 | 02.03.01 | h3 | Direct Navigation to Important Elements | The user can navigate directly to any important elements (e.g. structural or operable) in rendered content. | AA | 2.3.1 Direct Navigation to Important Elements: The user can navigate directly to any important elements (e.g. structural or operable) in rendered content. (Level AA) |
| 2.3.2 | 86 | 02.03.02 | h3 | Present Direct Commands from Rendered Content (enhanced) | The user can have any recognized direct commands in rendered content (e.g. accesskey, landmark) be presented with their associated elements (e.g. Alt+R to reply to a web email). | AA | 2.3.2 Present Direct Commands from Rendered Content (enhanced): The user can have any recognized direct commands in rendered content (e.g. accesskey, landmark) be presented with their associated elements (e.g. Alt+R to reply to a web email). (Level AA) |
| 2.3.3 | 87 | 02.03.03 | h3 | Direct activation of Enabled Elements | The user can move directly to and activate any enabled element in rendered content. | A | 2.3.3 Direct activation of Enabled Elements: The user can move directly to and activate any enabled element in rendered content. (Level A) |
| 2.3.4 | 88 | 02.03.04 | h3 | Present Direct Commands in User Interface | The user can have any direct commands in the user agent user interface (e.g. keyboard shortcuts) be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). | AA | 2.3.4 Present Direct Commands in User Interface: The user can have any direct commands in the user agent user interface (e.g. keyboard shortcuts) be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). (Level AA) |
| 2.3.5 | 89 | 02.03.05 | h3 | Customize Keyboard Commands | The user can override any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and user agent user interface controls, except for conventional bindings for the operating environment (e.g. arrow keys for navigating within menus). The rebinding options must include single-key and key-plus-modifier keys if available in the operating environment. The user must be able to save these settings beyond the current session. | AA | 2.3.5 Customize Keyboard Commands: The user can override any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and user agent user interface controls, except for conventional bindings for the operating environment (e.g. arrow keys for navigating within menus). The rebinding options must include single-key and key-plus-modifier keys if available in the operating environment. The user must be able to save these settings beyond the current session. (Level AA) |
| 2.4 | 90 | 02.04 | h2 | Provide text search | Provide text search. | Guideline 2.4 - Provide text search. | |
| 2.4-N1 | 91 | 02.04-N01 | note | Provide text search | Summary: Users can search rendered content (2.4.1) forward or backward (2.4.2) and can have the matched content highlighted in the viewport (2.4.3). The user is notified if there is no match (2.4.4). Users can also search by case and for text within alternative content (2.4.5). | Summary: Users can search rendered content (2.4.1) forward or backward (2.4.2) and can have the matched content highlighted in the viewport (2.4.3). The user is notified if there is no match (2.4.4). Users can also search by case and for text within alternative content (2.4.5). | |
| 2.4.1 | 92 | 02.04.01 | h3 | Text Search | The user can perform a search within rendered content (e.g. not hidden with a style), including rendered text alternatives and rendered generated content, for any sequence of printing characters from the document character set. | A | 2.4.1 Text Search: The user can perform a search within rendered content (e.g. not hidden with a style), including rendered text alternatives and rendered generated content, for any sequence of printing characters from the document character set. (Level A) |
| 2.4.2 | 93 | 02.04.02 | h3 | Find Direction | The user can search forward or backward in rendered content. | A | 2.4.2 Find Direction: The user can search forward or backward in rendered content. (Level A) |
| 2.4.3 | 94 | 02.04.03 | h3 | Match Found | When a search operation produces a match, the matched content is highlighted, the viewport is scrolled if necessary so that the matched content is within its visible area, and the user can search from the location of the match. | A | 2.4.3 Match Found: When a search operation produces a match, the matched content is highlighted, the viewport is scrolled if necessary so that the matched content is within its visible area, and the user can search from the location of the match. (Level A) |
| 2.4.4 | 95 | 02.04.04 | h3 | Alert on Wrap or No Match | The user can be notified when there is no match to a search operation. The user can be notified when the search continues from the beginning or end of content. | A | 2.4.4 Alert on Wrap or No Match: The user can be notified when there is no match to a search operation. The user can be notified when the search continues from the beginning or end of content. (Level A) |
| 2.4.5 | 96 | 02.04.05 | h3 | Search alternative content | The user can perform text searches within textual alternative content (e.g. text alternatives for non-text content, captions) even when the textual alternative content is not rendered onscreen. | AA | 2.4.5 Search alternative content: The user can perform text searches within textual alternative content (e.g. text alternatives for non-text content, captions) even when the textual alternative content is not rendered onscreen. (Level AA) |
| 2.5 | 97 | 02.05 | h2 | Provide structural navigation | Provide structural navigation. | Guideline 2.5 - Provide structural navigation. | |
| 2.5-N1 | 98 | 02.05-N01 | note | Provide structural navigation | Summary: Users can view (2.5.1), navigate (2.5.2), and configure the elements used in navigating (2.5.3) content hierarchy. | Summary: Users can view (2.5.1), navigate (2.5.2), and configure the elements used in navigating (2.5.3) content hierarchy. | |
| 2.5.1 | 99 | 02.05.01 | h3 | Location in Hierarchy | When the user agent is presenting hierarchical information, but the hierarchy is not reflected in a standardized fashion in the DOM or platform accessibility services, the user can view the path of nodes leading from the root of the hierarchy to a specified element. | AA | 2.5.1 Location in Hierarchy: When the user agent is presenting hierarchical information, but the hierarchy is not reflected in a standardized fashion in the DOM or platform accessibility services, the user can view the path of nodes leading from the root of the hierarchy to a specified element. (Level AA) |
| 2.5.2 | 100 | 02.05.02 | h3 | Navigate by structural element | The user agent provides at least the following types of structural navigation, where the structure types exist: a. by heading b. within tables | AA | 2.5.2 Navigate by structural element: The user agent provides at least the following types of structural navigation, where the structure types exist:(Level AA) a. by heading b. within tables |
| 2.5.3 | 101 | 02.05.03 | h3 | Configure Elements for Structural Navigation | The user can configure sets of important elements (including element types) for structured navigation and hierarchical/outline view. | AAA | 2.5.3 Configure Elements for Structural Navigation: The user can configure sets of important elements (including element types) for structured navigation and hierarchical/outline view. (Level AAA) |
| 2.6 | 102 | 02.06 | h2 | Provide access to event handlers | Provide access to event handlers | Guideline 2.6 - Provide access to event handlers | |
| 2.6-N1 | 103 | 02.06-N01 | note | Provide access to event handlers | Summary:Users can interact with web content by mouse, keyboard, voice input, gesture, or a combination of input methods. Users can discover what event handlers (e.g. onmouseover) are available at the element and activate an element's events individually (2.6.1). | Summary:Users can interact with web content by mouse, keyboard, voice input, gesture, or a combination of input methods. Users can discover what event handlers (e.g. onmouseover) are available at the element and activate an element's events individually (2.6.1). | |
| 2.6.1 | 104 | 02.06.01 | h3 | Access to input methods | The user can discover recognized input methods explicitly associated with an element, and activate those methods in a modality independent manner. | AA | 2.6.1 Access to input methods: The user can discover recognized input methods explicitly associated with an element, and activate those methods in a modality independent manner. (Level AA) |
| 2.7 | 105 | 02.07 | h2 | Configure and store preference settings | Configure and store preference settings | Guideline 2.7 - Configure and store preference settings | |
| 2.7-N1 | 106 | 02.07-N01 | note | Configure and store preference settings | Summary: Users can restore preference settings to default (2.7.2), and accessibility settings persist between sessions (2.7.1). Users can manage multiple sets of preference settings (2.7.3), and adjust preference setting outside the user interface so the current user interface does not prevent access (2.7.4). It's also recommended that groups of settings can be transported to compatible systems (2.7.5). | Summary: Users can restore preference settings to default (2.7.2), and accessibility settings persist between sessions (2.7.1). Users can manage multiple sets of preference settings (2.7.3), and adjust preference setting outside the user interface so the current user interface does not prevent access (2.7.4). It's also recommended that groups of settings can be transported to compatible systems (2.7.5). | |
| 2.7.1 | 107 | 02.07.01 | h3 | Persistent Accessibility Settings | User agent accessibility preference settings persist between sessions. | A | 2.7.1 Persistent Accessibility Settings: User agent accessibility preference settings persist between sessions. (Level A) |
| 2.7.2 | 108 | 02.07.02 | h3 | Restore all to default | The user can restore all preference settings to default values. | A | 2.7.2 Restore all to default: The user can restore all preference settings to default values. (Level A) |
| 2.7.3 | 109 | 02.07.03 | h3 | Multiple Sets of Preference Settings | The user can save and retrieve multiple sets of user agent preference settings. | AA | 2.7.3 Multiple Sets of Preference Settings: The user can save and retrieve multiple sets of user agent preference settings. (Level AA) |
| 2.7.4 | 110 | 02.07.04 | h3 | Change preference settings outside the user interface | The user can adjust any preference settings required to meet the User Agent Accessibility Guidelines (UAAG) 2.0 from outside the user agent user interface. | AA | 2.7.4 Change preference settings outside the user interface: The user can adjust any preference settings required to meet the User Agent Accessibility Guidelines (UAAG) 2.0 from outside the user agent user interface. (Level AA) |
| 2.7.5 | 111 | 02.07.05 | h3 | Portable Preference Settings | The user can transfer all compatible user agent preference settings between computers. | AAA | 2.7.5 Portable Preference Settings: The user can transfer all compatible user agent preference settings between computers. (Level AAA) |
| 2.8 | 112 | 02.08 | h2 | Customize display of GUI controls | Customize display of GUI controls | Guideline 2.8 - Customize display of GUI controls | |
| 2.8-N1 | 113 | 02.08-N01 | note | Customize display of GUI controls | Summary: It's recommended that users can add, remove and configure the position of graphical user agent controls and restore them to their default settings (2.8.1). | Summary: It's recommended that users can add, remove and configure the position of graphical user agent controls and restore them to their default settings (2.8.1). | |
| 2.8.1 | 114 | 02.08.01 | h3 | Customize display of controls representing user interface commands, functions, and extensions | The user can customize which user agent commands, functions, and extensions are displayed within the user agent's user interface as follows: a. Show: The user can choose to display any controls, which can include user installed extensions, available within the user agent user interface. It is acceptable to limit the total number of controls that are displayed onscreen. b. Simplify: The user can simplify the default user interface by choosing to display only commands essential for basic operation (e.g. by hiding some control). c. Reposition: The user can choose to reposition individual controls within containers (e.g. Toolbars or tool palettes), as well as reposition the containers themselves to facilitate physical access (e.g. To minimize hand travel on touch screens, or to facilitate preferred hand access on handheld mobile devices). d. Assign Activation Keystrokes or Gestures: The user can choose to view, assign or change default keystrokes or gestures used to activate controls. e. Reset: The user has the option to reset the containers and controls to their original configuration. | AA | 2.8.1 Customize display of controls representing user interface commands, functions, and extensions: The user can customize which user agent commands, functions, and extensions are displayed within the user agent's user interface as follows:(Level AA) a. Show: The user can choose to display any controls, which can include user installed extensions, available within the user agent user interface. It is acceptable to limit the total number of controls that are displayed onscreen. b. Simplify: The user can simplify the default user interface by choosing to display only commands essential for basic operation (e.g. by hiding some control). c. Reposition: The user can choose to reposition individual controls within containers (e.g. Toolbars or tool palettes), as well as reposition the containers themselves to facilitate physical access (e.g. To minimize hand travel on touch screens, or to facilitate preferred hand access on handheld mobile devices). d. Assign Activation Keystrokes or Gestures: The user can choose to view, assign or change default keystrokes or gestures used to activate controls. e. Reset: The user has the option to reset the containers and controls to their original configuration. |
| 2.8.2 | 115 | 02.08.02 | h3 | Reset Toolbar Configuration | Guideline 2.9 Allow time-independent interaction. | AA | 2.8.2 Reset Toolbar Configuration: Guideline 2.9 - Allow time-independent interaction. |
| 2.8.2-N1 | 116 | 02.08.02-N01 | note | Reset Toolbar Configuration | Summary: Users can extend the time limit for user input when such limits are controllable by the user agent (2.9.1); by default, the user agent shows the progress of content in the process of downloading (2.9.2). | Summary: Users can extend the time limit for user input when such limits are controllable by the user agent (2.9.1); by default, the user agent shows the progress of content in the process of downloading (2.9.2). | |
| 2.9.1 | 117 | 02.09.01 | h3 | Adjustable Timing | Where time limits for user input are recognized and controllable by the user agent, the user can extend the time limits. | A | 2.9.1 Adjustable Timing: Where time limits for user input are recognized and controllable by the user agent, the user can extend the time limits. (Level A) |
| 2.9.2 | 118 | 02.09.02 | h3 | Retrieval Progress | By default, the user agent shows the progress of content retrieval. | A | 2.9.2 Retrieval Progress: By default, the user agent shows the progress of content retrieval. (Level A) |
| 2.10 | 119 | 02.10 | h2 | Help users avoid flashing that could cause seizures | Help users avoid flashing that could cause seizures. | Guideline 2.10 - Help users avoid flashing that could cause seizures. | |
| 2.10-N1 | 120 | 02.10-N01 | note | Help users avoid flashing that could cause seizures | Summary: To help users avoid seizures, the default configuration prevents the browser user interface and rendered content from flashing more than three times a second above a luminescence or color threshold (2.10.1), or does not flash at all (2.10.2). | Summary: To help users avoid seizures, the default configuration prevents the browser user interface and rendered content from flashing more than three times a second above a luminescence or color threshold (2.10.1), or does not flash at all (2.10.2). | |
| 2.10.1 | 121 | 02.10.01 | h3 | 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. | A | 2.10.1 Three Flashes or Below Threshold: In its default configuration, the user agent does not display any user interface components or recognized content that flashes more than three times in any one-second period, unless the flash is below the general flash and red flash thresholds. (Level A) |
| 2.10.2 | 122 | 02.10.02 | h3 | 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). | AAA | 2.10.2 Three Flashes: In its default configuration, the user agent does not display any user interface components or recognized content that flashes more than three times in any one-second period (regardless of whether not the flash is below the general flash and red flash thresholds). (Level AAA) |
| 2.11 | 123 | 02.11 | h2 | Provide control of content that may reduce accessibility | Provide control of content that may reduce accessibility. | Guideline 2.11 - Provide control of content that may reduce accessibility. | |
| 2.11-N1 | 124 | 02.11-N01 | note | Provide control of content that may reduce accessibility | Summary: The user can control background images (2.11.1); present placeholders for time-based media (2.11.2) and executable regions (2.11.3), or block all executable content (2.11.4); adjust playback (2.11.5), stop/pause/resume (2.11.6), navigate, (2.11.7) and specify tracks for prerecorded time-based media (2.11.9); and adjust contrast and brightness of visual time-based media (2.11.10). | Summary: The user can control background images (2.11.1); present placeholders for time-based media (2.11.2) and executable regions (2.11.3), or block all executable content (2.11.4); adjust playback (2.11.5), stop/pause/resume (2.11.6), navigate, (2.11.7) and specify tracks for prerecorded time-based media (2.11.9); and adjust contrast and brightness of visual time-based media (2.11.10). | |
| 2.11-N2 | 125 | 02.11-N02 | note | Provide control of content that may reduce accessibility | Guideline 2.11 and its success criteria only apply to images, animations, video, audio, etc. that the user agent can recognize. | Applicability Notes: Guideline 2.11 and its success criteria only apply to images, animations, video, audio, etc. that the user agent can recognize. | |
| 2.11.2 | 126 | 02.11.02 | h3 | Time-Based Media Load-Only | The user can override the play on load of recognized time-based media content such that the content is not played until explicit user request. | A | 2.11.2 Time-Based Media Load-Only: The user can override the play on load of recognized time-based media content such that the content is not played until explicit user request. (Level A) |
| 2.11.3 | 127 | 02.11.03 | h3 | Execution Placeholder | The user can render a placeholder instead of executable content that would normally be contained within an on-screen area (e.g. Applet, Flash), until explicit user request to execute. | A | 2.11.3 Execution Placeholder: The user can render a placeholder instead of executable content that would normally be contained within an on-screen area (e.g. Applet, Flash), until explicit user request to execute. (Level A) |
| 2.11.4 | 128 | 02.11.04 | h3 | Execution Toggle | The user can turn on/off the execution of executable content that would not normally be contained within a particular area (e.g. Javascript). | A | 2.11.4 Execution Toggle: The user can turn on/off the execution of executable content that would not normally be contained within a particular area (e.g. Javascript). (Level A) |
| 2.11.5 | 129 | 02.11.05 | h3 | Playback Rate Adjustment for Prerecorded Content | The user can adjust the playback rate of prerecorded time-based media content, such that all of the following are true: a. The user can adjust the playback rate of the time-based media tracks to between 50% and 250% of real time. b. Speech whose playback rate has been adjusted by the user maintains pitch in order to limit degradation of the speech quality. c. Audio and video tracks remain synchronized across this required range of playback rates. d. The user agent provides a function that resets the playback rate to normal (100%). | A | 2.11.5 Playback Rate Adjustment for Prerecorded Content: The user can adjust the playback rate of prerecorded time-based media content, such that all of the following are true: (Level A) a. The user can adjust the playback rate of the time-based media tracks to between 50% and 250% of real time. b. Speech whose playback rate has been adjusted by the user maintains pitch in order to limit degradation of the speech quality. c. Audio and video tracks remain synchronized across this required range of playback rates. d. The user agent provides a function that resets the playback rate to normal (100%). |
| 2.11.6 | 130 | 02.11.06 | h3 | Stop/Pause/Resume Time-Based Media | The user can stop, pause, and resume rendered audio and animation content (including video, animated images, and changing text) that last three or more seconds at their default playback rate. | A | 2.11.6 Stop/Pause/Resume Time-Based Media: The user can stop, pause, and resume rendered audio and animation content (including video, animated images, and changing text) that last three or more seconds at their default playback rate. (Level A) |
| 2.11.7 | 131 | 02.11.07 | h3 | Navigate Time-Based Media | The user can navigate along the timebase using a continuous scale, and by relative time units within rendered audio and animations (including video and animated images) that last three or more seconds at their default playback rate. | A | 2.11.7 Navigate Time-Based Media: The user can navigate along the timebase using a continuous scale, and by relative time units within rendered audio and animations (including video and animated images) that last three or more seconds at their default playback rate. (Level A) |
| 2.11.8 | 132 | 02.11.08 | h3 | Semantic Navigation of Time-Based Media | The user can navigate by semantic structure within the time-based media, such as by chapters or scenes present in the media . | AA | 2.11.8 Semantic Navigation of Time-Based Media: The user can navigate by semantic structure within the time-based media, such as by chapters or scenes present in the media (Level AA). |
| 2.11.9 | 133 | 02.11.09 | h3 | Track Enable/Disable of Time-Based Media | During time-based media playback, the user can determine which tracks are available and select or deselect tracks, overriding global default settings for captions, audio descriptions, etc. | AA | 2.11.9 Track Enable/Disable of Time-Based Media: During time-based media playback, the user can determine which tracks are available and select or deselect tracks, overriding global default settings for captions, audio descriptions, etc. (Level AA) |
| 2.11.10 | 134 | 02.11.10 | h3 | Video Contrast and Brightness | Users can adjust the contrast and brightness of visual time-based media. | AAA | 2.11.10 Video Contrast and Brightness: Users can adjust the contrast and brightness of visual time-based media. (Level AAA) |
| 2.11.11 | 135 | 02.11.11 | h3 | Scale and position visual alternative media tracks | Guideline 2.12 Other Input Devices | AAA | 2.11.11 Scale and position visual alternative media tracks: Guideline 2.12 - Other Input Devices |
| 2.11.11-N1 | 136 | 02.11.11-N01 | note | Scale and position visual alternative media tracks | Summary: For all input devices supported by the platform, the user agents should let the user perform all functions aside from entering text (2.12.2), and enter text with any platform-provided features (2.12.1). If possible, it is also encouraged to let the user enter text even if the platform does not provide such a feature (2.12.3). | Summary: For all input devices supported by the platform, the user agents should let the user perform all functions aside from entering text (2.12.2), and enter text with any platform-provided features (2.12.1). If possible, it is also encouraged to let the user enter text even if the platform does not provide such a feature (2.12.3). | |
| 2.12.1 | 137 | 02.12.01 | h3 | Support Platform Text Input Devices | If the platform supports text input using an input device, the user agent is compatible with this functionality. | A | 2.12.1 Support Platform Text Input Devices: If the platform supports text input using an input device, the user agent is compatible with this functionality. (Level A) |
| 2.12.2 | 138 | 02.12.02 | h3 | Operation With Any Device | If an input device is supported by the platform , all user agent functionality other than text input can be operated using that device. | AA | 2.12.2 Operation With Any Device: If an input device is supported by the platform , all user agent functionality other than text input can be operated using that device. (Level AA) |
| 2.12.3 | 139 | 02.12.03 | h3 | Text Input With Any Device | If an input device is supported by the platform , all user agent functionality including text input can be operated using that device. | AAA | 2.12.3 Text Input With Any Device: If an input device is supported by the platform , all user agent functionality including text input can be operated using that device. (Level AAA) |
| 3 | 140 | 03 | h1 | Ensure that the user interface is understandable | Ensure that the user interface is understandable | PRINCIPLE 3: Ensure that the user interface is understandable | |
| 3.1 | 141 | 03.01 | h2 | Help users avoid unnecessary messages | Help users avoid unnecessary messages. | Guideline 3.1 - Help users avoid unnecessary messages. | |
| 3.1-N1 | 142 | 03.01-N01 | note | Help users avoid unnecessary messages | Summary: Users can turn off non-essential messages from the author or user-agent. | Summary: Users can turn off non-essential messages from the author or user-agent. | |
| 3.1.2 | 143 | 03.01.02 | h3 | Reduce Interruptions | The user can avoid or defer recognized non-essential or low priority messages and updating/changing information in the user agent user interface and rendered content. | AA | 3.1.2 Reduce Interruptions: The user can avoid or defer recognized non-essential or low priority messages and updating/changing information in the user agent user interface and rendered content.(Level AA) |
| 3.2 | 144 | 03.02 | h2 | Help users avoid and correct mistakes | Help users avoid and correct mistakes. | Guideline 3.2 - Help users avoid and correct mistakes. | |
| 3.2-N1 | 145 | 03.02-N01 | note | Help users avoid and correct mistakes | Summary: Users can have form submissions require confirmation (3.2.1), go back after navigating (3.2.2), and have their text checked for spelling errors (3.2.3). | Summary: Users can have form submissions require confirmation (3.2.1), go back after navigating (3.2.2), and have their text checked for spelling errors (3.2.3). | |
| 3.2.1 | 146 | 03.02.01 | h3 | Form Submission | The user can specify whether or not recognized form submissions must be confirmed. | AA | 3.2.1 Form Submission: The user can specify whether or not recognized form submissions must be confirmed. (Level AA) |
| 3.2.2 | 147 | 03.02.02 | h3 | Back Button | The user can reverse recognized navigation between web addresses (e.g. standard "back button" functionality). | AA | 3.2.2 Back Button: The user can reverse recognized navigation between web addresses (e.g. standard "back button" functionality). (Level AA) |
| 3.2.3 | 148 | 03.02.03 | h3 | Provide spell checking functionality | User agents provide spell checking functionality for text created inside the user agent. | AA | 3.2.3 Provide spell checking functionality: User agents provide spell checking functionality for text created inside the user agent. (Level AA) |
| 3.2.4 | 149 | 03.02.04 | h3 | Text Entry Undo | The user can reverse recognized text entry actions prior to submission. | A | 3.2.4 Text Entry Undo: The user can reverse recognized text entry actions prior to submission. (Level A) |
| 3.2.4-N1 | 150 | 03.02.04-N01 | note | Text Entry Undo | Submission can be triggered in many different ways, such as clicking a submit button, typing a key in a control with an onkeypress event, or by a script responding to a timer. | Note: Submission can be triggered in many different ways, such as clicking a submit button, typing a key in a control with an onkeypress event, or by a script responding to a timer. | |
| 3.2.5 | 151 | 03.02.05 | h3 | Settings Change Confirmation | If the user agent provides mechanisms for changing its user interface settings, it either allows the user to reverse the setting changes, or the user can require user confirmation to proceed. | A | 3.2.5 Settings Change Confirmation: If the user agent provides mechanisms for changing its user interface settings, it either allows the user to reverse the setting changes, or the user can require user confirmation to proceed. (Level A) |
| 3.3 | 152 | 03.03 | h2 | Document the user agent user interface including accessibility features | Document the user agent user interface including accessibility features. | Guideline 3.3 - Document the user agent user interface including accessibility features. | |
| 3.3-N1 | 153 | 03.03-N01 | note | Document the user agent user interface including accessibility features | Summary: User documentation is available in an accessible format (3.3.1), it includes accessibility features (3.3.2), delineates differences between versions (3.3.3), provides a centralized views of conformance UAAG2.0 (3.3.4), and is available as context sensitive help in the UA (3.3.5). | Summary: User documentation is available in an accessible format (3.3.1), it includes accessibility features (3.3.2), delineates differences between versions (3.3.3), provides a centralized views of conformance UAAG2.0 (3.3.4), and is available as context sensitive help in the UA (3.3.5). | |
| 3.3.1 | 154 | 03.03.01 | h3 | Accessible documentation | The product documentation is available in a format that meets success criteria of WCAG 2.0 Level "A" or greater. | A | 3.3.1 Accessible documentation: The product documentation is available in a format that meets success criteria of WCAG 2.0 Level "A" or greater. (Level A) |
| 3.3.2 | 155 | 03.03.02 | h3 | Document Accessibility Features | All features of the user agent that meet User Agent Accessibility Guidelines 2.0 success criteria are documented. | A | 3.3.2 Document Accessibility Features: All features of the user agent that meet User Agent Accessibility Guidelines 2.0 success criteria are documented. (Level A) |
| 3.3.3 | 156 | 03.03.03 | h3 | Changes Between Versions | Changes to features that meet UAAG 2.0 success criteria since the previous user agent release are documented. | AA | 3.3.3 Changes Between Versions: Changes to features that meet UAAG 2.0 success criteria since the previous user agent release are documented. (Level AA) |
| 3.3.4 | 157 | 03.03.04 | h3 | Centralized View | There is a dedicated section of the documentation that presents a view of all features of the user agent necessary to meet the requirements of User Agent Accessibility Guidelines 2.0. | AAA | 3.3.4 Centralized View: There is a dedicated section of the documentation that presents a view of all features of the user agent necessary to meet the requirements of User Agent Accessibility Guidelines 2.0. (Level AAA) |
| 3.4 | 158 | 03.04 | h2 | The user agent must behave in a predictable fashion | The user agent must behave in a predictable fashion. | Guideline 3.4 - The user agent must behave in a predictable fashion. | |
| 3.4-N1 | 159 | 03.04-N01 | note | The user agent must behave in a predictable fashion | Summary: Users can prevent non-requested focus changes (3.4.1). | Summary: Users can prevent non-requested focus changes (3.4.1). | |
| 3.4.1 | 160 | 03.04.01 | h3 | Avoid unpredictable focus | The user can prevent focus changes that are not a result of explicit user request. | A | 3.4.1 Avoid unpredictable focus: The user can prevent focus changes that are not a result of explicit user request. (Level A) |
| 4 | 161 | 04 | h1 | Facilitate programmatic access | Facilitate programmatic access | PRINCIPLE 4: Facilitate programmatic access | |
| 4.1 | 162 | 04.01 | h2 | Facilitate programmatic access to assistive technology | Facilitate programmatic access to assistive technology | Guideline 4.1 - Facilitate programmatic access to assistive technology | |
| 4.1-N1 | 163 | 04.01-N01 | note | Facilitate programmatic access to assistive technology | Summary: Be compatible with assistive technologies by supporting platform standards (4.1.1), including providing information about all menus, buttons, dialogs, etc. (4.1.2, 4.1.6), access to DOMs (4.1.4), and access to structural relationships and meanings, such as what text or image labels a control or serves as a heading (4.1.5). Where something can't be made accessible, provide an accessible alternative version, such as a standard window in place of a customized window (4.1.3). Make sure that that programmatic exchanges are quick and responsive (4.1.7). | Summary: Be compatible with assistive technologies by supporting platform standards (4.1.1), including providing information about all menus, buttons, dialogs, etc. (4.1.2, 4.1.6), access to DOMs (4.1.4), and access to structural relationships and meanings, such as what text or image labels a control or serves as a heading (4.1.5). Where something can't be made accessible, provide an accessible alternative version, such as a standard window in place of a customized window (4.1.3). Make sure that that programmatic exchanges are quick and responsive (4.1.7). | |
| 4.1.1 | 164 | 04.01.01 | h3 | Platform Accessibility Services | The user agent supports relevant platform accessibility services. | A | 4.1.1 Platform Accessibility Services: The user agent supports relevant platform accessibility services. (Level A) |
| 4.1.2 | 165 | 04.01.02 | h3 | Name, Role, State, Value, Description | For all user interface components including user interface, rendered content, generated content, and alternative content, the user agent makes available the name, role, state, value, and description via a platform accessibility services. | A | 4.1.2 Name, Role, State, Value, Description: For all user interface components including user interface, rendered content, generated content, and alternative content, the user agent makes available the name, role, state, value, and description via a platform accessibility services. (Level A) |
| 4.1.3 | 166 | 04.01.03 | h3 | Accessible Alternative | If a component of the user agent user interface cannot be exposed through the platform accessibility services, then the user agent provides an equivalent alternative that is exposed through the platform accessibility service. | A | 4.1.3 Accessible Alternative: If a component of the user agent user interface cannot be exposed through the platform accessibility services, then the user agent provides an equivalent alternative that is exposed through the platform accessibility service. (Level A) |
| 4.1.4 | 167 | 04.01.04 | h3 | Programmatic Availability of DOMs | If the user agent implements one or more DOMs, they must be made programmatically available to assistive technologies. | A | 4.1.4 Programmatic Availability of DOMs: If the user agent implements one or more DOMs, they must be made programmatically available to assistive technologies. (Level A) |
| 4.1.5 | 168 | 04.01.05 | h3 | Write Access | If the user can modify the state or value of a piece of content through the user interface (e.g., by checking a box or editing a text area), the same degree of write access is available programmatically. | A | 4.1.5 Write Access: If the user can modify the state or value of a piece of content through the user interface (e.g., by checking a box or editing a text area), the same degree of write access is available programmatically. (Level A) |
| 4.1.6 | 169 | 04.01.06 | h3 | Expose Accessible Properties | If any of the following properties are supported by the platform accessibility services, make the properties available to the accessibility platform architecture: a. the bounding dimensions and coordinates of onscreen elements b. font family of text c. font size of text d. foreground color of text e. background color of text. f. change state/value notifications g. selection h. highlighting i. input device focus j. direct keyboard commands k. underline of menu items (keyboard command/shortcuts) | A | 4.1.6 Expose Accessible Properties: If any of the following properties are supported by the platform accessibility services, make the properties available to the accessibility platform architecture: (Level A) a. the bounding dimensions and coordinates of onscreen elements b. font family of text c. font size of text d. foreground color of text e. background color of text. f. change state/value notifications g. selection h. highlighting i. input device focus j. direct keyboard commands k. underline of menu items (keyboard command/shortcuts) |
| 4.1.7 | 170 | 04.01.07 | h3 | Timely Communication | For APIs implemented to satisfy the requirements of UAAG 2.0, ensure that programmatic exchanges proceed at a rate such that users do not perceive a delay. | A | 4.1.7 Timely Communication: For APIs implemented to satisfy the requirements of UAAG 2.0, ensure that programmatic exchanges proceed at a rate such that users do not perceive a delay. (Level A) |
| 5 | 171 | 05 | h1 | Comply with applicable specifications and conventions | Comply with applicable specifications and conventions | PRINCIPLE 5: Comply with applicable specifications and conventions | |
| 5.1 | 172 | 05.01 | h2 | Comply with applicable specifications and conventions | Comply with applicable specifications and conventions. | Guideline 5.1 - Comply with applicable specifications and conventions. | |
| 5.1-N1 | 173 | 05.01-N01 | note | Comply with applicable specifications and conventions | Summary: When the browser's menus, buttons, dialogs, etc. are authored in HTML or similar standards, they need to meet W3C's Web Content Accessibility Guidelines. | Summary: When the browser's menus, buttons, dialogs, etc. are authored in HTML or similar standards, they need to meet W3C's Web Content Accessibility Guidelines. | |
| 5.1.1 | 174 | 05.01.01 | h3 | WCAG Compliant | Web-based authoring tool user interfaces meet the WCAG 2.0 success criteria: Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria. | AAA | 5.1.1 WCAG Compliant: Web-based authoring tool user interfaces meet the WCAG 2.0 success criteria: Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria. (Level AAA) |
| 5.1.1-N1 | 175 | 05.01.01-N01 | note | WCAG Compliant | This success criterion does not apply to non-Web-based user agent user interfaces, but does include any parts of non-Web-based user agents that are Web-based (e.g. help systems). | Note: This success criterion does not apply to non-Web-based user agent user interfaces, but does include any parts of non-Web-based user agents that are Web-based (e.g. help systems). | |
| 5.1.2 | 176 | 05.01.02 | h3 | Implement accessibility features of content specs | Implement and cite in the conformance claim the accessibility features of content specifications. Accessibility features are those that are either a. identified as such in the specification or b. allow authors to satisfy a requirement of WCAG. | A | 5.1.2 Implement accessibility features of content specs: Implement and cite in the conformance claim the accessibility features of content specifications. Accessibility features are those that are either (Level A): a. identified as such in the specification or b. allow authors to satisfy a requirement of WCAG. |
| 5.1.3 | 177 | 05.01.03 | h3 | Implement Accessibility Features of platform | If the user agent contains non-web-based user interfaces, then those user interfaces follow user interface accessibility guidelines for the platform. | A | 5.1.3 Implement Accessibility Features of platform: If the user agent contains non-web-based user interfaces, then those user interfaces follow user interface accessibility guidelines for the platform. (Level A) |
| 5.1.4 | 178 | 05.01.04 | h3 | Handle Unrendered Technologies | If the user agent does not render a technology, the user can choose a way to handle content in that technology (e.g. by launching another application or by saving it to disk). | A | 5.1.4 Handle Unrendered Technologies: If the user agent does not render a technology, the user can choose a way to handle content in that technology (e.g. by launching another application or by saving it to disk). (Level A) |
| 5.1.5 | 179 | 05.01.05 | h3 | Alternative content handlers | The user can select content elements and have them rendered in alternative viewers. | AA | 5.1.5 Alternative content handlers: The user can select content elements and have them rendered in alternative viewers. (Level AA) |
| 5.1.6 | 180 | 05.01.06 | h3 | Enable Reporting of User Agent Accessibility Faults | The user agent provides a mechanism for users to report user agent accessibility issues. | AAA | 5.1.6 Enable Reporting of User Agent Accessibility Faults: The user agent provides a mechanism for users to report user agent accessibility issues.(Level AAA) |
| 5.1.6-N1 | 181 | 05.01.06-N01 | note | Enable Reporting of User Agent Accessibility Faults | When a rendering requirement of another specification contradicts a requirement of UAAG 2.0, the user agent may disregard the rendering requirement of the other specification and still satisfy this guideline. | Applicability Note: When a rendering requirement of another specification contradicts a requirement of UAAG 2.0, the user agent may disregard the rendering requirement of the other specification and still satisfy this guideline. |