Based on "ED-UAAG20-20100920.txt" dated Tue Oct 5 14:22:17 2010.
| ID | Line Number | Canonical ID | Type | Title | Text | Priority | Whole Line |
|---|---|---|---|---|---|---|---|
| 1 | 1 | 01 | h1 | Comply with applicable specifications and conventions | Comply with applicable specifications and conventions | PRINCIPLE 1: Comply with applicable specifications and conventions | |
| 1.1 | 2 | 01.01 | h2 | Ensure that non-Web-based functionality is accessible. | Ensure that non-Web-based functionality is accessible. | Guideline 1.1 Ensure that non-Web-based functionality is accessible. | |
| 1.1.1 | 3 | 01.01.01 | h3 | Non-Web-Based Accessible (Level A) | Non-Web-based user agent user interfaces comply with and cite the "Level A" requirements of standards or operating environment conventions that benefit accessibility. The "Level A" requirements are those that are functionally equivalent to WCAG Level A success criteria. | A | 1.1.1 Non-Web-Based Accessible (Level A): Non-Web-based user agent user interfaces comply with and cite the "Level A" requirements of standards or operating environment conventions that benefit accessibility. The "Level A" requirements are those that are functionally equivalent to WCAG Level A success criteria. (Level A) |
| 1.1.2 | 4 | 01.01.02 | h3 | Non-Web-Based Accessible (Level AA) | Non-Web-based user agent user interfaces comply with and cite the "Level AA" requirements of standards or operating environment conventions that benefit accessibility. The "Level AA" requirements are those that are functionally equivalent to WCAG Level AA success criteria. | AA | 1.1.2 Non-Web-Based Accessible (Level AA): Non-Web-based user agent user interfaces comply with and cite the "Level AA" requirements of standards or operating environment conventions that benefit accessibility. The "Level AA" requirements are those that are functionally equivalent to WCAG Level AA success criteria. (Level AA) |
| 1.1.3 | 5 | 01.01.03 | h3 | Non-Web-Based Accessible (Level AAA) | Non-Web-based user agent user interfaces comply with and cite the "Level AAA" requirements of standards or operating environment conventions that benefit accessibility. The "Level AAA" requirements are those that are functionally equivalent to WCAG Level AAA success criteria. | AAA | 1.1.3 Non-Web-Based Accessible (Level AAA): Non-Web-based user agent user interfaces comply with and cite the "Level AAA" requirements of standards or operating environment conventions that benefit accessibility. The "Level AAA" requirements are those that are functionally equivalent to WCAG Level AAA success criteria. (Level AAA) |
| 1.1.3-N1 | 6 | 01.01.03-N01 | note | Non-Web-Based Accessible (Level AAA) | This guideline does not apply to Web-based user agent user interfaces, but does include any parts of Web-based user agents that are non-Web-based @@ Editors' Note: DEFINE@@ (e.g., client-side file uploaders). | Applicability Notes: This guideline does not apply to Web-based user agent user interfaces, but does include any parts of Web-based user agents that are non-Web-based @@ Editors' Note: DEFINE@@ (e.g., client-side file uploaders). | |
| 1.2 | 7 | 01.02 | h2 | Ensure that Web-based functionality is accessible. | Ensure that Web-based functionality is accessible. | Guideline 1.2 Ensure that Web-based functionality is accessible. | |
| 1.2.1 | 8 | 01.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 | 1.2.1 Web-Based Accessible (Level A): User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "A". (Level A) |
| 1.2.2 | 9 | 01.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 | 1.2.2 Web-Based Accessible (Level AA): User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "AA". (Level AA) |
| 1.2.3 | 10 | 01.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 | 1.2.3 Web-Based Accessible (Level AAA): User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level "AAA". (Level AAA) |
| 1.2.3-N1 | 11 | 01.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). | |
| 1.3 | 12 | 01.03 | h2 | Support accessibility features of technologies. | Support accessibility features of technologies. | Guideline 1.3 Support accessibility features of technologies. | |
| 1.3.1 | 13 | 01.03.01 | h3 | Accessibility Features | Implement and cite in the conformance claim the accessibility features of content and platform technology specifications. Accessibility features are those that are either * identified as such in the specification or * allow authors to satisfy a requirement of WCAG. | A | 1.3.1 Accessibility Features: Implement and cite in the conformance claim the accessibility features of content and platform technology specifications. Accessibility features are those that are either (Level A): * identified as such in the specification or * allow authors to satisfy a requirement of WCAG. |
| 1.4 | 14 | 01.04 | h2 | Render content according to specification. | Render content according to specification. | Guideline 1.4 Render content according to specification. | |
| 1.4.1 | 15 | 01.04.01 | h3 | Follow Specifications | Render content according to the technology specification. This includes any accessibility features of the technology (see Guideline 1.3). | A | 1.4.1 Follow Specifications: Render content according to the technology specification. This includes any accessibility features of the technology (see Guideline 1.3). (Level A) |
| 1.4.2 | 16 | 01.04.02 | h3 | Handle Unrendered Technologies | If the user agent does not render a technology, it allows the user to choose a way to handle content in that technology (e.g., by launching another application or by saving it to disk). | A | 1.4.2 Handle Unrendered Technologies: If the user agent does not render a technology, it allows the user to choose a way to handle content in that technology (e.g., by launching another application or by saving it to disk). (Level A) |
| 1.4.3 | 17 | 01.04.03 | h3 | Alternative content handlers | The user has the ability to select content elements and have them rendered in alternative viewers. | AA | 1.4.3 Alternative content handlers: The user has the ability to select content elements and have them rendered in alternative viewers. (Level AA) |
| 1.4.3-N1 | 18 | 01.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. | |
| 2 | 19 | 02 | h1 | Facilitate programmatic access | Facilitate programmatic access | PRINCIPLE 2: Facilitate programmatic access | |
| 2.1 | 20 | 02.01 | h2 | Facilitate programmatic access | Facilitate programmatic access | Guideline 2.1 Facilitate programmatic access | |
| 2.1.1 | 21 | 02.01.01 | h3 | Platform Accessibility Architecture | Support a platform accessibility architecture relevant to the operating environment. | A | 2.1.1 Platform Accessibility Architecture: Support a platform accessibility architecture relevant to the operating environment. (Level A) |
| 2.1.2 | 22 | 02.01.02 | h3 | Name, Role, State, Value, Description | For all user interface components including user interface, rendered content, generated content, and alternative content, make available the name, role, state, value, and description via a platform accessibility architecture. | A | 2.1.2 Name, Role, State, Value, Description: For all user interface components including user interface, rendered content, generated content, and alternative content, make available the name, role, state, value, and description via a platform accessibility architecture. (Level A) |
| 2.1.3 | 23 | 02.01.03 | h3 | Accessible Alternative | If a component of the user agent user interface cannot be exposed through the platform accessibility architecture, then provide an equivalent alternative that is exposed through the platform accessibility architecture. | A | 2.1.3 Accessible Alternative: If a component of the user agent user interface cannot be exposed through the platform accessibility architecture, then provide an equivalent alternative that is exposed through the platform accessibility architecture. (Level A) |
| 2.1.4 | 24 | 02.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 | 2.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) |
| 2.1.5 | 25 | 02.01.05 | h3 | Write Access | If a 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) . 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 | 2.1.5 Write Access: If a 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). 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) |
| 2.1.6 | 26 | 02.01.06 | h3 | Properties | If any of the following properties are supported by the accessibility platform architecture, make the properties available to the accessibility platform architecture: (1) the bounding dimensions and coordinates of rendered graphical objects (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 | A | 2.1.6 Properties: If any of the following properties are supported by the accessibility platform architecture, make the properties available to the accessibility platform architecture: (Level A) (1) the bounding dimensions and coordinates of rendered graphical objects (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 |
| 2.1.7 | 27 | 02.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 | 2.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) |
| 3 | 28 | 03 | h1 | Ensure that the user interface and rendered content are perceivable | Ensure that the user interface and rendered content are perceivable | PRINCIPLE 3: Ensure that the user interface and rendered content are perceivable | |
| 3.1 | 29 | 03.01 | h2 | Provide access to alternative content. | Provide access to alternative content. | Guideline 3.1 Provide access to alternative content. | |
| 3.1.1 | 30 | 03.01.01 | h3 | Identify Presence of Alternative Content | The user can have indicators rendered along with rendered elements that have alternative content (e.g. visual icons rendered in proximity of content that has short text alternatives, long descriptions, or captions). . | A | 3.1.1 Identify Presence of Alternative Content: The user can have indicators rendered along with rendered elements that have alternative content (e.g. visual icons rendered in proximity of content that has short text alternatives, long descriptions, or captions). (Level A). |
| 3.1.2 | 31 | 03.01.02 | h3 | Configurable Default Rendering | The user can globally specify which types of alternative content to render by default. | A | 3.1.2 Configurable Default Rendering: The user can globally specify which types of alternative content to render by default. (Level A) |
| 3.1.3 | 32 | 03.01.03 | h3 | Browse and Render | The user can browse the alternatives, switch between them, and render them 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 | 3.1.3 Browse and Render: The user can browse the alternatives, switch between them, and render them 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. |
| 3.1.4 | 33 | 03.01.04 | h3 | Rendering Alternative (Enhanced) | The user can globally configure a cascade of types of alternatives to render by default, in case a preferred type is unavailable. If the alternative content has a different height or width, the user agent will reflow the viewport. | AA | 3.1.4 Rendering Alternative (Enhanced): The user can globally configure a cascade of types of alternatives to render by default, in case a preferred type is unavailable. If the alternative content has a different height or width, the user agent will reflow the viewport. (Level AA) |
| 3.4 | 34 | 03.04 | h2 | Repair missing content. | Repair missing content. | Guideline 3.4 Repair missing content. | |
| 3.4.1 | 35 | 03.04.01 | h3 | Repair Missing Alternatives | The user has the option of receiving generated repair text when the user agent recognizes that the author has not provided alternative content required by the technology specification (e.g., short text alternative for an image). | A | 3.4.1 Repair Missing Alternatives: The user has the option of receiving generated repair text when the user agent recognizes that the author has not provided alternative content required by the technology specification (e.g., short text alternative for an image). (Level A) |
| 3.4.2 | 36 | 03.04.02 | h3 | Repair Empty Alternatives | The user has the option of receiving generated repair text when the user agent recognizes that the author has provided empty alternative content. | AA | 3.4.2 Repair Empty Alternatives: The user has the option of receiving generated repair text when the user agent recognizes that the author has provided empty alternative content. (Level AA) |
| 3.5 | 37 | 03.05 | h2 | Provide highlighting for selection, content focus, enabled elements, visited links. | Provide highlighting for selection, content focus, enabled elements, visited links. | Guideline 3.5 Provide highlighting for selection, content focus, enabled elements, visited links. | |
| 3.5.1 | 38 | 03.05.01 | h3 | Highlighted items | The user has the option to highlight the following classes of information so that each is uniquely distinguished. (a) selection, (b) content focus, (c) recognized enabled elements, and (d) recently visited links. | A | 3.5.1 Highlighted items: The user has the option to highlight the following classes of information so that each is uniquely distinguished. (Level A): (a) selection, (b) content focus, (c) recognized enabled elements, and (d) recently visited links. |
| 3.5.2 | 39 | 03.05.02 | h3 | Highlighting options | The highlighting options (with the same configurable range as the operating environment's conventional selection utilities) include at least (a) foreground colors, (b) background colors, and (c) input focus (with configurable color and width). | A | 3.5.2 Highlighting options: The highlighting options (with the same configurable range as the operating environment's conventional selection utilities) include at least (Level A): (a) foreground colors, (b) background colors, and (c) input focus (with configurable color and width). |
| 3.6 | 40 | 03.06 | h2 | Provide text configuration. | Provide text configuration. | Guideline 3.6 Provide text configuration. | |
| 3.6.1 | 41 | 03.06.01 | h3 | Configure Text | The user can globally set the following characteristics of visually rendered text content, overriding any specified by the author or user agent defaults (a) text scale (i.e., the general size of text) , (b) font family, and (c) text color (i.e., foreground and background). | A | 3.6.1 Configure Text: The user can globally set the following characteristics of visually rendered text content, overriding any specified by the author or user agent defaults (Level A): (a) text scale (i.e., the general size of text) , (b) font family, and (c) text color (i.e., foreground and background). |
| 3.6.2 | 42 | 03.06.02 | h3 | Preserve Distinctions | The user can preserve distinctions in the size of rendered text when that text is rescaled (e.g. headers continue to be larger than body text) within absolute limitations imposed by the platform. | A | 3.6.2 Preserve Distinctions: The user can preserve distinctions in the size of rendered text when that text is rescaled (e.g. headers continue to be larger than body text) within absolute limitations imposed by the platform. (Level A) |
| 3.6.3 | 43 | 03.06.03 | h3 | Option Range | The range of options for each text characteristic includes at least (a) the range offered by global preference settings supported by the operating environment (i.e. configured though the Control Panel or System) utility, or (b) if no such utility is available, the range supported by the conventional APIs of the operating environment for drawing text. | A | 3.6.3 Option Range: The range of options for each text characteristic includes at least (Level A): (a) the range offered by global preference settings supported by the operating environment (i.e. configured though the Control Panel or System) utility, or (b) if no such utility is available, the range supported by the conventional APIs of the operating environment for drawing text. |
| 3.7 | 44 | 03.07 | h2 | Provide volume configuration. | Provide volume configuration. | Guideline 3.7 Provide volume configuration. | |
| 3.7.1 | 45 | 03.07.01 | h3 | Global Volume | The user can globally set volume of all audio tracks it renders (including a "mute" setting) through available operating environment mechanisms. | A | 3.7.1 Global Volume: The user can globally set volume of all audio tracks it renders (including a "mute" setting) through available operating environment mechanisms. (Level A) |
| 3.7.2 | 46 | 03.07.02 | h3 | Speech Volume | The user can adjust the volume of all audio tracks the user agent renders, independently or relative to the volume level at the operating environment. | A | 3.7.2 Speech Volume: The user can adjust the volume of all audio tracks the user agent renders, independently or relative to the volume level at the operating environment. (Level A) |
| 3.8 | 47 | 03.08 | h2 | Provide synthesized speech configuration. | Provide synthesized speech configuration. | Guideline 3.8 Provide synthesized speech configuration. | |
| 3.8.1 | 48 | 03.08.01 | h3 | Speech Rate and Volume | The user can set in synthesized speech, overriding any values specified by the author * speech rate and * speech volume (independently of other sources of audio). | A | 3.8.1 Speech Rate and Volume: The user can set in synthesized speech, overriding any values specified by the author (Level A): * speech rate and * speech volume (independently of other sources of audio). |
| 3.8.2 | 49 | 03.08.02 | h3 | Speech Pitch and Range | The user can set in synthesized speech, overriding any values specified by the author (a) pitch ("pitch" refers to the average frequency of the speaking voice), and (b) pitch range ("pitch range" specifies a variation in average frequency), | AA | 3.8.2 Speech Pitch and Range: The user can set in synthesized speech, overriding any values specified by the author (Level AA): (a) pitch ("pitch" refers to the average frequency of the speaking voice), and (b) pitch range ("pitch range" specifies a variation in average frequency), |
| 3.8.3 | 50 | 03.08.03 | h3 | Advanced Speech Characteristics | The user can set all of the speech characteristics offered by the speech synthesizer, according to the full range of values available, overriding any values specified by the author. | AAA | 3.8.3 Advanced Speech Characteristics: The user can set all of the speech characteristics offered by the speech synthesizer, according to the full range of values available, overriding any values specified by the author. (Level AAA) |
| 3.8.4 | 51 | 03.08.04 | h3 | Speech Features | The following speech 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 and one where full number 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 | 3.8.4 Speech Features: The following speech 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 and one where full number 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. |
| 3.9 | 52 | 03.09 | h2 | Provide style sheetsconfiguration. | Provide style sheetsconfiguration. | Guideline 3.9 Provide style sheetsconfiguration. | |
| 3.9.1 | 53 | 03.09.01 | h3 | Author Style Sheets | If the author has supplied one or more style sheets, the user has the following options (a) select a style sheet, or (b) turn off style sheets. | A | 3.9.1 Author Style Sheets: If the author has supplied one or more style sheets, the user has the following options (Level A): (a) select a style sheet, or (b) turn off style sheets. |
| 3.9.2 | 54 | 03.09.02 | h3 | User Style Sheets | If the user has supplied one or more style sheets, the user has the following options (a) select a style sheet, or (b) turn off style sheets. | A | 3.9.2 User Style Sheets: If the user has supplied one or more style sheets, the user has the following options (Level A): (a) select a style sheet, or (b) turn off style sheets. |
| 3.10 | 55 | 03.10 | h2 | Help user to use viewports and orient within viewports. | Help user to use viewports and orient within viewports. | Guideline 3.10 Help user to use viewports and orient within viewports. | |
| 3.10.1 | 56 | 03.10.01 | h3 | Highlight Viewport | The viewport with the input focus (including nested viewports and their containers) is highlighted, and the user is able to customize attributes of the highlighted mechanism, including, but not limited to, shape, size, stroke width, color, and blink rate (if any). | A | 3.10.1 Highlight Viewport: The viewport with the input focus (including nested viewports and their containers) is highlighted, and the user is able to customize attributes of the highlighted mechanism, including, but not limited to, shape, size, stroke width, color, and blink rate (if any). (Level A) |
| 3.10.2 | 57 | 03.10.02 | h3 | Move Viewport to Selection and Focus | When a viewport's selection or input focus changes, the viewport moves as necessary to ensure that the new selection or input focus location is at least partially in the viewport. | A | 3.10.2 Move Viewport to Selection and Focus: When a viewport's selection or input focus changes, the viewport moves as necessary to ensure that the new selection or input focus location is at least partially in the viewport. (Level A) |
| 3.10.3 | 58 | 03.10.03 | h3 | @@ Editor's Note | Merged with 3.10.2. Renumber @@ | A | 3.10.3 @@ Editor's Note: Merged with 3.10.2. Renumber @@ |
| 3.10.4 | 59 | 03.10.04 | h3 | Resizable | The user has the option to make graphical viewports resizable, within the limits of the display, overriding any values specified by the author. | A | 3.10.4 Resizable: The user has the option to make graphical viewports resizable, within the limits of the display, overriding any values specified by the author. (Level A) |
| 3.10.5 | 60 | 03.10.05 | h3 | 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 | 3.10.5 Scrollbars: Graphical viewports include scrollbars if the rendered content (including after user preferences have been applied) extends beyond the viewport dimensions, overriding any values specified by the author. (Level A) |
| 3.10.6 | 61 | 03.10.06 | h3 | Viewport History | If the user agent maintains a viewport history mechanism (e.g., via the "back button") that stores previous "viable" states (i.e., that have not been negated by the content, user agent settings or user agent extensions). It maintains information about the page and embedded controls, including viewport scrolling, selection and keyboard focus. It restores the saved values when the user returns to a state in the history. | A | 3.10.6 Viewport History: If the user agent maintains a viewport history mechanism (e.g., via the "back button") that stores previous "viable" states (i.e., that have not been negated by the content, user agent settings or user agent extensions). It maintains information about the page and embedded controls, including viewport scrolling, selection and keyboard focus. It restores the saved values when the user returns to a state in the history. (Level A) |
| 3.10.7 | 62 | 03.10.07 | h3 | Open on Request | The user has the option of having "top-level"viewports (e.g., windows) only open on explicit user request. In this mode, instead of opening a viewport automatically, notify the user and allow the user to open it with an explicit request (e.g., by confirming a prompt or following a link generated by the user agent). | AA | 3.10.7 Open on Request: The user has the option of having "top-level"viewports (e.g., windows) only open on explicit user request. In this mode, instead of opening a viewport automatically, notify the user and allow the user to open it with an explicit request (e.g., by confirming a prompt or following a link generated by the user agent). (Level AA) |
| 3.10.8 | 63 | 03.10.08 | h3 | Do Not Take Focus | When configured to allow top-level viewports to open without explicit user request, the user has the option to specify that if a top-level viewport opens, it does not take the active keyboard focus . | AA | 3.10.8 Do Not Take Focus: When configured to allow top-level viewports to open without explicit user request, the user has the option to specify that if a top-level viewport opens, it does not take the active keyboard focus . (Level AA) |
| 3.10.9 | 64 | 03.10.09 | h3 | Stay on Top | The user has the option of having the viewport with the current focus be displayed and remain on top of all other viewports with which it overlaps. | AA | 3.10.9 Stay on Top: The user has the option of having the viewport with the current focus be displayed and remain on top of all other viewports with which it overlaps. (Level AA) |
| 3.10.10 | 65 | 03.10.10 | h3 | Close Viewport | The user can close any top-level viewport. | AA | 3.10.10 Close Viewport: The user can close any top-level viewport. (Level AA) |
| 3.10.10-N1 | 66 | 03.10.10-N01 | note | Close Viewport | Dialog boxes or other special purpose viewports that provide limited functionality, do not have to spawn all the user-requested features that do not apply to that special function. | Note: Dialog boxes or other special purpose viewports that provide limited functionality, do not have to spawn all the user-requested features that do not apply to that special function. | |
| 3.10.11 | 67 | 03.10.11 | h3 | Same UI | The user has the option of having all top-level viewports follow the same user interface configuration as the current or spawning viewport. | AA | 3.10.11 Same UI: The user has the option of having all top-level viewports follow the same user interface configuration as the current or spawning viewport. (Level AA) |
| 3.10.12 | 68 | 03.10.12 | h3 | Indicate Viewport Position | Indicate the viewport's position relative to rendered content (e.g., the proportion along an audio or video timeline, the proportion of a Web page before the current position ), and what proportion of the content is currently visible in the viewport along either vertical or horizontal dimension. | AAA | 3.10.12 Indicate Viewport Position: Indicate the viewport's position relative to rendered content (e.g., the proportion along an audio or video timeline, the proportion of a Web page before the current position ), and what proportion of the content is currently visible in the viewport along either vertical or horizontal dimension. (Level AAA) |
| 3.11 | 69 | 03.11 | h2 | Provide an effective focus mechanism. | Provide an effective focus mechanism. | Guideline 3.11 Provide an effective focus mechanism. | |
| 3.11.1 | 70 | 03.11.01 | h3 | Keyboard Focus | At least one keyboard focus is provided for each viewport (including frames), where enabled elements are part of the rendered content. | A | 3.11.1 Keyboard Focus: At least one keyboard focus is provided for each viewport (including frames), where enabled elements are part of the rendered content. (Level A) |
| 3.11.2 | 71 | 03.11.02 | h3 | Current Focus | The user can make the keyboard focus of each viewport the active input focus. | A | 3.11.2 Current Focus: The user can make the keyboard focus of each viewport the active input focus. (Level A) |
| 3.11.3 | 72 | 03.11.03 | h3 | User Interface Focus | An active input focus is provided. | A | 3.11.3 User Interface Focus: An active input focus is provided. (Level A) |
| 3.11.4 | 73 | 03.11.04 | h3 | Extensions Focusable | The keyboard focus can navigate within extensions to the user interface. | A | 3.11.4 Extensions Focusable: The keyboard focus can navigate within extensions to the user interface. (Level A) |
| 3.11.5 | 74 | 03.11.05 | 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 | 3.11.5 Hand-Off Focus: The user agent programmatically notifies any nested user agent(s) (e.g., plug-ins) when active input focus moves to a nested agent. (Level A) |
| 3.11.6 | 75 | 03.11.06 | h3 | Retrieve Focus | At any time, the user agent is able to retrieve input focus from a nested viewport (including nested viewports that are user agents). | A | 3.11.6 Retrieve Focus: At any time, the user agent is able to retrieve input focus from a nested viewport (including nested viewports that are user agents). (Level A) |
| 3.11.7 | 76 | 03.11.07 | h3 | Return Focus | An embedded user agent is responsible for notifying the embedding user agent that active input focus should move back to it. | A | 3.11.7 Return Focus: An embedded user agent is responsible for notifying the embedding user agent that active input focus should move back to it. (Level A) |
| 3.11.8 | 77 | 03.11.08 | h3 | Bi-Directional | The user can move the keyboard focus forward or backward to any enabled element in the viewport. | A | 3.11.8 Bi-Directional: The user can move the keyboard focus forward or backward to any enabled element in the viewport. (Level A) |
| 3.11.9 | 78 | 03.11.09 | h3 | Sequential Navigation | If the author has not specified a navigation order, the default is sequential navigation, in document order. | A | 3.11.9 Sequential Navigation: If the author has not specified a navigation order, the default is sequential navigation, in document order. (Level A) |
| 3.11.10 | 79 | 03.11.10 | h3 | Only on User Request | The user can specify that the keyboard focus of a viewport only change on explicit user request. | A | 3.11.10 Only on User Request: The user can specify that the keyboard focus of a viewport only change on explicit user request. (Level A) |
| 3.11.11 | 80 | 03.11.11 | h3 | On Focus | The user can ensure that moving the keyboard focus to or from an enabled element does not cause the user agent to take any further action. | A | 3.11.11 On Focus: The user can ensure that moving the keyboard focus to or from an enabled element does not cause the user agent to take any further action. (Level A) |
| 3.12 | 81 | 03.12 | h2 | Provide alternative views. | Provide alternative views. | Guideline 3.12 Provide alternative views. | |
| 3.12.1 | 82 | 03.12.01 | h3 | Text View | For content authored in text formats, a view of the text source is provided. | A | 3.12.1 Text View: For content authored in text formats, a view of the text source is provided. (Level A) |
| 3.12.2 | 83 | 03.12.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 | 3.12.2 Outline View: An "outline" view of rendered content is provided, composed of labels for important structural elements (e.g. heading text, table titles, form titles, and other labels that are part of the content). (Level AA) |
| 3.12.2-N1 | 84 | 03.12.02-N01 | note | Outline View | What constitutes a label is defined by each markup language specification. For example, in HTML, a heading (H1-H6) is a label for the section that follows it, a CAPTION is a label for a table, and the title attribute is a label for its element. | Note: What constitutes a label is defined by each markup language specification. For example, in HTML, a heading (H1-H6) is a label for the section that follows it, a CAPTION is a label for a table, and the title attribute is a label for its element. | |
| 3.12.3 | 85 | 03.12.03 | h3 | Configure Set of Important Elements | The user can be presented with a hierarchical view of the rendered content that conveys associations implied by author-specified presentation attributes (i.e. position and appearance). | AA | 3.12.3 Configure Set of Important Elements:The user can be presented with a hierarchical view of the rendered content that conveys associations implied by author-specified presentation attributes (i.e. position and appearance). (Level AA) |
| 3.13 | 86 | 03.13 | h2 | Provide link information. | Provide link information. | Guideline 3.13 Provide link information. | |
| 3.13.1 | 87 | 03.13.01 | h3 | Basic Link Information | The following information is provided for each link * link element content, * new viewport (whether the author has specified that the resource will open in a new viewport) | A | 3.13.1 Basic Link Information: The following information is provided for each link (Level A): * link element content, * new viewport (whether the author has specified that the resource will open in a new viewport) |
| 3.13.2 | 88 | 03.13.02 | h3 | Extended Link Information | The following information is provided 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 | 3.13.2 Extended Link Information: The following information is provided for each link (Level AAA): * link title, * technology type (of the linked Web resource) * internal/external: (whether the link is internal to the resource e.g., the link is to a target in the same Web page) |
| 4 | 89 | 04 | h1 | Ensure that the user interface is operable | Ensure that the user interface is operable | PRINCIPLE 4. Ensure that the user interface is operable | |
| 4.1 | 90 | 04.01 | h2 | Ensure full keyboard access. | Ensure full keyboard access. | Guideline 4.1 Ensure full keyboard access. | |
| 4.1.1 | 91 | 04.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 | 4.1.1 Keyboard Operation: All functionality can be operated via the keyboard using sequential or direct keyboard commands that do not require specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (e.g., free hand drawing). This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation. (Level A) |
| 4.1.2 | 92 | 04.01.02 | h3 | Keystroke Precedence | The user can specify that keystrokes be processed in the following order: user agent user interface, user agent extensions, content keystroke operations administered by the user agent (e.g., access keys, web application controls), and executable content (e.g., key press events in scripts, etc.). | A | 4.1.2 Keystroke Precedence: The user can specify that keystrokes be processed in the following order: user agent user interface, user agent extensions, content keystroke operations administered by the user agent (e.g., access keys, web application controls), and executable content (e.g., key press events in scripts, etc.). (Level A) |
| 4.1.3 | 93 | 04.01.03 | h3 | No Keyboard Trap (Minimum) | 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 | 4.1.3 No Keyboard Trap (Minimum): The user agent prevents keyboard traps as follows (Level A): (a) in the UI: if keyboard focus can be moved to a component using the keyboard, then focus can be moved away from that component using standard sequential keyboard commands (e.g., TAB key) (b) in the rendered content: provides a documented direct keyboard command that will always restore keyboard focus to a known location (e.g., the address bar). (c) in the rendered content: provides a documented direct keyboard command that will always move keyboard focus to a subsequent focusable element |
| 4.1.4 | 94 | 04.01.04 | 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 | 4.1.4 Separate Selection from Activation: The user can specify that selection is separate from activation (e.g., navigating through a set of radio buttons without changing which is the active/selected option). (Level A) |
| 4.1.5 | 95 | 04.01.05 | h3 | Standard Text Area Navigation Conventions | Views that render text support the standard text area conventions for the operating environment, including, but not necessarily limited to: character keys, Backspace/Delete, Insert, arrow key navigation (e.g., caret browsing), Page Up/Page Down, navigate to start/end, navigate by paragraph, shift-to-select mechanism. | A | 4.1.5 Standard Text Area Navigation Conventions: Views that render text support the standard text area conventions for the operating environment, including, but not necessarily limited to: character keys, Backspace/Delete, Insert, arrow key navigation (e.g., caret browsing), Page Up/Page Down, navigate to start/end, navigate by paragraph, shift-to-select mechanism. (Level A) |
| 4.1.6 | 96 | 04.01.06 | h3 | Present Direct Commands in Rendered Content | The user can have any recognized direct commands (e.g. accesskey) in rendered content be presented with their associated elements (e.g. "[Ctrl+t]" displayed after a link whose accesskey value is "t", or an audio browser reading the value or label of a form control followed by "accesskey control plus t"). | A | 4.1.6 Present Direct Commands in Rendered Content: The user can have any recognized direct commands (e.g. accesskey) in rendered content be presented with their associated elements (e.g. "[Ctrl+t]" displayed after a link whose accesskey value is "t", or an audio browser reading the value or label of a form control followed by "accesskey control plus t"). (Level A) |
| 4.1.7 | 97 | 04.01.07 | h3 | Present Direct Commands in User Interface | The user has the option to have any direct commands (e.g. keyboard shortcuts) in the user agent user interface be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). | AA | 4.1.7 Present Direct Commands in User Interface: The user has the option to have any direct commands (e.g. keyboard shortcuts) in the user agent user interface be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). (Level AA) |
| 4.1.8 | 98 | 04.01.08 | h3 | Keyboard Navigation | The user can use the keyboard to navigate from group to group of focusable items and to traverse forwards and backwards all of the focusable elements within each group. Groups include, but are not limited to, toolbars, panels, and user agent extensions. | AA | 4.1.8 Keyboard Navigation: The user can use the keyboard to navigate from group to group of focusable items and to traverse forwards and backwards all of the focusable elements within each group. Groups include, but are not limited to, toolbars, panels, and user agent extensions. (Level AA) |
| 4.1.9 | 99 | 04.01.09 | h3 | Important Command Functions | Important command functions (e.g. related to navigation, display, content, information management) are available using a single or sequence of keystrokes or key combinations. | AA | 4.1.9 Important Command Functions: Important command functions (e.g. related to navigation, display, content, information management) are available using a single or sequence of keystrokes or key combinations. (Level AA) |
| 4.1.10 | 100 | 04.01.10 | h3 | Override of UI Keyboard Commands | The user can override any keyboard shortcut binding for the user agent user interface except for conventional bindings for the operating environment (e.g. access to help). The rebinding options must include single-key and key-plus-modifier keys if available in the operating environment. | AA | 4.1.10 Override of UI Keyboard Commands: The user can override any keyboard shortcut binding for the user agent user interface except for conventional bindings for the operating environment (e.g. access to help). The rebinding options must include single-key and key-plus-modifier keys if available in the operating environment. (Level AA) |
| 4.1.11 | 101 | 04.01.11 | h3 | User Override of Accesskeys | The user can override any recognized author supplied content keybinding (i.e. access key). The user must have an option to save the override of user interface keyboard shortcuts so that the rebinding persists beyond the current session. | AA | 4.1.11 User Override of Accesskeys: The user can override any recognized author supplied content keybinding (i.e. access key). The user must have an option to save the override of user interface keyboard shortcuts so that the rebinding persists beyond the current session. (Level AA) |
| 4.1.12 | 102 | 04.01.12 | 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. access to help). | AA | 4.1.12 Specify preferred keystrokes: The user can override any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and user interface controls, except for conventional bindings for the operating environment (e.g. access to help). (Level AA) |
| 4.2 | 103 | 04.02 | h2 | Provide access to event handlers. | Provide access to event handlers. | Guideline 4.2 Provide access to event handlers. | |
| 4.2.1 | 104 | 04.02.01 | h3 | List event handlers | The user can, through keyboard input alone, call up a list of input device event handlers explicitly associated with the keyboard focus element. | A | 4.2.1 List event handlers: The user can, through keyboard input alone, call up a list of input device event handlers explicitly associated with the keyboard focus element. (Level A) |
| 4.2.2 | 105 | 04.02.02 | h3 | Activate any event handler | The user can, through keyboard input alone, activate any input device event handlers explicitly associated with the keyboard focus element. | A | 4.2.2 Activate any event handler: The user can, through keyboard input alone, activate any input device event handlers explicitly associated with the keyboard focus element. (Level A) |
| 4.2.3 | 106 | 04.02.03 | h3 | Activate all event handlers | The user can, through keyboard input alone, simultaneously activate all input device event handlers explicitly associated with the content focus element. | A | 4.2.3 Activate all event handlers: The user can, through keyboard input alone, simultaneously activate all input device event handlers explicitly associated with the content focus element. (Level A) |
| 4.3 | 107 | 04.03 | h2 | Allow time-independent interaction. | Allow time-independent interaction. | Guideline 4.3 Allow time-independent interaction. | |
| 4.3.1 | 108 | 04.03.01 | h3 | Timing Adjustable | Where time limits for user input are recognized and controllable by the user agent, the user can extend the time limit. | A | 4.3.1 Timing Adjustable: Where time limits for user input are recognized and controllable by the user agent, the user can extend the time limit. (Level A) |
| 4.4 | 109 | 04.04 | h2 | Help users avoid flashing that could cause seizures. | Help users avoid flashing that could cause seizures. | Guideline 4.4 Help users avoid flashing that could cause seizures. | |
| 4.4.1 | 110 | 04.04.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 | 4.4.1 Three Flashes or Below Threshold: In its default configuration, the user agent does not display any user interface components or recognized content that flashes more than three times in any one-second period, unless the flash is below the general flash and red flash thresholds. (Level A) |
| 4.4.2 | 111 | 04.04.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). [WCAG 2.0] | AAA | 4.4.2 Three Flashes: In its default configuration, the user agent does not display any user interface components or recognized content that flashes more than three times in any one-second period (regardless of whether not the flash is below the general flash and red flash thresholds). (Level AAA) [WCAG 2.0] |
| 4.5 | 112 | 04.05 | h2 | Configure and store preference settings. | Configure and store preference settings. | Guideline 4.5 Configure and store preference settings. | |
| 4.5.1 | 113 | 04.05.01 | h3 | 4 | 5 | 4.5.1 Change Preference Settings The user can change settings that impact accessibility. (Level A) | |
| 4.5.2 | 114 | 04.05.02 | h3 | Persistent Accessibility Settings | User agent accessibility preference settings persist between sessions. | A | 4.5.2 Persistent Accessibility Settings: User agent accessibility preference settings persist between sessions. (Level A) |
| 4.5.3 | 115 | 04.05.03 | h3 | Multiple Sets of Preference Settings | The user can save and retrieve multiple sets of user agent preference settings. | AA | 4.5.3 Multiple Sets of Preference Settings: The user can save and retrieve multiple sets of user agent preference settings. (Level AA) |
| 4.5.4 | 116 | 04.05.04 | h3 | Portable Preference Settings | The user can transfer preference settings across locations onto a compatible system. | AAA | 4.5.4 Portable Preference Settings:The user can transfer preference settings across locations onto a compatible system. (Level AAA) |
| 4.5.5 | 117 | 04.05.05 | h3 | Preferences Wizard | A wizard helps the user to configure the accessibility-related user agent preferences (at least). | AAA | 4.5.5 Preferences Wizard: A wizard helps the user to configure the accessibility-related user agent preferences (at least). (Level AAA) |
| 4.5.6 | 118 | 04.05.06 | h3 | Restore all to default | The user can restore all preference settings to default values. | A | 4.5.6 Restore all to default: The user can restore all preference settings to default values. (Level A) |
| 4.5.7 | 119 | 04.05.07 | h3 | Restore related preferences to default | The user can restore groups of related preference settings to default values (e.g. reset keyboard shortcuts, reset colors and sizes of rendered content). | AA | 4.5.7 Restore related preferences to default: The user can restore groups of related preference settings to default values (e.g. reset keyboard shortcuts, reset colors and sizes of rendered content). (Level AA) |
| 4.5.8 | 120 | 04.05.08 | h3 | Change preference setting outside the UI | The user can adjust preference settings from outside the user agent user interface. | AA | 4.5.8 Change preference setting outside the UI: The user can adjust preference settings from outside the user agent user interface. (Level AA) |
| 4.6 | 121 | 04.06 | h2 | Provide text search. | Provide text search. | Guideline 4.6 Provide text search. | |
| 4.6.1 | 122 | 04.06.01 | h3 | Find | The user can perform a search within rendered content (e.g., not hidden with a style), including text alternatives, for any sequence of characters from the document character set set. | A | 4.6.1 Find: The user can perform a search within rendered content (e.g., not hidden with a style), including text alternatives, for any sequence of characters from the document character set set. (Level A) |
| 4.6.2 | 123 | 04.06.02 | h3 | Find Direction | The user can search forward or backward from the focused location in content. The user is notified of changes in search direction. The user is notified when the search reaches the upper or lower extent of the content based on the search direction. | A | 4.6.2 Find Direction: The user can search forward or backward from the focused location in content. The user is notified of changes in search direction. The user is notified when the search reaches the upper or lower extent of the content based on the search direction. (Level A) |
| 4.6.3 | 124 | 04.06.03 | h3 | Match Found | When there is a match, the user is alerted and the viewport moves so that the matched text content is at least partially within it. The user can search for the next instance of the text from the location of the match. | A | 4.6.3 Match Found: When there is a match, the user is alerted and the viewport moves so that the matched text content is at least partially within it. The user can search for the next instance of the text from the location of the match. |
| 4.6.4 | 125 | 04.06.04 | h3 | Alert on No Match | The user is notified when there is no match or after the last match in content (i.e., prior to starting the search over from the beginning of content). | A | 4.6.4 Alert on No Match: The user is notified when there is no match or after the last match in content (i.e., prior to starting the search over from the beginning of content). (Level A) |
| 4.6.5 | 126 | 04.06.05 | h3 | Advanced Find | The user agent provides an accessible advanced search facility, with a case-sensitive and case-insensitive search option, and the ability for the user to perform a search within all content (including hidden content and captioning) for text and text alternatives, for any sequence of characters from the document character set. | AA | 4.6.5 Advanced Find: The user agent provides an accessible advanced search facility, with a case-sensitive and case-insensitive search option, and the ability for the user to perform a search within all content (including hidden content and captioning) for text and text alternatives, for any sequence of characters from the document character set. (Level AA) |
| 4.7 | 127 | 04.07 | h2 | Provide structured navigation. | Provide structured navigation. | Guideline 4.7 Provide structured navigation. | |
| 4.7.1 | 128 | 04.07.01 | 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 | 4.7.1 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) |
| 4.7.2 | 129 | 04.07.02 | h3 | Direct navigation | The user can navigate directly to important (structural and operable) elements in rendered content. . | A | 4.7.2 Direct navigation: The user can navigate directly to important (structural and operable) elements in rendered content. (Level A). |
| 4.7.3 | 130 | 04.07.03 | 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 | 4.7.3 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) |
| 4.7.4 | 131 | 04.07.04 | 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 | 4.7.4 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). |
| 4.7.4-N4 | 132 | 04.07.04-N04 | note | Location in Hierarchy | 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). | @@ Editors' Note: Success Criteria from 3.3 have been moved to 4.9. SC 3.3.3 has been moved to 5.1@@ | |
| 4.7.5 | 133 | 04.07.05 | h3 | Direct activation | The user can move directly to and activate any operable elements in rendered content. | AA | 4.7.5 Direct activation: The user can move directly to and activate any operable elements in rendered content. (Level AA) |
| 4.7.6 | 134 | 04.07.06 | h3 | Configure Set of Important Elements | The user has the option to configure the set of important elements for structured navigation, including by element type (e.g., headers, list items, images). @@ Editor's note: Review the definition of "important elements" @@ | AAA | 4.7.6 Configure Set of Important Elements: The user has the option to configure the set of important elements for structured navigation, including by element type (e.g., headers, list items, images). (Level AAA) @@ Editor's note: Review the definition of "important elements" @@ |
| 4.7.7 | 135 | 04.07.07 | h3 | Discover navigation and activation keystrokes | Direct navigation and activation keystrokes are discoverable both programmatically and via perceivable labels. | A | 4.7.7 Discover navigation and activation keystrokes: Direct navigation and activation keystrokes are discoverable both programmatically and via perceivable labels. (Level A) |
| 4.7.7-N7 | 136 | 04.07.07-N07 | note | Discover navigation and activation keystrokes | Discover navigation and activation keystrokes: Direct navigation and activation keystrokes are discoverable both programmatically and via perceivable labels. (Level A) | @@ Editor's note: Review the definition of "important elements" @@ | |
| 4.8 | 137 | 04.08 | h2 | Provide toolbar configuration. | Provide toolbar configuration. | Guideline 4.8 Provide toolbar configuration. | |
| 4.8.1 | 138 | 04.08.01 | h3 | Configure Position | When graphical user agent user interfaces have toolbars, the user can add, remove and configure the position of user agent user interface controls on those toolbars from a pre-defined set of controls. | AAA | 4.8.1 Configure Position: When graphical user agent user interfaces have toolbars, the user can add, remove and configure the position of user agent user interface controls on those toolbars from a pre-defined set of controls. (Level AAA) |
| 4.8.2 | 139 | 04.08.02 | h3 | Restore Default Toolbars | The user can restore the default toolbar configuration. | AAA | 4.8.2 Restore Default Toolbars: The user can restore the default toolbar configuration. (Level AAA) |
| 4.9 | 140 | 04.09 | h2 | Provide control of content that may reduce accessibility. | Provide control of content that may reduce accessibility. | Guideline 4.9 Provide control of content that may reduce accessibility. | |
| 4.9.1 | 141 | 04.09.01 | h3 | Background Image Toggle | The user has the global option to hide/show background images. | A | 4.9.1 Background Image Toggle: The user has the global option to hide/show background images. (Level A) |
| 4.9.2 | 142 | 04.09.02 | h3 | Time-Based Media Load-Only | The user can load time-based media content @@ Editors' Note: DEFINE@@ such that the first frame is displayed (if video), but the content is not played until explicit user request. | A | 4.9.2 Time-Based Media Load-Only: The user can load time-based media content @@ Editors' Note: DEFINE@@ such that the first frame is displayed (if video), but the content is not played until explicit user request. (Level A) |
| 4.9.3 | 143 | 04.09.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 | 4.9.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) |
| 4.9.4 | 144 | 04.09.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 | 4.9.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) |
| 4.9.5 | 145 | 04.09.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 | 4.9.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%). |
| 4.9.6 | 146 | 04.09.06 | h3 | Stop/Pause/Resume Multimedia | The user can stop, pause, and resume rendered audio and animation content (including video and animated images) that last three or more seconds at their default playback rate. | A | 4.9.6 Stop/Pause/Resume Multimedia: The user can stop, pause, and resume rendered audio and animation content (including video and animated images) that last three or more seconds at their default playback rate. (Level A) |
| 4.9.6 | 147 | 04.09.06 | h3 | Navigate Multimedia | 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 | 4.9.6 Navigate Multimedia: 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) |
| 4.9.7 | 148 | 04.09.07 | 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). | A | 4.9.7 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). |
| 4.9.8 | 149 | 04.09.08 | 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. | A | 4.9.8 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. |
| 4.9.9 | 150 | 04.09.09 | h3 | Sizing Playback Viewport | User can adjust the size of the time-based media up to the full height or width of the containing viewport. In doing so, the user can preserve aspect ratio and to adjust the size of the playback viewport to avoid cropping, within the scaling limitations imposed by the media itself. | AA | 4.9.9 Sizing Playback Viewport: User can adjust the size of the time-based media up to the full height or width of the containing viewport. In doing so, the user can preserve aspect ratio and to adjust the size of the playback viewport to avoid cropping, within the scaling limitations imposed by the media itself. (Level AA) |
| 4.9.10 | 151 | 04.09.10 | h3 | Scale and position alternative media tracks | User can scale and position alternative media tracks independent of base video. | AAA | 4.9.10 Scale and position alternative media tracks: User can scale and position alternative media tracks independent of base video. (Level AAA) |
| 4.9.11 | 152 | 04.09.11 | h3 | Adjust Playback Contrast and Brightness | User can control the contrast and brightness of the content within the playback viewport. | AAA | 4.9.11 Adjust Playback Contrast and Brightness: User can control the contrast and brightness of the content within the playback viewport. |
| 4.9.11-N1 | 153 | 04.09.11-N01 | note | Adjust Playback Contrast and Brightness | The guideline only applies to images, animations, video, audio, etc. that the user agent can recognize. | Applicability Notes: The guideline only applies to images, animations, video, audio, etc. that the user agent can recognize. | |
| 4.9.11-N2 | 154 | 04.09.11-N02 | note | Adjust Playback Contrast and Brightness | The guideline only applies to images, animations, video, audio, etc. that the user agent can recognize. | @@ Editors' Note: If the browser is playing the video natively, there is only 1 user agent. In that case, it falls on the browser to meet the UAAG spec. @@ | |
| 4.9.11-N3 | 155 | 04.09.11-N03 | note | Adjust Playback Contrast and Brightness | The guideline only applies to images, animations, video, audio, etc. that the user agent can recognize. | @@ Editors' Note: If an author uses windows media player inside the video element, the browser needs to map its native controls to the embedded wmp controls, and provide access to all the controls. @@ | |
| 4.9.11-N4 | 156 | 04.09.11-N04 | note | Adjust Playback Contrast and Brightness | The guideline only applies to images, animations, video, audio, etc. that the user agent can recognize. | @@ Editors' Note: User needs to be able to define rendering parameters of playback at render-time. @@ | |
| 5 | 157 | 05 | h1 | Ensure that the user interface is understandable | Ensure that the user interface is understandable | Principle 5: Ensure that the user interface is understandable | |
| 5.1 | 158 | 05.01 | h2 | Help users avoid unnecessary messages. | Help users avoid unnecessary messages. | Guideline 5.1 Help users avoid unnecessary messages. | |
| 5.1.1 | 159 | 05.01.01 | 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 (e.g., ignoring updating content marked "polite" ). | AA | 5.1.1 Option to Ignore: The user can turn off rendering of non-essential or low priority text messages or updating/changing information in the content based on priority properties defined by the author (e.g., ignoring updating content marked "polite" ). (Level AA) |
| 5.1.2 | 160 | 05.01.02 | h3 | Retrieval Progress | Show the progress of content retrieval. | A | 5.1.2 Retrieval Progress: Show the progress of content retrieval. (Level A) |
| 5.2 | 161 | 05.02 | h2 | Help users avoid and correct mistakes. | Help users avoid and correct mistakes. | Guideline 5.2 Help users avoid and correct mistakes. | |
| 5.2.1 | 162 | 05.02.01 | h3 | Form Submission | The user can redefine keyboard shortcuts for submitting and canceling recognized forms. | AA | 5.2.1 Form Submission: The user can redefine keyboard shortcuts for submitting and canceling recognized forms. (Level AA) |
| 5.3 | 163 | 05.03 | h2 | Document the user agent user interface including all accessibility features. | Document the user agent user interface including all accessibility features. | Guideline 5.3 Document the user agent user interface including all accessibility features. | |
| 5.3.1 | 164 | 05.03.01 | h3 | Accessible documentation | The product documentation is available in a format that conforms to WCAG 2.0 Level "A" or greater. | 5.3.1 Accessible documentation: The product documentation is available in a format that conforms to WCAG 2.0 Level "A" or greater. | |
| 5.3.2 | 165 | 05.03.02 | h3 | Document Accessibility Features | All user agent features that benefit accessibility @@ Editors' Note: DEFINE - as specified in the conformance claim@@ are documented. | A | 5.3.2 Document Accessibility Features: All user agent features that benefit accessibility @@ Editors' Note: DEFINE - as specified in the conformance claim@@ are documented. (Level A) |
| 5.3.3 | 166 | 05.03.03 | h3 | Changes Between Versions | Changes to features that affect accessibility since the previous version of the user agent are documented. | AA | 5.3.3 Changes Between Versions: Changes to features that affect accessibility since the previous version of the user agent are documented. (Level AA) |
| 5.3.4 | 167 | 05.03.04 | h3 | Centralized View | There is a centralized view of all features of the user agent that benefit accessibility, in a dedicated section of the documentation. | AA | 5.3.4 Centralized View: There is a centralized view of all features of the user agent that benefit accessibility, in a dedicated section of the documentation. (Level AA) |
| 5.3.5 | 168 | 05.03.05 | h3 | Context Sensitive Help | There is context-sensitive help on all user agent features that benefit accessibility. | AAA | 5.3.5 Context Sensitive Help: There is context-sensitive help on all user agent features that benefit accessibility. (Level AAA) |
| 5.3.6 | 169 | 05.03.06 | h3 | Appropriate Language | If characteristics of the user agent involve producing an end user experience such as speech, the user agent reacts appropriately to language changes. | AAA | 5.3.6 Appropriate Language: If characteristics of the user agent involve producing an end user experience such as speech, the user agent reacts appropriately to language changes. |
| 5.4 | 170 | 05.04 | h2 | The user agent must behave in a predictable fashion. | The user agent must behave in a predictable fashion. | 5.4 The user agent must behave in a predictable fashion. | |
| 5.4.1 | 171 | 05.04.01 | h3 | Control default focus | The user agent provides a mechanism for setting global configuration of default focus. | 5.4.1 Control default focus: The user agent provides a mechanism for setting global configuration of default focus. | |
| 5.4.2 | 172 | 05.04.02 | h3 | Unpredictable focus | The user is informed when the user agent changes focus. The user agent provides a global option to block uninitiated focus changes. | 5.4.2 Unpredictable focus: The user is informed when the user agent changes focus. The user agent provides a global option to block uninitiated focus changes. | |
| 5.4.2-N2 | 173 | 05.04.02-N02 | note | Unpredictable focus | Unpredictable focus: The user is informed when the user agent changes focus. The user agent provides a global option to block uninitiated focus changes. | @@ Editors' Note: Missing: Greater ease in interpreting security messaging. Should be cross-referenced with the security working group. @@ |