Based on "ED-UAAG20-20120117.txt" dated Thu Jan 19 12:41:14 2012.
| 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 easily determine which pieces of content have alternatives such as alt text or longdesc (1.1.1) and interact with the text to see the available alternatives (1.1.3). 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. | Summary: The user can easily determine which pieces of content have alternatives such as alt text or longdesc (1.1.1) and interact with the text to see the available alternatives (1.1.3). 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. | |
| 1.1.1 | 4 | 01.01.01 | h3 | Configurable Default Rendering | The user can specify which types of alternative content to render by default. | A | 1.1.1 Configurable Default Rendering: The user can specify which types of alternative content to render by default. (Level A) |
| 1.1.2 | 5 | 01.01.02 | h3 | Browse and Render | When a rendered element has alternative content, the user can render alternatives according to the following: * 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. | A | 1.1.2 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. |
| 1.1.3 | 6 | 01.01.03 | h3 | Identify Presence of Unrendered Alternative Content | The user can specify that content be rendered with an adjacent indicator when unrendered alternative content is present (e.g. an icon to indicate an image has a short text alternative). | A | 1.1.3 Identify Presence of Unrendered Alternative Content: The user can specify that content be rendered with an adjacent indicator when unrendered alternative content is present (e.g. an icon to indicate an image has a short text alternative). (Level A) |
| 1.1.4 | 7 | 01.01.04 | h3 | Rendering Alternative Cascade Order | The user can specify the cascade order in which to render alternative content. | AA | 1.1.4 Rendering Alternative Cascade Order: The user can specify the cascade order in which to render alternative content. (Level AA) |
| 1.2 | 8 | 01.02 | h2 | Repair missing content | Repair missing content. | Guideline 1.2 - Repair missing content. | |
| 1.2-N1 | 9 | 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 a filename in place of missing (1.2.1) or empty (1.2.2) alt text. The user can ask the browser to predict alternative content if it is missing (1.2.3) or notify the user if the content cannot be rendered (1.2.4). | Summary: The user can request useful alternative content when the author fails to provide it. For example, showing a filename in place of missing (1.2.1) or empty (1.2.2) alt text. The user can ask the browser to predict alternative content if it is missing (1.2.3) or notify the user if the content cannot be rendered (1.2.4). | |
| 1.2.1 | 10 | 01.02.01 | h3 | 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 the author has not provided alternative content. | A | 1.2.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 the author has not provided alternative content. (Level A) |
| 1.2.2 | 11 | 01.02.02 | h3 | 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. | AAA | 1.2.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 AAA) |
| 1.2.3 | 12 | 01.02.03 | h3 | Repair Missing Associations | The user can specify whether or not the user agent should attempt to predict associations from author-specified presentation attributes (i.e. position and appearance). | AAA | 1.2.3 Repair Missing Associations: The user can specify whether or not the user agent should attempt to predict associations from author-specified presentation attributes (i.e. position and appearance). (Level AAA) |
| 1.2.4 | 13 | 01.02.04 | h3 | Broken Alternative Content | The user can be notified when the user agent cannot render alternative content (e.g. when captions are broken). | AAA | 1.2.4 Broken Alternative Content: The user can be notified when the user agent cannot render alternative content (e.g. when captions are broken). (Level AAA) |
| 1.3 | 14 | 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 | 15 | 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 | 16 | 01.03.01 | h3 | Highlighted Items | The user can globally specify that the following be highlighted so that each class is uniquely distinguished. It is not the intention that all recognized enabled elements be uniquely distinguished, just that they be distinguished from disabled elements. (a) selection (b) active keyboard focus (indicated by focus cursors and/or text cursors) (c) recognized enabled elements (d) presence of alternative content (e) recently visited links | A | 1.3.1 Highlighted Items: The user can globally specify that the following be highlighted so that each class is uniquely distinguished. It is not the intention that all recognized enabled elements be uniquely distinguished, just that they be distinguished from disabled elements. (Level A) (a) selection (b) active keyboard focus (indicated by focus cursors and/or text cursors) (c) recognized enabled elements (d) presence of alternative content (e) recently visited links |
| 1.3.2 | 17 | 01.03.02 | h3 | Highlighting Options | When highlighting classes specified by 1.3.1 Highlighted Items and 1.3.3 Highlighted Input Controls, The user can specify highlighting options that include at least: [@@Editor's Note: Review for editorial rewording to compensate for a reference to an SC the reader hasn't read yet.@@ ] (a) foreground colors, (b) background colors, and (c) border (configurable color, style, and thickness) | A | 1.3.2 Highlighting Options: When highlighting classes specified by 1.3.1 Highlighted Items and 1.3.3 Highlighted Input Controls, The user can specify highlighting options that include at least: (Level A) [@@Editor's Note: Review for editorial rewording to compensate for a reference to an SC the reader hasn't read yet.@@ ] (a) foreground colors, (b) background colors, and (c) border (configurable color, style, and thickness) |
| 1.3.3 | 18 | 01.03.03 | h3 | Highlighted Input Controls | The user can have the following highlighted when they are recognized: (a) enabled controls that take input (e.g. push buttons, radio buttons, check boxes, and text input fields, but not groupings or static text and images) regardless of whether they are read-write or read-only, and (b) elements with scripted input handlers (e.g. images or text ranges that have onClick or onKeyPress events) regardless of whether the current state allows them to operate. | AA | 1.3.3 Highlighted Input Controls: The user can have the following highlighted when they are recognized: (Level AA) (a) enabled controls that take input (e.g. push buttons, radio buttons, check boxes, and text input fields, but not groupings or static text and images) regardless of whether they are read-write or read-only, and (b) elements with scripted input handlers (e.g. images or text ranges that have onClick or onKeyPress events) regardless of whether the current state allows them to operate. |
| 1.4 | 19 | 01.04 | h2 | Provide text configuration | Provide text configuration. | Guideline 1.4 - Provide text configuration. | |
| 1.4-N1 | 20 | 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 | 21 | 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 (i.e. the general size of text) , (b) font family, (c) text color (i.e. foreground and background), (d) line spacing, and (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 (i.e. the general size of text) , (b) font family, (c) text color (i.e. foreground and background), (d) line spacing, and (e) character spacing. |
| 1.4.2 | 22 | 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 | 23 | 01.05 | h2 | Provide volume configuration | Provide volume configuration. | Guideline 1.5 - Provide volume configuration. | |
| 1.5-N1 | 24 | 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 | 25 | 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. If the global setting is mute, the user agent may override a global mute on explicit user request that cautions the user about the implication. | 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. If the global setting is mute, the user agent may override a global mute on explicit user request that cautions the user about the implication. (Level A) |
| 1.6 | 26 | 01.06 | h2 | Provide synthesized speech configuration | Provide synthesized speech configuration. | Guideline 1.6 - Provide synthesized speech configuration. | |
| 1.6-N1 | 27 | 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 | 28 | 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 | 29 | 01.06.02 | h3 | Speech Pitch and Range | If synthesized speech is produced, the user can specify the following: (a) pitch (i.e. the average frequency of the speaking voice), and (b) pitch range (i.e. specifies a variation in average frequency), | AA | 1.6.2 Speech Pitch and Range: If synthesized speech is produced, the user can specify the following: (Level AA) : (a) pitch (i.e. the average frequency of the speaking voice), and (b) pitch range (i.e. specifies a variation in average frequency), |
| 1.6.3 | 30 | 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 | 31 | 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: 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. | 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: 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. |
| 1.7 | 32 | 01.07 | h2 | Enable Configuration of Style Profiles | Enable Configuration of Style Profiles. | Guideline 1.7 - Enable Configuration of Style Profiles. | |
| 1.7-N1 | 33 | 01.07-N01 | note | Enable Configuration of Style Profiles | Summary: The user agent shall support user style profiles (1.7.1) and the user can choose which if any user-supplied (1.7.2) and author-supplied (1.7.3) style profiles to use. | Summary: The user agent shall support user style profiles (1.7.1) and the user can choose which if any user-supplied (1.7.2) and author-supplied (1.7.3) style profiles to use. | |
| 1.7.1 | 34 | 01.07.01 | h3 | Support User Style Profiles | User agents that support a mechanism for authors to supply style profiles shall also provide an equally effective mechanism for users to supply profiles. | A | 1.7.1 Support User Style Profiles: User agents that support a mechanism for authors to supply style profiles shall also provide an equally effective mechanism for users to supply profiles. (Level A) |
| 1.7.2 | 35 | 01.07.02 | h3 | Apply User Style Profiles | The user can turn on the use of user style profiles and for every user style profile defined, the user can choose whether or not it should be applied to: (a) the current page, or (b) all pages on specified web sites, or (c) all pages. | A | 1.7.2 Apply User Style Profiles: The user can turn on the use of user style profiles and for every user style profile defined, the user can choose whether or not it should be applied to: (Level A) (a) the current page, or (b) all pages on specified web sites, or (c) all pages. |
| 1.7.3 | 36 | 01.07.03 | h3 | Author Style Sheets | The user can turn off the use of author style profiles, and for every author style sheet defined the user can choose whether or not it should be applied to: (a) the current page, or (b) all pages for which it is defined. | A | 1.7.3 Author Style Sheets: The user can turn off the use of author style profiles, and for every author style sheet defined the user can choose whether or not it should be applied to: (Level A) (a) the current page, or (b) all pages for which it is defined. |
| 1.7.4 | 37 | 01.07.04 | h3 | Save copies of style profiles | The user can save copies of the style profiles referenced by the current page, so that they can edit and load them as user style profiles. | AA | 1.7.4 Save copies of style profiles: The user can save copies of the style profiles referenced by the current page, so that they can edit and load them as user style profiles. (Level AA) |
| 1.8 | 38 | 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 | 39 | 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), 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.11), and restoring the focus and point of regard when the user returns to a previously viewed page (1.8.5). Additionally, the user can specify that all view ports have the same user interface elements (1.8.10), if and how new viewports open (1.8.6), and whether the new window automatically gets focus (1.8.7). The user can also close any open window or tab (1.8.9). | 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), 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.11), and restoring the focus and point of regard when the user returns to a previously viewed page (1.8.5). Additionally, the user can specify that all view ports have the same user interface elements (1.8.10), if and how new viewports open (1.8.6), and whether the new window automatically gets focus (1.8.7). The user can also close any open window or tab (1.8.9). | |
| 1.8.1 | 40 | 01.08.01 | h3 | Highlight Viewport | The viewport with the input focus (including nested viewports and their containers) is highlighted, and the user can customize attributes of the highlighted mechanism, including, but not limited to, shape, size, stroke width, color, and blink rate (if any). | A | 1.8.1 Highlight Viewport: The viewport with the input focus (including nested viewports and their containers) is highlighted, and the user can customize attributes of the highlighted mechanism, including, but not limited to, shape, size, stroke width, color, and blink rate (if any). (Level A) |
| 1.8.2 | 41 | 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 | 42 | 01.08.03 | h3 | Resize Viewport | The user can make viewports resizable, within the limits of the display, overriding any values specified by the author. | A | 1.8.3 Resize Viewport: The user can make viewports resizable, within the limits of the display, overriding any values specified by the author. (Level A) |
| 1.8.4 | 43 | 01.08.04 | h3 | Viewport 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. | A | 1.8.4 Viewport 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) |
| 1.8.11 | 44 | 01.08.11 | h3 | Indicate Viewport Position | The user can determine the viewport's position relative to the full extent of the rendered content. | A | 1.8.11 Indicate Viewport Position: The user can determine the viewport's position relative to the full extent of the rendered content. (Level A) |
| 1.8.5 | 45 | 01.08.05 | 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, restoring the prior point of regard, input focus and selection. | A | 1.8.5 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.(Level A) |
| 1.8.6 | 46 | 01.08.06 | h3 | Open on Request | The user can specify whether author content can open new top-level viewports (e.g. windows or tabs). | A | 1.8.6 Open on Request: The user can specify whether author content can open new top-level viewports (e.g. windows or tabs). (Level A) |
| 1.8.7 | 47 | 01.08.07 | 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.7 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.10 | 48 | 01.08.10 | h3 | Same UI | The user can specify that all top-level viewports (e.g. windows or tabs) follow the current user interface configuration. | AA | 1.8.10 Same UI: The user can specify that all top-level viewports (e.g. windows or tabs) follow the current user interface configuration. (Level AA) |
| 1.10 | 49 | 01.10 | h2 | Provide alternative views | Provide alternative views. | Guideline 1.10 - Provide alternative views. | |
| 1.10-N1 | 50 | 01.10-N01 | note | Provide alternative views | Summary: The user can view the source of content (1.10.1), or an "outline" view (1.10.2), and may specify the elements to be used for the outline view (1.10.3). | Summary: The user can view the source of content (1.10.1), or an "outline" view (1.10.2), and may specify the elements to be used for the outline view (1.10.3). | |
| 1.10.1 | 51 | 01.10.01 | h3 | Source View | The user can view all source text that is available to the user agent. | AA | 1.10.1 Source View: The user can view all source text that is available to the user agent. (Level AA) |
| 1.10.2 | 52 | 01.10.02 | h3 | 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). | AA | 1.10.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) |
| 1.10.2-N1 | 53 | 01.10.02-N01 | note | Outline View | The outline constitutes the important structural elements for the user (See 1.10.3). 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. | Note: The outline constitutes the important structural elements for the user (See 1.10.3). 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. | |
| 1.10.3 | 54 | 01.10.03 | h3 | Configure Elements for Outline View | The user can configure the set of important elements for the outline view, including by element type (e.g. headers). | AAA | 1.10.3 Configure Elements for Outline View: The user can configure the set of important elements for the outline view, including by element type (e.g. headers). (Level AAA) |
| 1.11 | 55 | 01.11 | h2 | Provide element information | Provide element information. | Guideline 1.11 - Provide element information. | |
| 1.11-N1 | 56 | 01.11-N01 | note | Provide element information | Summary:The user agent presents information about content relationships (e.g. form labels, table headers)(1.11.1), and extended link information (e.g. title, internal vs. external) (1.11.2) | Summary:The user agent presents information about content relationships (e.g. form labels, table headers)(1.11.1), and extended link information (e.g. title, internal vs. external) (1.11.2) | |
| 1.11.1 | 57 | 01.11.01 | h3 | Access Relationships | The user can access explicitly-defined relationships based on the user's position in content (e.g. show form control's label, show label's form control, show a cell's table headers). | A | 1.11.1 Access Relationships: The user can access explicitly-defined relationships based on the user's position in content (e.g. show form control's label, show label's form control, show a cell's table headers). (Level A) |
| 1.11.2 | 58 | 01.11.02 | h3 | Extended Link Information | The user agent provides for each link: * 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) | AAA | 1.11.2 Extended Link Information: The user agent provides 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) |
| 2 | 59 | 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 | 60 | 02.01 | h2 | Ensure full keyboard access | Ensure full keyboard access. | Guideline 2.1 - Ensure full keyboard access. | |
| 2.1-N1 | 61 | 02.01-N01 | note | Ensure full keyboard access | Summary: Users can operate all functions (2.1.1), and move focus (2.1.2, 2.1.3) using just the keyboard. Users can activate important or common features with shortcut keys, (2.1.8), override keyboard shortcuts in content and user interface (2.1.4), escape keyboard traps (2.1.5), specify that selecting an item in a dropdown list or menuoes not activate that item or move to that new web page (2.1.6) and use standard keys for that platform (2.1.7). | Summary: Users can operate all functions (2.1.1), and move focus (2.1.2, 2.1.3) using just the keyboard. Users can activate important or common features with shortcut keys, (2.1.8), override keyboard shortcuts in content and user interface (2.1.4), escape keyboard traps (2.1.5), specify that selecting an item in a dropdown list or menuoes not activate that item or move to that new web page (2.1.6) and use standard keys for that platform (2.1.7). | |
| 2.1.1 | 62 | 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 mouse input or other input methods in addition to keyboard operation. | 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 mouse input or other input methods in addition to keyboard operation. (Level A) |
| 2.1.2 | 63 | 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 | 64 | 02.01.03 | h3 | Viewport Navigation | The user can move the active keyboard focus to any viewport. | A | 2.1.3 Viewport Navigation: The user can move the active keyboard focus to any viewport. (Level A) |
| 2.1.4 | 65 | 02.01.04 | h3 | 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. arrow keys for navigating within menus). | A | 2.1.4 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. arrow keys for navigating within menus). (Level A) |
| 2.1.5 | 66 | 02.01.05 | h3 | No Keyboard Trap | If keyboard focus can be moved to a component using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, users are advised of the method for moving focus away. The user agent prevents keyboard traps as follows: (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 | A | 2.1.5 No Keyboard Trap: If keyboard focus can be moved to a component using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it 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)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 |
| 2.1.6 | 67 | 02.01.06 | h3 | 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). | A | 2.1.6 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) |
| 2.1.7 | 68 | 02.01.07 | h3 | Follow Text Keyboard Conventions | Views that render text support the standard text area conventions for the operating environment. | A | 2.1.7 Follow Text Keyboard Conventions: Views that render text support the standard text area conventions for the operating environment. (Level A) |
| 2.1.8 | 69 | 02.01.08 | h3 | Efficient Keyboard Access | The user agent user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access. | A | 2.1.8 Efficient Keyboard Access: The user agent user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access. (Level A) |
| 2.1.9 | 70 | 02.01.09 | h3 | Allow Override of User Interface 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. | AA | 2.1.9 Allow Override of User Interface 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) |
| 2.2 | 71 | 02.02 | h2 | Provide sequential navigation | Provide sequential navigation | Guideline 2.2 - Provide sequential navigation | |
| 2.2-N1 | 72 | 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 | 73 | 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 | 74 | 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 | 75 | 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 | 76 | 02.02.04 | h3 | Options for Wrapping in Navigation | When user interaction with web content causes focus wrapping at the, the user can prevent wrapping or the user can receive feedback when wrapping. | AA | 2.2.4 Options for Wrapping in Navigation: When user interaction with web content causes focus wrapping at the, the user can prevent wrapping or the user can receive feedback when wrapping. (Level AA) |
| 2.3 | 77 | 02.03 | h2 | Provide direct navigation and activation | Provide direct navigation and activation | Guideline 2.3 - Provide direct navigation and activation | |
| 2.3-N1 | 78 | 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 the direct commands to their needs (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 the direct commands to their needs (2.3.5). | |
| 2.3.1 | 79 | 02.03.01 | h3 | Direct Navigation to Important Elements | The user can navigate directly to important (structural and operable) elements in rendered content. | A | 2.3.1 Direct Navigation to Important Elements: The user can navigate directly to important (structural and operable) elements in rendered content. (Level A) |
| 2.3.2 | 80 | 02.03.02 | h3 | Present Direct Commands in Rendered Content | The user can have any recognized direct commands in rendered content (e.g. accesskey, landmark) be presented with their associated elements. | A | 2.3.2 Present Direct Commands in Rendered Content: The user can have any recognized direct commands in rendered content (e.g. accesskey, landmark) be presented with their associated elements. (Level A) |
| 2.3.x | 81 | 02.03.x | h3 | Discover navigation and activation keystrokes | The user can discover direct navigation and activation keystrokes both programmatically and via perceivable labels. | A | 2.3.x Discover navigation and activation keystrokes: The user can discover direct navigation and activation keystrokes both programmatically and via perceivable labels. (Level A) |
| 2.3.3 | 82 | 02.03.03 | h3 | Direct activation | The user can move directly to and activate any operable elements in rendered content. | AA | 2.3.3 Direct activation: The user can move directly to and activate any operable elements in rendered content. (Level AA) |
| 2.3.4 | 83 | 02.03.04 | h3 | Present Direct Commands in User Interface | The user can 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). | AA | 2.3.4 Present Direct Commands in User Interface: The user can 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) |
| 2.3.5 | 84 | 02.03.05 | h3 | Allow 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. | AA | 2.3.5 Allow 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) |
| 2.4 | 85 | 02.04 | h2 | Provide text search | Provide text search. | Guideline 2.4 - Provide text search. | |
| 2.4-N1 | 86 | 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 alternatives (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 alternatives (2.4.5). | |
| 2.4.1 | 87 | 02.04.01 | h3 | Find | 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 Find: 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 | 88 | 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 | 89 | 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 | 90 | 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 | 91 | 02.04.05 | h3 | Advanced Find | The user can search with a case-sensitivity option and the ability to search all content (including alternative content, hidden content, and captions) for any sequence of characters from the document character set. | AA | 2.4.5 Advanced Find: The user can search with a case-sensitivity option and the ability to search all content (including alternative content, hidden content, and captions) for any sequence of characters from the document character set. (Level AA) |
| 2.5 | 92 | 02.05 | h2 | Provide structural navigation | Provide structural navigation. | Guideline 2.5 - Provide structural navigation. | |
| 2.5-N1 | 93 | 02.05-N01 | note | Provide structural navigation | Summary: Users can customize user agent settings related to accessibility (2.7.1) with settings being saved between sessions (2.7.2) and restore settings to default values (2.7.3). Users can have multiple sets of preferences (2.7.4), have related settings restored to default as a group (2.7.5) and adjust preferences outside the user agent main user interface (2.7.6). Users can also transfer settings between devices (2.7.7) and are offered a wizard to assist in user customization (2.7.8). | Summary: Users can customize user agent settings related to accessibility (2.7.1) with settings being saved between sessions (2.7.2) and restore settings to default values (2.7.3). Users can have multiple sets of preferences (2.7.4), have related settings restored to default as a group (2.7.5) and adjust preferences outside the user agent main user interface (2.7.6). Users can also transfer settings between devices (2.7.7) and are offered a wizard to assist in user customization (2.7.8). | |
| 2.5.3 | 94 | 02.05.03 | h3 | Location in Hierarchy | The user can view the path of nodes leading from the root of any content hierarchy in which the structure and semantics are implied by presentation, as opposed to an explicit logical structure with defined semantics (such as the HTML5 Canvas Element), or as a consequence of decentralized-extensibility (such as the HTML5 item / itemprop microdata elements), and only if the user agent keeps an internal model of the hierarchy that it does not expose via the DOM or some other accessibility mechanism. . | A | 2.5.3 Location in Hierarchy: The user can view the path of nodes leading from the root of any content hierarchy in which the structure and semantics are implied by presentation, as opposed to an explicit logical structure with defined semantics (such as the HTML5 Canvas Element), or as a consequence of decentralized-extensibility (such as the HTML5 item / itemprop microdata elements), and only if the user agent keeps an internal model of the hierarchy that it does not expose via the DOM or some other accessibility mechanism. (Level A) . |
| 2.5.5 | 95 | 02.05.05 | h3 | Access to Relationships which Aid Navigation | The user can access explicitly-defined relationships based on the user's position in content, and the path of nodes leading from the root of any content hierarchy to that position. | AA | 2.5.5 Access to Relationships which Aid Navigation: The user can access explicitly-defined relationships based on the user's position in content, and the path of nodes leading from the root of any content hierarchy to that position. (Level AA) |
| 2.5.7 | 96 | 02.05.07 | h3 | Configure Elements for Structural Navigation | The user can configure the sets of important elements (including element types) for structured navigation and hierarchical/outline view. | AAA | 2.5.7 Configure Elements for Structural Navigation: The user can configure the sets of important elements (including element types) for structured navigation and hierarchical/outline view. (Level AAA) |
| 2.6 | 97 | 02.06 | h2 | Provide access to event handlers | Provide access to event handlers | Guideline 2.6 - Provide access to event handlers | |
| 2.6-N1 | 98 | 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 (2.6.1) and activate an element's events individually (2.6.2) or [@@ Editor's Note: PLACEHOLDER @@] (2.6.3) | 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 (2.6.1) and activate an element's events individually (2.6.2) or [@@ Editor's Note: PLACEHOLDER @@] (2.6.3) | |
| 2.6.1 | 99 | 02.06.01 | h3 | List event handlers | The user can call up a list of input device event handlers explicitly associated with the keyboard focus element, and activate any one or more of the event handlers. | A | 2.6.1 List event handlers: The user can call up a list of input device event handlers explicitly associated with the keyboard focus element, and activate any one or more of the event handlers. (Level A) |
| 2.7 | 100 | 02.07 | h2 | Configure and store preference settings | Configure and store preference settings. | Guideline 2.7 - Configure and store preference settings. | |
| 2.7-N1 | 101 | 02.07-N01 | note | Configure and store preference settings | Summary: Users can configure and restore accessibility preference settings (2.7.1, 2.7.3), and accessibility settings persist between sessions (2.7.2). Users can manage multiple sets of preference settings and restore groups of settings to defaults (2.7.4, 2.7.5), and adjust preference setting outside the user interface so the current user interface does not prevent access (2.7.6). It's also recommended that groups of settings can be transported to compatible systems, and a wizard be available to help users configure their preferences (2.7.7, 2.7.8). | Summary: Users can configure and restore accessibility preference settings (2.7.1, 2.7.3), and accessibility settings persist between sessions (2.7.2). Users can manage multiple sets of preference settings and restore groups of settings to defaults (2.7.4, 2.7.5), and adjust preference setting outside the user interface so the current user interface does not prevent access (2.7.6). It's also recommended that groups of settings can be transported to compatible systems, and a wizard be available to help users configure their preferences (2.7.7, 2.7.8). | |
| 2.7.2 | 102 | 02.07.02 | h3 | Persistent Accessibility Settings | User agent accessibility preference settings persist between sessions. | A | 2.7.2 Persistent Accessibility Settings: User agent accessibility preference settings persist between sessions. (Level A) |
| 2.7.3 | 103 | 02.07.03 | h3 | Restore all to default | The user can restore all preference settings to default values. | A | 2.7.3 Restore all to default: The user can restore all preference settings to default values. (Level A) |
| 2.7.4 | 104 | 02.07.04 | h3 | Multiple Sets of Preference Settings | The user can save and retrieve multiple sets of user agent preference settings. | AA | 2.7.4 Multiple Sets of Preference Settings: The user can save and retrieve multiple sets of user agent preference settings. (Level AA) |
| 2.7.6 | 105 | 02.07.06 | h3 | Change preference setting outside the user interface | The user can adjust preference settings from outside the user agent user interface. | AA | 2.7.6 Change preference setting outside the user interface: The user can adjust preference settings from outside the user agent user interface. (Level AA) |
| 2.7.7 | 106 | 02.07.07 | h3 | Portable Preference Settings | The user can transfer preference settings across locations onto a compatible system. | AAA | 2.7.7 Portable Preference Settings: The user can transfer preference settings across locations onto a compatible system. (Level AAA) |
| 2.7.8 | 107 | 02.07.08 | h3 | Preferences Wizard | One or more wizards help the user to configure the accessibility-related user agent preferences. | AAA | 2.7.8 Preferences Wizard: One or more wizards help the user to configure the accessibility-related user agent preferences. (Level AAA) |
| 2.8 | 108 | 02.08 | h2 | Provide toolbar configuration | Provide toolbar configuration. | Guideline 2.8 - Provide toolbar configuration. | |
| 2.8-N1 | 109 | 02.08-N01 | note | Provide toolbar configuration | Summary: It's recommended that users can add, remove and configure the position of graphical user agent controls (2.8.1) and restore them to their default settings (2.8.2). | Summary: It's recommended that users can add, remove and configure the position of graphical user agent controls (2.8.1) and restore them to their default settings (2.8.2). | |
| 2.8.1 | 110 | 02.08.01 | h3 | Configure Position | The user can add, remove, and reorder any toolbars and similar containers, and the items within them. | AA | 2.8.1 Configure Position: The user can add, remove, and reorder any toolbars and similar containers, and the items within them. (Level AA) |
| 2.8.2 | 111 | 02.08.02 | h3 | Restore Default Toolbars | The user can restore the default toolbar, panel, or inspector configuration. | AAA | 2.8.2 Restore Default Toolbars: The user can restore the default toolbar, panel, or inspector configuration. (Level AAA) |
| 2.9 | 112 | 02.09 | h2 | Allow time-independent interaction | Allow time-independent interaction. | Guideline 2.9 - Allow time-independent interaction. | |
| 2.9-N1 | 113 | 02.09-N01 | note | Allow time-independent interaction | 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 | 114 | 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 | 115 | 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 | 116 | 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 | 117 | 02.10-N01 | note | Help users avoid flashing that could cause seizures | Summary: The user can avoid potential seizures with a default browser configuration that does not flash 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: The user can avoid potential seizures with a default browser configuration that does not flash 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 | 118 | 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 | 119 | 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 | 120 | 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 | 121 | 02.11-N01 | note | Provide control of content that may reduce accessibility | Summary: The user can control background images (2.11.1); render and control placeholders for time-based media and executable content (2.11.2, 2.11.3, 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); scale and position alternative media tracks (2.11.11); and adjust contrast and brightness of visual time-based media (2.11.12). | Summary: The user can control background images (2.11.1); render and control placeholders for time-based media and executable content (2.11.2, 2.11.3, 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); scale and position alternative media tracks (2.11.11); and adjust contrast and brightness of visual time-based media (2.11.12). | |
| 2.11.1 | 122 | 02.11.01 | h3 | Background Image Toggle | The user has the global option to hide or show background images. | A | 2.11.1 Background Image Toggle: The user has the global option to hide or show background images. (Level A) |
| 2.11.2 | 123 | 02.11.02 | h3 | Time-Based Media Load-Only | The user can have placeholders rendered for 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 have placeholders rendered for time-based media content, such that the content is not played until explicit user request. (Level A) |
| 2.11.3 | 124 | 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 | 125 | 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 | 126 | 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: * The user can adjust the playback rate of the time-based media tracks to between 50% and 250% of real time. * Speech whose playback rate has been adjusted by the user maintains pitch in order to limit degradation of the speech quality. * Audio and video tracks remain synchronized across this required range of playback rates. * 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) * The user can adjust the playback rate of the time-based media tracks to between 50% and 250% of real time. * Speech whose playback rate has been adjusted by the user maintains pitch in order to limit degradation of the speech quality. * Audio and video tracks remain synchronized across this required range of playback rates. * The user agent provides a function that resets the playback rate to normal (100%). |
| 2.11.6 | 127 | 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 | 128 | 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 | 129 | 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 | 130 | 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. These selections may override 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. These selections may override global default settings for captions, audio descriptions, etc. (Level AA) |
| 2.11.11 | 131 | 02.11.11 | h3 | Scale and position visual alternative media tracks | The user can scale and position alternative media tracks independent of base video. | AAA | 2.11.11 Scale and position visual alternative media tracks: The user can scale and position alternative media tracks independent of base video. (Level AAA) |
| 2.11.12 | 132 | 02.11.12 | h3 | Video Contrast and Brightness | Users can adjust the contrast and brightness of visual time-based media. | AAA | 2.11.12 Video Contrast and Brightness: Users can adjust the contrast and brightness of visual time-based media. (Level AAA) |
| 2.11.12-N1 | 133 | 02.11.12-N01 | note | Video Contrast and Brightness | Guideline 2.11 and its success criteria only applie to images, animations, video, audio, etc. that the user agent can recognize. | Applicability Notes: Guideline 2.11 and its success criteria only applie to images, animations, video, audio, etc. that the user agent can recognize. | |
| 2.12 | 134 | 02.12 | h2 | Other Input Devices | Other Input Devices | Guideline 2.12 - Other Input Devices | |
| 2.12-N1 | 135 | 02.12-N01 | note | Other Input Devices | 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 | 136 | 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 | 137 | 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 | 138 | 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 | 139 | 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 | 140 | 03.01 | h2 | Help users avoid unnecessary messages | Help users avoid unnecessary messages. | Guideline 3.1 - Help users avoid unnecessary messages. | |
| 3.1-N1 | 141 | 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-N2 | 142 | 03.01-N02 | note | Help users avoid unnecessary messages | @@ 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.@@ | @@ 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 | 143 | 03.01.02 | h3 | 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. | AA | 3.1.2 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. (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 choose to confirm form submissions. [@@ Editor's Note: Add SC for built-in spell checking, and back button (navigational undo)@@] | Summary: Users can choose to confirm form submissions. [@@ Editor's Note: Add SC for built-in spell checking, and back button (navigational undo)@@] | |
| 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.3 | 147 | 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 | 148 | 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 | 149 | 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 | 150 | 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 | 151 | 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 | 152 | 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 | 153 | 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 | 154 | 03.04-N01 | note | The user agent must behave in a predictable fashion | Summary: Moving the focus allows presentation of information (e.g. tooltips) but does not cause any other action (3.4.2). Users can prevent non-requested focus changes (3.4.1). | Summary: Moving the focus allows presentation of information (e.g. tooltips) but does not cause any other action (3.4.2). Users can prevent non-requested focus changes (3.4.1). | |
| 3.4.1 | 155 | 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) |
| 3.4.2 | 156 | 03.04.02 | h3 | Avoid Side Effects of Navigation | The user can move the keyboard focus without causing the user agent to take any further action, other than the presentation of information (e.g. scrolling or pop-ups that do not change the focus or selection). | A | 3.4.2 Avoid Side Effects of Navigation: The user can move the keyboard focus without causing the user agent to take any further action, other than the presentation of information (e.g. scrolling or pop-ups that do not change the focus or selection). (Level A) |
| 3.4.2-N1 | 157 | 03.04.02-N01 | note | Avoid Side Effects of Navigation | @@ Editors' Note: Missing: Greater ease in interpreting security messaging. Should be cross-referenced with the security working group. @@ | @@ Editors' Note: Missing: Greater ease in interpreting security messaging. Should be cross-referenced with the security working group. @@ | |
| 4 | 158 | 04 | h1 | Facilitate programmatic access | Facilitate programmatic access | PRINCIPLE 4: Facilitate programmatic access | |
| 4.1 | 159 | 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 | 160 | 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 | 161 | 04.01.01 | h3 | Platform Accessibility Architecture | The user agent supports a platform accessibility architecture relevant to the operating environment. | A | 4.1.1 Platform Accessibility Architecture: The user agent supports a platform accessibility architecture relevant to the operating environment. (Level A) |
| 4.1.2 | 162 | 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 architecture. | 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 architecture. (Level A) |
| 4.1.3 | 163 | 04.01.03 | h3 | Accessible Alternative | If a component of the user agent user interface cannot be exposed through the platform accessibility architecture, then the user agent provides an equivalent alternative that is exposed through the platform accessibility architecture. | A | 4.1.3 Accessible Alternative: If a component of the user agent user interface cannot be exposed through the platform accessibility architecture, then the user agent provides an equivalent alternative that is exposed through the platform accessibility architecture. (Level A) |
| 4.1.4 | 164 | 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 | 165 | 04.01.05 | h3 | Write Access | If the user agent keeps an internal representation of the user content in terms of element structure, relationships between elements, element meaning, or some combination thereof, it must expose this internal representation via an appropriate means (normally by using the platform accessibility architecture or a programmatically available DOM). | A | 4.1.5 Write Access: If the user agent keeps an internal representation of the user content in terms of element structure, relationships between elements, element meaning, or some combination thereof, it must expose this internal representation via an appropriate means (normally by using the platform accessibility architecture or a programmatically available DOM). (Level A) |
| 4.1.6 | 166 | 04.01.06 | h3 | Expose Accessible Properties | If any of the following properties are supported by the platform accessibility architecture, make the properties available to the accessibility platform architecture: (1) the bounding dimensions and coordinates of onscreen elements (2) font family of text (3) font size of text (4) foreground color of text (5) background color of text. (6) change state/value notifications (7) selection (8) highlighting (9) input device focus (10) direct keyboard commands | A | 4.1.6 Expose Accessible Properties: If any of the following properties are supported by the platform accessibility architecture, make the properties available to the accessibility platform architecture: (Level A) (1) the bounding dimensions and coordinates of onscreen elements (2) font family of text (3) font size of text (4) foreground color of text (5) background color of text. (6) change state/value notifications (7) selection (8) highlighting (9) input device focus (10) direct keyboard commands |
| 4.1.7 | 167 | 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) |
| 4.2 | 168 | 04.02 | h2 | Facilitate programmatic access to nested user agents | Facilitate programmatic access to nested user agents | Guideline 4.2 - Facilitate programmatic access to nested user agents | |
| 4.2-N1 | 169 | 04.02-N01 | note | Facilitate programmatic access to nested user agents | Summary: Input focus correctly transitions between nested user agents (4.2.1),users can retrieve input focus at any time (4.2.2) and input focus never gets stuck in any nested user agent (4.2.3). | Summary: Input focus correctly transitions between nested user agents (4.2.1),users can retrieve input focus at any time (4.2.2) and input focus never gets stuck in any nested user agent (4.2.3). | |
| 4.2.1 | 170 | 04.02.01 | h3 | 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. | A | 4.2.1 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) |
| 4.2.2 | 171 | 04.02.02 | h3 | Retrieve Focus | At any time, the user is able to retrieve input focus from a nested viewport (including a nested viewport that is a user agent). | A | 4.2.2 Retrieve Focus: At any time, the user is able to retrieve input focus from a nested viewport (including a nested viewport that is a user agent).(Level A) |
| 4.2.3 | 172 | 04.02.03 | h3 | Return Focus | At any time, the user agent can retrieve input focus from a nested viewport (including nested viewports that are user agents). | A | 4.2.3 Return Focus: At any time, the user agent can retrieve input focus from a nested viewport (including nested viewports that are user agents). (Level A) |
| 5 | 173 | 05 | h1 | Comply with applicable specifications and conventions | Comply with applicable specifications and conventions | PRINCIPLE 5: Comply with applicable specifications and conventions | |
| 5-N1 | 174 | 05-N01 | note | Comply with applicable specifications and conventions | @@ Editors' Note: 5.1 is being removed because it duplicated 5.3.2 @@ | @@ Editors' Note: 5.1 is being removed because it duplicated 5.3.2 @@ | |
| 5.2 | 175 | 05.02 | h2 | Ensure that Web-based functionality is accessible | Ensure that Web-based functionality is accessible. | Guideline 5.2 - Ensure that Web-based functionality is accessible. | |
| 5.2-N1 | 176 | 05.02-N01 | note | Ensure that Web-based functionality is accessible | 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.2.1 | 177 | 05.02.01 | h3 | Web-Based Accessible (Level A) | User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "A". | A | 5.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) |
| 5.2.2 | 178 | 05.02.02 | h3 | Web-Based Accessible (Level AA) | User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "AA". | AA | 5.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) |
| 5.2.3 | 179 | 05.02.03 | h3 | Web-Based Accessible (Level AAA) | User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "AAA". | AAA | 5.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) |
| 5.2.3-N1 | 180 | 05.02.03-N01 | note | Web-Based Accessible (Level AAA) | This guideline 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). | Applicability Notes: This guideline 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.3 | 181 | 05.03 | h2 | Support accessibility features of technologies | Support accessibility features of technologies. | Guideline 5.3 - Support accessibility features of technologies. | |
| 5.3-N1 | 182 | 05.03-N01 | note | Support accessibility features of technologies | Summary: Implement the accessibility features of all the technologies you're using, such as supporting the platform's multitasking capabilities and HTML's alt attribute for images. Document your implementation. | Summary: Implement the accessibility features of all the technologies you're using, such as supporting the platform's multitasking capabilities and HTML's alt attribute for images. Document your implementation. | |
| 5.3.1 | 183 | 05.03.01 | 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 * identified as such in the specification or * allow authors to satisfy a requirement of WCAG. | A | 5.3.1 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) : * identified as such in the specification or * allow authors to satisfy a requirement of WCAG. |
| 5.3.2 | 184 | 05.03.02 | h3 | Implement Accessibility Features of platform | Implement and cite in the conformance claim the accessibility features of content and platform technology specifications. Accessibility features are those that are either * identified as such in the specification or * allow authors to satisfy a requirement of WCAG. | A | 5.3.2 Implement Accessibility Features of platform: 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. |
| 5.3.2-N1 | 185 | 05.03.02-N01 | note | Implement Accessibility Features of platform | [@@ Editor's Note: Suzanne proposed additional SC which are holding on action items. @@]] | [@@ Editor's Note: Suzanne proposed additional SC which are holding on action items. @@]] | |
| 5.4 | 186 | 05.04 | h2 | Render content according to specification | Render content according to specification. | Guideline 5.4 - Render content according to specification. | |
| 5.4-N1 | 187 | 05.04-N01 | note | Render content according to specification | Summary: Render content according to the technology specification, including accessibility features (5.4.1), and let users choose how content types are handled, such as opening embedded images, videos, or documents in separate applications or saving them to disk (5.4.2, 5.4.3). | Summary: Render content according to the technology specification, including accessibility features (5.4.1), and let users choose how content types are handled, such as opening embedded images, videos, or documents in separate applications or saving them to disk (5.4.2, 5.4.3). | |
| 5.4-N2 | 188 | 05.04-N02 | note | Render content according to specification | [delete all of 5.4.1 ]5.4.1 Follow Specifications: The user agent renders content according to the technology specification, except where it would actually harm overall accessibility. (Level A) | [delete all of 5.4.1 ]5.4.1 Follow Specifications: The user agent renders content according to the technology specification, except where it would actually harm overall accessibility. (Level A) | |
| 5.4.2 | 189 | 05.04.02 | 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.4.2 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.4.3 | 190 | 05.04.03 | h3 | Alternative content handlers | The user can select content elements and have them rendered in alternative viewers. | AA | 5.4.3 Alternative content handlers: The user can select content elements and have them rendered in alternative viewers. (Level AA) |
| 5.4.3-N1 | 191 | 05.04.03-N01 | note | Alternative content handlers | 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. |