Based on "ED-UAAG20-20140923-SC.txt" dated Thu Oct 2 11:33:15 2014 (W3C WAI UAAG 2.0 format).
Created by d:\greglo\progs\perl\StandardToHTML-2014-10-02.pl at Thu Oct 2 23:56:42 2014.
| ID | Line Number | Canonical ID | Type | Title | Text | Priority | Whole Line |
|---|---|---|---|---|---|---|---|
| 1 | 1 | 01 | h1 | Ensure that the user interface and rendered content are perceivable | Ensure that the user interface and rendered content are perceivable | PRINCIPLE 1 - Ensure that the user interface and rendered content are perceivable | |
| 1.1 | 2 | 01.01 | h2 | Provide access to alternative content | Provide access to alternative content | Guideline 1.1 - Provide access to alternative content | |
| 1.1-N1 | 3 | 01.01-N01 | note | Provide access to alternative content | Summary: The user can choose to render any type of alternative content available (1.1.1) with an indicator that the alternative content is present (1.1.2) or a placeholder replacing the non-text content (1.1.3) . It's recommended that users can also choose at least one alternative, such as alt text, to be displayed by default (1.1.4). It's recommended that caption text or sign language alternative cannot obscure the video or the controls (1.1.5) and that the user can configure the size and position of media alternatives (1.1.6). | Summary: The user can choose to render any type of alternative content available (1.1.1) with an indicator that the alternative content is present (1.1.2) or a placeholder replacing the non-text content (1.1.3) . It's recommended that users can also choose at least one alternative, such as alt text, to be displayed by default (1.1.4). It's recommended that caption text or sign language alternative cannot obscure the video or the controls (1.1.5) and that the user can configure the size and position of media alternatives (1.1.6). | |
| 1.1.1 | 4 | 01.01.01 | h3 | Render Alternative Content | The user can choose to render any type of recognized alternative content that is present for a content element. | A | 1.1.1 Render Alternative Content: The user can choose to render any type of recognized alternative content that is present for a content element. (Level A) |
| 1.1.1-N1 | 5 | 01.01.01-N01 | note | Render Alternative Content | It is recommended that the user agent allow the user to choose whether the alternative content replaces or supplements the original content element. | Note: It is recommended that the user agent allow the user to choose whether the alternative content replaces or supplements the original content element. | |
| 1.1.2 | 6 | 01.01.02 | h3 | Indicate Unrendered Alternative Content | The user can specify that indicators be displayed along with rendered content when recognized unrendered alternative content is present. | A | 1.1.2 Indicate Unrendered Alternative Content: The user can specify that indicators be displayed along with rendered content when recognized unrendered alternative content is present. (Level A) |
| 1.1.3 | 7 | 01.01.03 | h3 | Replace Non-Text Content | The user can request a placeholder that incorporates recognized text alternative content instead of recognized non-text content, until explicit user request to render the non-text content. | A | 1.1.3 Replace Non-Text Content: The user can request a placeholder that incorporates recognized text alternative content instead of recognized non-text content, until explicit user request to render the non-text content. (Level A) |
| 1.1.4 | 8 | 01.01.04 | h3 | Provide Configurable Alternative Content Defaults | The user can specify which type(s) of alternative content to render by default for each type of non-text content, including time based media. | AA | 1.1.4 Provide Configurable Alternative Content Defaults: The user can specify which type(s) of alternative content to render by default for each type of non-text content, including time based media. (Level AA) |
| 1.1.5 | 9 | 01.01.05 | h3 | Facilitate Clear Display of Alternative Content for Time-based Media | For recognized on-screen alternative content for time-based media (e.g. captions, sign language video), the following are all true: | AA | 1.1.5 Facilitate Clear Display of Alternative Content for Time-based Media: For recognized on-screen alternative content for time-based media (e.g. captions, sign language video), the following are all true: (Level AA) |
| 1.1.5.1 | 10 | 01.01.05.01 | h4 | Facilitate Clear Display of Alternative Content for Time-based Media | Don't obscure controls: Displaying time-based media alternatives doesn't obscure recognized controls for the primary time-based media. | AA | * Don't obscure controls: Displaying time-based media alternatives doesn't obscure recognized controls for the primary time-based media. |
| 1.1.5.2 | 11 | 01.01.05.02 | h4 | Facilitate Clear Display of Alternative Content for Time-based Media | Don't obscure primary media: The user can specify that displaying time-based media alternatives doesn't obscure the primary time-based media. | AA | * Don't obscure primary media: The user can specify that displaying time-based media alternatives doesn't obscure the primary time-based media. |
| 1.1.5.3 | 12 | 01.01.05.03 | h4 | Facilitate Clear Display of Alternative Content for Time-based Media | Use configurable text: The user can configure recognized text within time-based media alternatives (e.g. captions) in conformance with 1.4.1. | AA | * Use configurable text: The user can configure recognized text within time-based media alternatives (e.g. captions) in conformance with 1.4.1. |
| 1.1.5-N1 | 13 | 01.01.05-N01 | note | Facilitate Clear Display of Alternative Content for Time-based Media | Depending on the screen area available, the display of the primary time-based media may need to be reduced in size to meet this requirement. | Note: Depending on the screen area available, the display of the primary time-based media may need to be reduced in size to meet this requirement. | |
| 1.1.6 | 14 | 01.01.06 | h3 | Allow Resize and Reposition of Time-based Media Alternatives | The user can configure recognized alternative content for time-based media (e.g. captions, sign language video) as follows: | AAA | 1.1.6 Allow Resize and Reposition of Time-based Media Alternatives: The user can configure recognized alternative content for time-based media (e.g. captions, sign language video) as follows: (Level AAA) |
| 1.1.6.1 | 15 | 01.01.06.01 | h4 | Allow Resize and Reposition of Time-based Media Alternatives | Resize: The user can resize alternative content for time-based media up to the size of the user agent's viewport. | AAA | * Resize: The user can resize alternative content for time-based media up to the size of the user agent's viewport. |
| 1.1.6.2 | 16 | 01.01.06.02 | h4 | Allow Resize and Reposition of Time-based Media Alternatives | Reposition: The user can reposition alternative content for time-based media to two or more of the following: above, below, to the right, to the left, and overlapping the primary time-based media. | AAA | * Reposition: The user can reposition alternative content for time-based media to two or more of the following: above, below, to the right, to the left, and overlapping the primary time-based media. |
| 1.1.6-N 1 | 17 | 01.01.06-N01 | note | Allow Resize and Reposition of Time-based Media Alternatives | Depending on the screen area available, the display of the primary time-based media may need to be reduced in size or hidden to meet this requirement. | Note 1: Depending on the screen area available, the display of the primary time-based media may need to be reduced in size or hidden to meet this requirement. | |
| 1.1.6-N 2 | 18 | 01.01.06-N02 | note | Allow Resize and Reposition of Time-based Media Alternatives | Implementation may involve displaying alternative content for time-based media in a separate viewport, but this is not required. | Note 2: Implementation may involve displaying alternative content for time-based media in a separate viewport, but this is not required. | |
| 1.2 | 19 | 01.02 | h2 | Repair missing content | Repair missing content | Guideline 1.2 - Repair missing content | |
| 1.2-N1 | 20 | 01.02-N01 | note | Repair missing content | Summary: The user can request useful alternative content when the author fails to provide it. For example, showing metadata in place of missing or empty (1.2.1) alt text. The user can ask the browser to predict missing structural information, such as field labels, table headings or section headings (1.2.2). | Summary: The user can request useful alternative content when the author fails to provide it. For example, showing metadata in place of missing or empty (1.2.1) alt text. The user can ask the browser to predict missing structural information, such as field labels, table headings or section headings (1.2.2). | |
| 1.2.1 | 21 | 01.02.01 | h3 | Support Repair by Assistive Technologies | If text alternatives for non-text content are missing or empty then both of the following are true: | AA | 1.2.1 Support Repair by Assistive Technologies: If text alternatives for non-text content are missing or empty then both of the following are true: (Level AA) |
| 1.2.1.1 | 22 | 01.02.01.01 | h4 | Support Repair by Assistive Technologies | The user agent doesn't attempt to repair the text alternatives by substituting text values that are also available to assistive technologies. | AA | * The user agent doesn't attempt to repair the text alternatives by substituting text values that are also available to assistive technologies. |
| 1.2.1.2 | 23 | 01.02.01.02 | h4 | Support Repair by Assistive Technologies | The user agent makes available metadata related to the non-text content available programmatically, but not via fields reserved for text alternatives. | AA | * The user agent makes available metadata related to the non-text content available programmatically, but not via fields reserved for text alternatives. |
| 1.2.2 | 24 | 01.02.02 | h3 | Repair Missing Structure | The user can specify whether or not the user agent should attempt to insert the following types of structural markup on the basis of author-specified presentation attributes (e.g. position and appearance): * Labels | AAA | 1.2.2 Repair Missing Structure: The user can specify whether or not the user agent should attempt to insert the following types of structural markup on the basis of author-specified presentation attributes (e.g. position and appearance): (Level AAA) * Labels |
| 1.2.2.1 | 25 | 01.02.02.01 | h4 | Repair Missing Structure | Headers (e.g. heading markup, table headers) | AAA | * Headers (e.g. heading markup, table headers) |
| 1.3 | 26 | 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 | 27 | 01.03-N01 | note | Provide highlighting for selection, keyboard focus, enabled elements, visited links | Summary: The user can visually distinguish between selected, focused, and enabled items; and recently visited links (1.3.1); with a choice of highlighting options that at least include foreground and background colors, and border color and thickness (1.3.2). | Summary: The user can visually distinguish between selected, focused, and enabled items; and recently visited links (1.3.1); with a choice of highlighting options that at least include foreground and background colors, and border color and thickness (1.3.2). | |
| 1.3.1 | 28 | 01.03.01 | h3 | Highlighted Items | The user can specify that the following classes be highlighted so that each is uniquely distinguished: | A | 1.3.1 Highlighted Items: The user can specify that the following classes be highlighted so that each is uniquely distinguished: (Level A) |
| 1.3.1.1 | 29 | 01.03.01.01 | h4 | Highlighted Items | Selection | A | * Selection |
| 1.3.1.2 | 30 | 01.03.01.02 | h4 | Highlighted Items | Active keyboard focus (indicated by focus cursors and/or text cursors) | A | * Active keyboard focus (indicated by focus cursors and/or text cursors) |
| 1.3.1.3 | 31 | 01.03.01.03 | h4 | Highlighted Items | Recognized enabled input elements (distinguished from disabled elements) | A | * Recognized enabled input elements (distinguished from disabled elements) |
| 1.3.1.4 | 32 | 01.03.01.04 | h4 | Highlighted Items | Recently visited links | A | * Recently visited links |
| 1.3.1.5 | 33 | 01.03.01.05 | h4 | Highlighted Items | Found search results | A | * Found search results |
| 1.3.2 | 34 | 01.03.02 | h3 | Highlighting Options | When highlighting classes specified by 1.3.1 Highlighted Items, the user can specify highlighting options that include at least: | AA | 1.3.2 Highlighting Options: When highlighting classes specified by 1.3.1 Highlighted Items, the user can specify highlighting options that include at least: (Level AA) |
| 1.3.2.1 | 35 | 01.03.02.01 | h4 | Highlighting Options | Foreground colors | AA | * Foreground colors |
| 1.3.2.2 | 36 | 01.03.02.02 | h4 | Highlighting Options | Background colors | AA | * Background colors |
| 1.3.2.3 | 37 | 01.03.02.03 | h4 | Highlighting Options | Borders (color, style, and thickness) | AA | * Borders (color, style, and thickness) |
| 1.3.2.4 | 38 | 01.03.02.04 | h4 | Highlighting Options | Size when the indicator is an image | AA | * Size when the indicator is an image |
| 1.3.2.5 | 39 | 01.03.02.05 | h4 | Highlighting Options | Blink rate (where implemented) | AA | * Blink rate (where implemented) |
| 1.4 | 40 | 01.04 | h2 | Provide text configuration | Provide text configuration | Guideline 1.4 - Provide text configuration | |
| 1.4-N1 | 41 | 01.04-N01 | note | Provide text configuration | Summary: The user can set text scale, color, style, line spacing, and font family globally (1.4.1, Level A). It is recommended that users set text size, color, line spacing, text style and font family for element types (1.4.2, Level AA); set character spacing, justification and margin sizes globally (1.4.3, Level AA); set capitalization, hyphenation, and borders globally (1.4.5, Level AAA); and print configured and reflowed text (1.4.4 Level AA). | Summary: The user can set text scale, color, style, line spacing, and font family globally (1.4.1, Level A). It is recommended that users set text size, color, line spacing, text style and font family for element types (1.4.2, Level AA); set character spacing, justification and margin sizes globally (1.4.3, Level AA); set capitalization, hyphenation, and borders globally (1.4.5, Level AAA); and print configured and reflowed text (1.4.4 Level AA). | |
| 1.4-N 1 | 42 | 01.04-N01 | note | Provide text configuration | Success criteria 1.4.1, 1.4.3, and 1.4.5 address configuration at a global level, that is, it changes all of the text. Success criteria 1.4.2 and 1.4.5 are at an element type level, such as configuring just the heading text. | Note 1: Success criteria 1.4.1, 1.4.3, and 1.4.5 address configuration at a global level, that is, it changes all of the text. Success criteria 1.4.2 and 1.4.5 are at an element type level, such as configuring just the heading text. | |
| 1.4-N 2 | 43 | 01.04-N02 | note | Provide text configuration | All of the success criteria under guideline 1.4 allow users to override the text characteristics specified by authors, and override user agent defaults. | Note 2: All of the success criteria under guideline 1.4 allow users to override the text characteristics specified by authors, and override user agent defaults. | |
| 1.4-N 3 | 44 | 01.04-N03 | note | Provide text configuration | The success criteria in guideline 1.4 can be met through user stylesheets. For platforms without user stylesheets, text configuration needs to be provide to users through the user agent's main user interface. | Note 3: The success criteria in guideline 1.4 can be met through user stylesheets. For platforms without user stylesheets, text configuration needs to be provide to users through the user agent's main user interface. | |
| 1.4.1 | 45 | 01.04.01 | h3 | Basic text formatting (Globally) | The user can globally set all of the following characteristics of visually rendered text content: | A | 1.4.1 Basic text formatting (Globally): The user can globally set all of the following characteristics of visually rendered text content: (Level A) |
| 1.4.1.1 | 46 | 01.04.01.01 | h4 | Basic text formatting (Globally) | Text scale with preserved size distinctions (e.g. keeping headings proportional to main font) | A | * Text scale with preserved size distinctions (e.g. keeping headings proportional to main font) |
| 1.4.1.2 | 47 | 01.04.01.02 | h4 | Basic text formatting (Globally) | Text color and background color, choosing from all platform color options | A | * Text color and background color, choosing from all platform color options |
| 1.4.1.3 | 48 | 01.04.01.03 | h4 | Basic text formatting (Globally) | Font family, choosing from all installed fonts | A | * Font family, choosing from all installed fonts |
| 1.4.1.4 | 49 | 01.04.01.04 | h4 | Basic text formatting (Globally) | Line spacing, choosing from a range with at least three values | A | * Line spacing, choosing from a range with at least three values |
| 1.4.2 | 50 | 01.04.02 | h3 | Basic text formatting (by Element) | The user can set all of the following characteristics of visually rendered text content for text element types including at least headings, input fields, and links: | AA | 1.4.2 Basic text formatting (by Element): The user can set all of the following characteristics of visually rendered text content for text element types including at least headings, input fields, and links: (Level AA) |
| 1.4.2.1 | 51 | 01.04.02.01 | h4 | Basic text formatting (by Element) | Text size or scale | AA | * Text size or scale |
| 1.4.2.2 | 52 | 01.04.02.02 | h4 | Basic text formatting (by Element) | Text color and background color, choosing from all platform color options | AA | * Text color and background color, choosing from all platform color options |
| 1.4.2.3 | 53 | 01.04.02.03 | h4 | Basic text formatting (by Element) | Font family, choosing from at least all platform fonts | AA | * Font family, choosing from at least all platform fonts |
| 1.4.2.4 | 54 | 01.04.02.04 | h4 | Basic text formatting (by Element) | Line spacing, choosing from a range with at least three values | AA | * Line spacing, choosing from a range with at least three values |
| 1.4.2.5 | 55 | 01.04.02.05 | h4 | Basic text formatting (by Element) | Text style (underline, italic, bold) | AA | * Text style (underline, italic, bold) |
| 1.4.3 | 56 | 01.04.03 | h3 | Blocks of text (Globally) | The user can globally set all of the following characteristics of visually rendered blocks of text: | AA | 1.4.3 Blocks of text (Globally): The user can globally set all of the following characteristics of visually rendered blocks of text: (Level AA) |
| 1.4.3.1 | 57 | 01.04.03.01 | h4 | Blocks of text (Globally) | Character spacing, choosing from a range with at least 5 values | AA | * Character spacing, choosing from a range with at least 5 values |
| 1.4.3.2 | 58 | 01.04.03.02 | h4 | Blocks of text (Globally) | Justification (left or right, including turning off full justification) | AA | * Justification (left or right, including turning off full justification) |
| 1.4.3.3 | 59 | 01.04.03.03 | h4 | Blocks of text (Globally) | Margins around blocks of text | AA | * Margins around blocks of text |
| 1.4.3-N1 | 60 | 01.04.03-N01 | note | Blocks of text (Globally) | For the purposes of UAAG 2.0, the base character width is the font width of the character commonly accepted as the base character for calculating kerning in the typography for that language (e.g. zero character in English). | Note: For the purposes of UAAG 2.0, the base character width is the font width of the character commonly accepted as the base character for calculating kerning in the typography for that language (e.g. zero character in English). | |
| 1.4.4 | 61 | 01.04.04 | h3 | Configured and Reflowed Text Printing | The user can print the rendered content, and the following are all true: | AA | 1.4.4 Configured and Reflowed Text Printing: The user can print the rendered content, and the following are all true: (Level AA) |
| 1.4.4.a | 62 | 01.04.04.A | h4 | Configured and Reflowed Text Printing | any visual, non-time-based, rendered content can be printed | AA | (a) any visual, non-time-based, rendered content can be printed |
| 1.4.4.b | 63 | 01.04.04.B | h4 | Configured and Reflowed Text Printing | the user can choose between available printing devices | AA | (b) the user can choose between available printing devices |
| 1.4.4.c | 64 | 01.04.04.C | h4 | Configured and Reflowed Text Printing | the user can have content printed as it is rendered on screen, reflecting any user scaling, highlighting, and other modifications | AA | (c) the user can have content printed as it is rendered on screen, reflecting any user scaling, highlighting, and other modifications |
| 1.4.4.d | 65 | 01.04.04.D | h4 | Configured and Reflowed Text Printing | the user can have printed content reflow as if the top-level viewport had been resized to match the horizontal dimension of the printing device's printable area | AA | (d) the user can have printed content reflow as if the top-level viewport had been resized to match the horizontal dimension of the printing device's printable area |
| 1.4.5 | 66 | 01.04.05 | h3 | Advanced text formatting (Globally) | The user can globally set all of the following characteristics of visually rendered blocks of text: | AAA | 1.4.5 Advanced text formatting (Globally): The user can globally set all of the following characteristics of visually rendered blocks of text: (Level AAA) |
| 1.4.5.1 | 67 | 01.04.05.01 | h4 | Advanced text formatting (Globally) | Capitalization (overriding upper case and small caps style) | AAA | * Capitalization (overriding upper case and small caps style) |
| 1.4.5.2 | 68 | 01.04.05.02 | h4 | Advanced text formatting (Globally) | Word-breaking properties (e.g. auto-hyphenation) | AAA | * Word-breaking properties (e.g. auto-hyphenation) |
| 1.4.5.3 | 69 | 01.04.05.03 | h4 | Advanced text formatting (Globally) | Borders | AAA | * Borders |
| 1.4.5-N1 | 70 | 01.04.05-N01 | note | Advanced text formatting (Globally) | This success criteria does not apply to text entered as all caps. Content authors are encouraged to use styles instead of typing text as all caps. | Note: This success criteria does not apply to text entered as all caps. Content authors are encouraged to use styles instead of typing text as all caps. | |
| 1.5 | 71 | 01.05 | h2 | Provide volume configuration | Provide volume configuration | Guideline 1.5 - Provide volume configuration | |
| 1.5-N1 | 72 | 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 | 73 | 01.05.01 | h3 | Global Volume | The user can adjust the volume of each audio tracks independently of other tracks, relative to the global volume level set through operating environment mechanisms. | A | 1.5.1 Global Volume: The user can adjust the volume of each audio tracks independently of other tracks, relative to the global volume level set through operating environment mechanisms. (Level A) |
| 1.6 | 74 | 01.06 | h2 | Provide synthesized speech configuration | Provide synthesized speech configuration | Guideline 1.6 - Provide synthesized speech configuration | |
| 1.6-N1 | 75 | 01.06-N01 | note | Provide synthesized speech configuration | Summary: If synthesized speech is produced, the user can specify speech rate, volume, and voice (1.6.1, Level A), pitch and pitch range (1.6.2, Level AA), advanced synthesizer speech characteristics such as emphasis (1.6.3, Level AAA) and features such as spelling (1.6.4, Level AAA). | Summary: If synthesized speech is produced, the user can specify speech rate, volume, and voice (1.6.1, Level A), pitch and pitch range (1.6.2, Level AA), advanced synthesizer speech characteristics such as emphasis (1.6.3, Level AAA) and features such as spelling (1.6.4, Level AAA). | |
| 1.6.1 | 76 | 01.06.01 | h3 | Speech Rate, Volume, and Voice | If synthesized speech is produced, the user can specify the following: | A | 1.6.1 Speech Rate, Volume, and Voice: If synthesized speech is produced, the user can specify the following: (Level A) |
| 1.6.1.1 | 77 | 01.06.01.01 | h4 | Speech Rate, Volume, and Voice | Speech rate | A | * Speech rate |
| 1.6.1.2 | 78 | 01.06.01.02 | h4 | Speech Rate, Volume, and Voice | Speech volume (independently of other sources of audio) | A | * Speech volume (independently of other sources of audio) |
| 1.6.1.3 | 79 | 01.06.01.03 | h4 | Speech Rate, Volume, and Voice | Voice, when more than one voice is available | A | * Voice, when more than one voice is available |
| 1.6.2 | 80 | 01.06.02 | h3 | Speech Pitch and Range | If synthesized speech is produced, the user can specify the following if offered by the speech synthesizer: | AA | 1.6.2 Speech Pitch and Range: If synthesized speech is produced, the user can specify the following if offered by the speech synthesizer: (Level AA) |
| 1.6.2.1 | 81 | 01.06.02.01 | h4 | Speech Pitch and Range | Pitch (average frequency of the speaking voice) | AA | * Pitch (average frequency of the speaking voice) |
| 1.6.2.2 | 82 | 01.06.02.02 | h4 | Speech Pitch and Range | Pitch range (variation in average frequency) | AA | * Pitch range (variation in average frequency) |
| 1.6.2-N1 | 83 | 01.06.02-N01 | note | Speech Pitch and Range | Because the technical implementations of text to speech engines vary (e.g. formant-based synthesis, concatenative synthesis), a specific engine may not support varying pitch or pitch range. A user agent should expose the availability of pitch and pitch range control if the currently selected or installed text to speech engine offers this capability. | Note: Because the technical implementations of text to speech engines vary (e.g. formant-based synthesis, concatenative synthesis), a specific engine may not support varying pitch or pitch range. A user agent should expose the availability of pitch and pitch range control if the currently selected or installed text to speech engine offers this capability. | |
| 1.6.3 | 84 | 01.06.03 | h3 | Advanced Speech Characteristics | If synthesized speech is produced, the user can adjust all of the speech characteristics provided by the speech synthesizer. | AAA | 1.6.3 Advanced Speech Characteristics: If synthesized speech is produced, the user can adjust all of the speech characteristics provided by the speech synthesizer. (Level AAA) |
| 1.6.4 | 85 | 01.06.04 | h3 | Synthesized Speech Features | If synthesized speech is produced, the following features are provided: | AA | 1.6.4 Synthesized Speech Features: If synthesized speech is produced, the following features are provided: (Level AA) |
| 1.6.4.1 | 86 | 01.06.04.01 | h4 | Synthesized Speech Features | User-defined extensions to the synthesized speech dictionary. | AA | * User-defined extensions to the synthesized speech dictionary. |
| 1.6.4.2 | 87 | 01.06.04.02 | h4 | Synthesized Speech Features | "Spell-out": text is spelled one character at a time, or according to language-dependent pronunciation rules. | AA | * "Spell-out": text is spelled one character at a time, or according to language-dependent pronunciation rules. |
| 1.6.4.3 | 88 | 01.06.04.03 | h4 | Synthesized Speech Features | At least two ways of speaking numerals: spoken as individual digits and punctuation (e.g. "one two zero three point five" for 1203.5 or "one comma two zero three point five" for 1,203.5), and spoken as full numbers are spoken (e.g. "one thousand, two hundred and three point five" for 1203.5). | AA | * At least two ways of speaking numerals: spoken as individual digits and punctuation (e.g. "one two zero three point five" for 1203.5 or "one comma two zero three point five" for 1,203.5), and spoken as full numbers are spoken (e.g. "one thousand, two hundred and three point five" for 1203.5). |
| 1.6.4.4 | 89 | 01.06.04.04 | h4 | Synthesized Speech Features | At least two ways of speaking punctuation: spoken literally, and with punctuation understood from speech characteristics like pauses. | AA | * At least two ways of speaking punctuation: spoken literally, and with punctuation understood from speech characteristics like pauses. |
| 1.6.5 | 90 | 01.06.05 | h3 | Synthesized Speech Language | If synthesized speech is produced and more than one language is available, the user can change the language. | AA | 1.6.5 Synthesized Speech Language: If synthesized speech is produced and more than one language is available, the user can change the language. (Level AA) |
| 1.7 | 91 | 01.07 | h2 | Enable configuration of user stylesheets | Enable configuration of user stylesheets | Guideline 1.7 - Enable configuration of user stylesheets | |
| 1.7-N1 | 92 | 01.07-N01 | note | Enable configuration of user stylesheets | Summary: The user agent supports user stylesheets (1.7.1, Level A), the user can choose which if any user-supplied (1.7.2, Level A) and author-supplied (1.7.3, Level A) stylesheets to use, and the user can save stylesheets (1.7.4, Level AA). | Summary: The user agent supports user stylesheets (1.7.1, Level A), the user can choose which if any user-supplied (1.7.2, Level A) and author-supplied (1.7.3, Level A) stylesheets to use, and the user can save stylesheets (1.7.4, Level AA). | |
| 1.7.1 | 93 | 01.07.01 | h3 | Support User Stylesheets | If the user agent supports a mechanism for author stylesheets, the user agent also provides a mechanism for user stylesheets. | A | 1.7.1 Support User Stylesheets: If the user agent supports a mechanism for author stylesheets, the user agent also provides a mechanism for user stylesheets. (Level A) |
| 1.7.2 | 94 | 01.07.02 | h3 | Apply User Stylesheets | If user stylesheets are supported, then the user can enable or disable user stylesheets for: | A | 1.7.2 Apply User Stylesheets: If user stylesheets are supported, then the user can enable or disable user stylesheets for: (Level A) |
| 1.7.2.1 | 95 | 01.07.02.01 | h4 | Apply User Stylesheets | All pages on specified websites, or | A | * All pages on specified websites, or |
| 1.7.2.2 | 96 | 01.07.02.02 | h4 | Apply User Stylesheets | All pages | A | * All pages |
| 1.7.3 | 97 | 01.07.03 | h3 | Disable Author Stylesheets | If the user agent supports a mechanism for author stylesheets, the user can disable the use of author stylesheets on the current page. | A | 1.7.3 Disable Author Stylesheets: If the user agent supports a mechanism for author stylesheets, the user can disable the use of author stylesheets on the current page. (Level A) |
| 1.7.4 | 98 | 01.07.04 | h3 | Save Copies of Stylesheets | The user can save copies of the stylesheets referenced by the current page. This allows the user to edit and load the copies as user stylesheets. | AA | 1.7.4 Save Copies of Stylesheets: The user can save copies of the stylesheets referenced by the current page. This allows the user to edit and load the copies as user stylesheets. (Level AA) |
| 1.8 | 99 | 01.08 | h2 | Help users to orient within, and control, windows and viewports | Help users to orient within, and control, windows and viewports | Guideline 1.8 - Help users to orient within, and control, windows and viewports | |
| 1.8-N1 | 100 | 01.08-N01 | note | Help users to orient within, and control, 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, Level A) and customizing the highlighting attributes (1.8.7, Level AA), keeping the focus within the viewport (1.8.2 & 1.8.6, Level A), resizing the viewport (1.8.8, Level A), providing scrollbars that identify when content is outside the visible region (1.8.3, Level A) and which portion is visible (1.8.4, Level A), changing the size of graphical content with zoom (1.8.5, Level A & 1.8.7, Level A), and restoring the focus and point of regard when the user returns to a previously viewed page (1.8.9, Level AA). The user can specify that all viewports have the same user interface elements (1.8.12, Level AA), if and how new viewports open (1.8.10, Level AA), and whether the new viewport automatically gets focus (1.8.11, Level AA). The user can specifiy that multi-column text blocks be reflowed into a single column (1.8.14, Level AA), that the user can override absolute layout dimensions (1.8.15, Level AA), and linearize the content (1.8.16, Level AA). The user can mark items in a web page and use shortcuts to navigate back to marked items. (1.8.17, Level AAA). | Summary: The user agent provides programmatic and visual cues to keep the user oriented. These include highlighting the viewport (1.8.1, Level A) and customizing the highlighting attributes (1.8.7, Level AA), keeping the focus within the viewport (1.8.2 & 1.8.6, Level A), resizing the viewport (1.8.8, Level A), providing scrollbars that identify when content is outside the visible region (1.8.3, Level A) and which portion is visible (1.8.4, Level A), changing the size of graphical content with zoom (1.8.5, Level A & 1.8.7, Level A), and restoring the focus and point of regard when the user returns to a previously viewed page (1.8.9, Level AA). The user can specify that all viewports have the same user interface elements (1.8.12, Level AA), if and how new viewports open (1.8.10, Level AA), and whether the new viewport automatically gets focus (1.8.11, Level AA). The user can specifiy that multi-column text blocks be reflowed into a single column (1.8.14, Level AA), that the user can override absolute layout dimensions (1.8.15, Level AA), and linearize the content (1.8.16, Level AA). The user can mark items in a web page and use shortcuts to navigate back to marked items. (1.8.17, Level AAA). | |
| 1.8.1 | 101 | 01.08.01 | h3 | Highlight Viewport | The user can have the viewport with the input focus be highlighted. | A | 1.8.1 Highlight Viewport: The user can have the viewport with the input focus be highlighted. (Level A) |
| 1.8.2 | 102 | 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 | 103 | 01.08.03 | h3 | Provide Viewport Scrollbars | When the rendered content extends beyond the viewport dimensions, users can have graphical viewports include scrollbars, overriding any values specified by the author. | A | 1.8.3 Provide Viewport Scrollbars: When the rendered content extends beyond the viewport dimensions, users can have graphical viewports include scrollbars, overriding any values specified by the author. (Level A) |
| 1.8.4 | 104 | 01.08.04 | h3 | Indicate Viewport Position | The user can determine the viewport's position relative to the full extent of the rendered content. | A | 1.8.4 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 | 105 | 01.08.05 | h3 | Allow Zoom | The user can rescale content within top-level graphical viewports as follows: | A | 1.8.5 Allow Zoom: The user can rescale content within top-level graphical viewports as follows: (Level A) |
| 1.8.5.1 | 106 | 01.08.05.01 | h4 | Allow Zoom | Zoom in: to 500% or more of the default size | A | * Zoom in: to 500% or more of the default size |
| 1.8.5.2 | 107 | 01.08.05.02 | h4 | Allow Zoom | Zoom out: to 10% or less of the default size, so the content fits within the height or width of the viewport | A | * Zoom out: to 10% or less of the default size, so the content fits within the height or width of the viewport |
| 1.8.6 | 108 | 01.08.06 | h3 | Maintain Point of Regard | The point of regard remains visible and at the same location within the viewport when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed. | A | 1.8.6 Maintain Point of Regard: The point of regard remains visible and at the same location within the viewport when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed. (Level A) |
| 1.8.7 | 109 | 01.08.07 | h3 | Customize Viewport Highlighting | When highlighting viewports as specified by 1.8.1 Highlight Viewport, the user can customize attributes of the viewport highlighting mechanism (e.g. blink rate for blinking, color and width of borders). | AA | 1.8.7 Customize Viewport Highlighting: When highlighting viewports as specified by 1.8.1 Highlight Viewport, the user can customize attributes of the viewport highlighting mechanism (e.g. blink rate for blinking, color and width of borders). (Level AA) |
| 1.8.8 | 110 | 01.08.08 | h3 | Allow Viewport Resize | The user can resize viewports within restrictions imposed by the platform, overriding any values specified by the author. | AA | 1.8.8 Allow Viewport Resize: The user can resize viewports within restrictions imposed by the platform, overriding any values specified by the author. (Level AA) |
| 1.8.9 | 111 | 01.08.09 | h3 | Provide Viewport History | For user agents that implement a history mechanism for top-level viewports (e.g. "back" button), the user can return to any state in the viewport history that is allowed by the content, including: | AA | 1.8.9 Provide Viewport History: For user agents that implement a history mechanism for top-level viewports (e.g. "back" button), the user can return to any state in the viewport history that is allowed by the content, including: (Level AA) |
| 1.8.9.a | 112 | 01.08.09.A | h4 | Provide Viewport History | restored point of regard | AA | (a) restored point of regard |
| 1.8.9.b | 113 | 01.08.09.B | h4 | Provide Viewport History | input focus | AA | (b) input focus |
| 1.8.9.c | 114 | 01.08.09.C | h4 | Provide Viewport History | selection, and | AA | (c) selection, and |
| 1.8.9.d | 115 | 01.08.09.D | h4 | Provide Viewport History | user's form field entries | AA | (d) user's form field entries |
| 1.8.10 | 116 | 01.08.10 | h3 | Allow Top-Level Viewport Open on Request | The user can specify whether author content can open new top-level viewports (e.g. windows or tabs). | AA | 1.8.10 Allow Top-Level Viewport Open on Request: The user can specify whether author content can open new top-level viewports (e.g. windows or tabs). (Level AA) |
| 1.8.11 | 117 | 01.08.11 | h3 | Allow Top-Level Viewport Focus Control | 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.11 Allow Top-Level Viewport Focus Control: 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.12 | 118 | 01.08.12 | h3 | Allow Same User Interface | The user can specify that all top-level viewports (e.g. windows or tabs) follow the defined user interface configuration. | AA | 1.8.12 Allow Same User Interface: The user can specify that all top-level viewports (e.g. windows or tabs) follow the defined user interface configuration. (Level AA) |
| 1.8.13 | 119 | 01.08.13 | h3 | Multi-Column Text Reflow | The user can specify that recognized multi-column text blocks each be reflowed into a single column. | AA | 1.8.13 Multi-Column Text Reflow: The user can specify that recognized multi-column text blocks each be reflowed into a single column. (Level AA) |
| 1.8.13-N1 | 120 | 01.08.13-N01 | note | Multi-Column Text Reflow | Some layouts may become unusable if author-specified layout is overridden. In this case, the user can turn linearization off and try another strategy. It is recommended that user agents provide a convenient way for the user to turn this behavior on and off. | Note: Some layouts may become unusable if author-specified layout is overridden. In this case, the user can turn linearization off and try another strategy. It is recommended that user agents provide a convenient way for the user to turn this behavior on and off. | |
| 1.8.14 | 121 | 01.08.14 | h3 | Ignore Absolute Layout Dimensions | The user can have the user agent override author-specified absolute layout dimensions. | AA | 1.8.14 Ignore Absolute Layout Dimensions: The user can have the user agent override author-specified absolute layout dimensions. (Level AA) |
| 1.8.15 | 122 | 01.08.15 | h3 | Linearize Content | The user can have recognized content rendered as a single column, overriding author-specified formatting of columns, tables, and positioning. | AA | 1.8.15 Linearize Content: The user can have recognized content rendered as a single column, overriding author-specified formatting of columns, tables, and positioning. (Level AA) |
| 1.8.15-N1 | 123 | 01.08.15-N01 | note | Linearize Content | Some layouts may become unusable if author-specified layout is overridden. In this case, the user can turn linearization off and try another strategy. It is recommended that user agents provide a convenient way for the user to turn this behavior on and off. | Note: Some layouts may become unusable if author-specified layout is overridden. In this case, the user can turn linearization off and try another strategy. It is recommended that user agents provide a convenient way for the user to turn this behavior on and off. | |
| 1.8.16 | 124 | 01.08.16 | h3 | Provide Web Page Bookmarks | The user can mark items in a web page, then use shortcuts to navigate back to marked items. The user can specify whether a navigation mark disappears after a session, or is persistent across sessions. | AAA | 1.8.16 Provide Web Page Bookmarks: The user can mark items in a web page, then use shortcuts to navigate back to marked items. The user can specify whether a navigation mark disappears after a session, or is persistent across sessions. (Level AAA) |
| 1.9 | 125 | 01.09 | h2 | Provide alternative views | Provide alternative views | Guideline 1.9 - Provide alternative views | |
| 1.9-N1 | 126 | 01.09-N01 | note | Provide alternative views | Summary: The user can view the source of content (1.9.2, Level AAA), and an outline view of content. (1.9.1, Level AA). | Summary: The user can view the source of content (1.9.2, Level AAA), and an outline view of content. (1.9.1, Level AA). | |
| 1.9.1 | 127 | 01.09.01 | h3 | Outline View | Users can view a navigable outline of the rendered content that allows focus to be moved to the corresponding element in the main viewport. | AA | 1.9.1 Outline View: Users can view a navigable outline of the rendered content that allows focus to be moved to the corresponding element in the main viewport. (Level AA) |
| 1.9.1-N1 | 128 | 01.09.01-N01 | note | Outline View | The elements reflected in the outline view depend on the web content technology, and may include headings, table captions, and content sections. | Note: The elements reflected in the outline view depend on the web content technology, and may include headings, table captions, and content sections. | |
| 1.9.2 | 129 | 01.09.02 | h3 | Source View | The user can view all source text that is available to the user agent. | AAA | 1.9.2 Source View: The user can view all source text that is available to the user agent. (Level AAA) |
| 1.10 | 130 | 01.10 | h2 | Provide element information | Provide element information | Guideline 1.10 - Provide element information | |
| 1.10-N1 | 131 | 01.10-N01 | note | Provide element information | Summary: The user can access information about relationships between elements (e.g. form labels, table headers) (1.10.1, Level AA), and extended link information (e.g. title, internal vs. external) (1.10.2, Level AAA) | Summary: The user can access information about relationships between elements (e.g. form labels, table headers) (1.10.1, Level AA), and extended link information (e.g. title, internal vs. external) (1.10.2, Level AAA) | |
| 1.10.1 | 132 | 01.10.01 | h3 | Show Related Elements | The user can access the information from explicitly-defined relationships in the content, including at least the following: | AA | 1.10.1 Show Related Elements: The user can access the information from explicitly-defined relationships in the content, including at least the following: (Level AA) |
| 1.10.1.a | 133 | 01.10.01.A | h4 | Show Related Elements | label for a control or image (e.g. HTML label element, figcaption or aria-labelledby attributes) | AA | (a) label for a control or image (e.g. HTML label element, figcaption or aria-labelledby attributes) |
| 1.10.1.b | 134 | 01.10.01.B | h4 | Show Related Elements | caption for a table | AA | (b) caption for a table |
| 1.10.1.c | 135 | 01.10.01.C | h4 | Show Related Elements | row and column labels for a table cell | AA | (c) row and column labels for a table cell |
| 1.10.2 | 136 | 01.10.02 | h3 | Show Element Hierarchy | The user can determine the path of element nodes going from the root element of the element hierarchy to the currently focused or selected element. | AAA | 1.10.2 Show Element Hierarchy: The user can determine the path of element nodes going from the root element of the element hierarchy to the currently focused or selected element. (Level AAA) |
| 2 | 137 | 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-N1 | 138 | 02-N01 | note | Ensure that the user interface is operable | Modality Independence: Users interacting with a web browser may do so using one or more input methods including keyboard, mouse, speech, touch, and gesture. It's critical that each user be free to use whatever input method, or combination of methods, that works best for a given situation. If every potential user task is made accessible, so multiple modalities are supported, that a user can choose what works best. For instance, if a user can't use or doesn't have access to a mouse, but can use and access a keyboard, the keyboard can call a modality independent control to activate an OnMouseOver event. Another example is a user on a mobile device that lacks keyboard who uses uses taps, wirelessly connected devices, and voice commands to simulate discrete or keyboard input. See Independent User Interface: Events for additional information on APIs and techniques for modality independent controls. | Note: Modality Independence: Users interacting with a web browser may do so using one or more input methods including keyboard, mouse, speech, touch, and gesture. It's critical that each user be free to use whatever input method, or combination of methods, that works best for a given situation. If every potential user task is made accessible, so multiple modalities are supported, that a user can choose what works best. For instance, if a user can't use or doesn't have access to a mouse, but can use and access a keyboard, the keyboard can call a modality independent control to activate an OnMouseOver event. Another example is a user on a mobile device that lacks keyboard who uses uses taps, wirelessly connected devices, and voice commands to simulate discrete or keyboard input. See Independent User Interface: Events for additional information on APIs and techniques for modality independent controls. | |
| 2.1 | 139 | 02.01 | h2 | Ensure full keyboard access | Ensure full keyboard access | Guideline 2.1 - Ensure full keyboard access | |
| 2.1-N1 | 140 | 02.01-N01 | note | Ensure full keyboard access | Summary: Every viewport has a keyboard focus (2.1.2, Level A). Users can operate all functions using just the keyboard (2.1.1, Level A), activate important or common features with shortcut keys, (2.1.6, Level A), escape keyboard traps (2.1.3, Level A), specify that selecting an item in a dropdown list or menu not activate that item (2.1.4, Level A) and use standard keys for its platform (2.1.5, Level A). | Summary: Every viewport has a keyboard focus (2.1.2, Level A). Users can operate all functions using just the keyboard (2.1.1, Level A), activate important or common features with shortcut keys, (2.1.6, Level A), escape keyboard traps (2.1.3, Level A), specify that selecting an item in a dropdown list or menu not activate that item (2.1.4, Level A) and use standard keys for its platform (2.1.5, Level A). | |
| 2.1.1 | 141 | 02.01.01 | h3 | Provide Full Keyboard Functionality | All functionality can be operated via the keyboard using sequential or direct keyboard commands that do not require specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (e.g. free hand drawing). This does not forbid and should not discourage providing other input methods in addition to keyboard operation including mouse, touch, gesture and speech. | A | 2.1.1 Provide Full Keyboard Functionality: All functionality can be operated via the keyboard using sequential or direct keyboard commands that do not require specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (e.g. free hand drawing). This does not forbid and should not discourage providing other input methods in addition to keyboard operation including mouse, touch, gesture and speech. (Level A) |
| 2.1.2 | 142 | 02.01.02 | h3 | Show Keyboard Focus | Every viewport has an active or inactive keyboard focus at all times. | A | 2.1.2 Show Keyboard Focus: Every viewport has an active or inactive keyboard focus at all times. (Level A) |
| 2.1.3 | 143 | 02.01.03 | h3 | Avoid Keyboard Traps | If keyboard focus can be moved to a component using a keyboard interface (including nested user agents), then focus can be moved away from that component using only a keyboard interface. If this requires more than unmodified arrow or Tab keys (or standard exit methods like Escape), users are advised of the method for moving focus away. | A | 2.1.3 Avoid Keyboard Traps: If keyboard focus can be moved to a component using a keyboard interface (including nested user agents), then focus can be moved away from that component using only a keyboard interface. If this requires more than unmodified arrow or Tab keys (or standard exit methods like Escape), users are advised of the method for moving focus away. (Level A) |
| 2.1.4 | 144 | 02.01.04 | h3 | Separate Selection from Activation | The user can specify that focus and selection can be moved without causing further changes in focus, selection, or the state of controls, by either the user agent or author-supplied content. | A | 2.1.4 Separate Selection from Activation: The user can specify that focus and selection can be moved without causing further changes in focus, selection, or the state of controls, by either the user agent or author-supplied content. (Level A) |
| 2.1.5 | 145 | 02.01.05 | h3 | Follow Text Keyboard Conventions | The user agent follows keyboard conventions for the operating environment. | A | 2.1.5 Follow Text Keyboard Conventions: The user agent follows keyboard conventions for the operating environment. (Level A) |
| 2.1.6 | 146 | 02.01.06 | h3 | Make Keyboard Access Efficient | The user agent user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access. | A | 2.1.6 Make Keyboard Access Efficient: The user agent user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access. (Level A) |
| 2.2 | 147 | 02.02 | h2 | Provide sequential navigation | Provide sequential navigation | Guideline 2.2 - Provide sequential navigation | |
| 2.2-N1 | 148 | 02.02-N01 | note | Provide sequential navigation | Summary: Users can use the keyboard to navigate sequentially to all the operable elements in the viewport (2.2.1, Level A) as well as between viewports (2.2.2, Level A), and the default navigation order is the document order (2.2.3, Level A). Users can optionally disable wrapping or request a signal when wrapping occurs (2.2.4, Level AA). | Summary: Users can use the keyboard to navigate sequentially to all the operable elements in the viewport (2.2.1, Level A) as well as between viewports (2.2.2, Level A), and the default navigation order is the document order (2.2.3, Level A). Users can optionally disable wrapping or request a signal when wrapping occurs (2.2.4, Level AA). | |
| 2.2.1 | 149 | 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 rendered content of 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 rendered content of the current viewport. (Level A) |
| 2.2.2 | 150 | 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 | 151 | 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 | 152 | 02.02.04 | h3 | Options for Wrapping in Navigation | The user can request notification when sequential navigation wraps at the beginning or end of a document, and can prevent such wrapping. | AA | 2.2.4 Options for Wrapping in Navigation: The user can request notification when sequential navigation wraps at the beginning or end of a document, and can prevent such wrapping. (Level AA) |
| 2.3 | 153 | 02.03 | h2 | Provide direct navigation and activation | Provide direct navigation and activation | Guideline 2.3 - Provide direct navigation and activation | |
| 2.3-N1 | 154 | 02.03-N01 | note | Provide direct navigation and activation | Summary: Users can navigate directly (e.g. using keyboard shortcuts) to elements (2.3.1, Level AA) with the option to immediately activate operable elements (2.3.2, Level AA). Display commands with the elements to make it easier for users to discover the commands (2.3.3 & 2.3.4, Level AA). The user can remap and save direct commands (2.3.5, Level AA). | Summary: Users can navigate directly (e.g. using keyboard shortcuts) to elements (2.3.1, Level AA) with the option to immediately activate operable elements (2.3.2, Level AA). Display commands with the elements to make it easier for users to discover the commands (2.3.3 & 2.3.4, Level AA). The user can remap and save direct commands (2.3.5, Level AA). | |
| 2.3.1 | 155 | 02.03.01 | h3 | Allow Direct Navigation to Enabled Elements | The user can move keyboard focus directly to any enabled element in the rendered content. | AA | 2.3.1 Allow Direct Navigation to Enabled Elements: The user can move keyboard focus directly to any enabled element in the rendered content. (Level AA) |
| 2.3.2 | 156 | 02.03.02 | h3 | Allow Direct Activation of Enabled Elements | The user can, in a single action, move keyboard focus directly to any enabled element in the rendered content and perform an activation action on that element. | AA | 2.3.2 Allow Direct Activation of Enabled Elements: The user can, in a single action, move keyboard focus directly to any enabled element in the rendered content and perform an activation action on that element. (Level AA) |
| 2.3.3 | 157 | 02.03.03 | h3 | Present Direct Commands from Rendered Content | The user can have any recognized direct commands in rendered content (e.g. accesskey, landmark) be presented with their associated elements (e.g. Alt+R to reply to a web email). | AA | 2.3.3 Present Direct Commands from Rendered Content: The user can have any recognized direct commands in rendered content (e.g. accesskey, landmark) be presented with their associated elements (e.g. Alt+R to reply to a web email). (Level AA) |
| 2.3.4 | 158 | 02.03.04 | h3 | Present Direct Commands in User Interface | The user can have any direct commands in the UA user interface (e.g. keyboard shortcuts) be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). | AA | 2.3.4 Present Direct Commands in User Interface: The user can have any direct commands in the UA user interface (e.g. keyboard shortcuts) be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). (Level AA) |
| 2.3.5 | 159 | 02.03.05 | h3 | Allow Customized Keyboard Commands | The user can remap any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and UA user interface controls, except for conventional bindings for the operating environment (e.g. arrow keys for navigating within menus). | AA | 2.3.5 Allow Customized Keyboard Commands: The user can remap any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and UA user interface controls, except for conventional bindings for the operating environment (e.g. arrow keys for navigating within menus). (Level AA) |
| 2.4 | 160 | 02.04 | h2 | Provide text search | Provide text search | Guideline 2.4 - Provide text search | |
| 2.4-N1 | 161 | 02.04-N01 | note | Provide text search | Summary: Users can search rendered content (2.4.1, Level A) forward or backward (2.4.2, Level A) and can have the matched content highlighted in the viewport (2.4.3, Level A). The user is notified in an accessible manner if there is no match (2.4.4, Level A). Users can also search by case and for text within alternative content (2.4.5, Level AA). | Summary: Users can search rendered content (2.4.1, Level A) forward or backward (2.4.2, Level A) and can have the matched content highlighted in the viewport (2.4.3, Level A). The user is notified in an accessible manner if there is no match (2.4.4, Level A). Users can also search by case and for text within alternative content (2.4.5, Level AA). | |
| 2.4.1 | 162 | 02.04.01 | h3 | Text Search | The user can perform a search within rendered content, including rendered text alternatives and rendered generated content, for any sequence of printing characters from the document character set. | A | 2.4.1 Text Search: The user can perform a search within rendered content, including rendered text alternatives and rendered generated content, for any sequence of printing characters from the document character set. (Level A) |
| 2.4.2 | 163 | 02.04.02 | h3 | Search Direction | The user can search forward or backward in rendered content. | A | 2.4.2 Search Direction: The user can search forward or backward in rendered content. (Level A) |
| 2.4.3 | 164 | 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 | 165 | 02.04.04 | h3 | Alert on Wrap or No Match | The user can choose to receive notification when there is no match to a search operation. The user can choose to receive notification when the search continues from the beginning or end of content. | A | 2.4.4 Alert on Wrap or No Match: The user can choose to receive notification when there is no match to a search operation. The user can choose to receive notification when the search continues from the beginning or end of content. (Level A) |
| 2.4.5 | 166 | 02.04.05 | h3 | Alternative Content Search | The user can perform text searches within alternative content that is text (e.g. text alternatives for non-text content, captions) even when the alternative content is not rendered onscreen. | AA | 2.4.5 Alternative Content Search: The user can perform text searches within alternative content that is text (e.g. text alternatives for non-text content, captions) even when the alternative content is not rendered onscreen. (Level AA) |
| 2.5 | 167 | 02.05 | h2 | Provide structural navigation | Provide structural navigation | Guideline 2.5 - Provide structural navigation | |
| 2.5-N1 | 168 | 02.05-N01 | note | Provide structural navigation | Summary: Users can view (2.5.1, Level AA), navigate (2.5.2, Level A), and configure the elements used in navigating (2.5.3, Level AAA) content hierarchy. | Summary: Users can view (2.5.1, Level AA), navigate (2.5.2, Level A), and configure the elements used in navigating (2.5.3, Level AAA) content hierarchy. | |
| 2.5.1 | 169 | 02.05.01 | h3 | Show Location in Hierarchy | When the user agent is presenting hierarchical information, but the hierarchy is not reflected in a standardized fashion in the DOM or platform accessibility services, the user can view the path of nodes leading from the root of the hierarchy to a specified element. | AA | 2.5.1 Show Location in Hierarchy: When the user agent is presenting hierarchical information, but the hierarchy is not reflected in a standardized fashion in the DOM or platform accessibility services, the user can view the path of nodes leading from the root of the hierarchy to a specified element. (Level AA) |
| 2.5.2 | 170 | 02.05.02 | h3 | Provide Structural Navigation by Heading and within Tables | The user agent provides at least the following types of structural navigation, where the structure types are recognized: | AA | 2.5.2 Provide Structural Navigation by Heading and within Tables: The user agent provides at least the following types of structural navigation, where the structure types are recognized: (Level AA) |
| 2.5.2.1 | 171 | 02.05.02.01 | h4 | Provide Structural Navigation by Heading and within Tables | By heading | AA | * By heading |
| 2.5.2.2 | 172 | 02.05.02.02 | h4 | Provide Structural Navigation by Heading and within Tables | By content sections | AA | * By content sections |
| 2.5.2.3 | 173 | 02.05.02.03 | h4 | Provide Structural Navigation by Heading and within Tables | Within tables | AA | * Within tables |
| 2.5.3 | 174 | 02.05.03 | h3 | Configure Structural Navigation and Views | The user can configure which elements are used for structural navigation and outline views. | AAA | 2.5.3 Configure Structural Navigation and Views: The user can configure which elements are used for structural navigation and outline views. (Level AAA) |
| 2.6 | 175 | 02.06 | h2 | Provide access to event handlers | Provide access to event handlers | Guideline 2.6 - Provide access to event handlers | |
| 2.6-N1 | 176 | 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 each element and activate an element's events individually (2.6.1). | Summary: Users can interact with web content by mouse, keyboard, voice input, gesture, or a combination of input methods. Users can discover what event handlers (e.g. onmouseover) are available at each element and activate an element's events individually (2.6.1). | |
| 2.6.1 | 177 | 02.06.01 | h3 | Allow Access and Activation of Input Methods | The user agent provides a means for the user to determine recognized input methods explicitly associated with an element, and a means for the user to activate those methods in a modality independent manner. | AA | 2.6.1 Allow Access and Activation of Input Methods: The user agent provides a means for the user to determine recognized input methods explicitly associated with an element, and a means for the user to activate those methods in a modality independent manner. (Level AA) |
| 2.7 | 178 | 02.07 | h2 | Configure and store preference settings | Configure and store preference settings | Guideline 2.7 - Configure and store preference settings | |
| 2.7-N1 | 179 | 02.07-N01 | note | Configure and store preference settings | Summary: Users can restore preference settings to default (2.7.2, Level A), and accessibility settings persist between sessions (2.7.1, Level A). Users can manage multiple sets of preference settings (2.7.3, Level AA), and adjust preference settings outside the user interface so the current user interface does not prevent access (2.7.4, Level AA), and transport settings to compatible systems (2.7.5, Level AA). | Summary: Users can restore preference settings to default (2.7.2, Level A), and accessibility settings persist between sessions (2.7.1, Level A). Users can manage multiple sets of preference settings (2.7.3, Level AA), and adjust preference settings outside the user interface so the current user interface does not prevent access (2.7.4, Level AA), and transport settings to compatible systems (2.7.5, Level AA). | |
| 2.7.1 | 180 | 02.07.01 | h3 | Allow Persistent Accessibility Settings | User agent accessibility preference settings persist between sessions. | A | 2.7.1 Allow Persistent Accessibility Settings: User agent accessibility preference settings persist between sessions. (Level A) |
| 2.7.1-N1 | 181 | 02.07.01-N01 | note | Allow Persistent Accessibility Settings | User agents may have a public access setting that turns this off. | Note: User agents may have a public access setting that turns this off. | |
| 2.7.2 | 182 | 02.07.02 | h3 | Allow Restore All to Default | The user can restore all preference settings to default values. | A | 2.7.2 Allow Restore All to Default: The user can restore all preference settings to default values. (Level A) |
| 2.7.3 | 183 | 02.07.03 | h3 | Allow Multiple Sets of Preference Settings | The user can save and retrieve multiple sets of user agent preference settings. | AA | 2.7.3 Allow Multiple Sets of Preference Settings: The user can save and retrieve multiple sets of user agent preference settings. (Level AA) |
| 2.7.4 | 184 | 02.07.04 | h3 | Allow Preference Changes from outside the User Interface | The user can adjust any preference settings required to meet the User Agent Accessibility Guidelines (UAAG) 2.0 from outside the UA user interface. | AAA | 2.7.4 Allow Preference Changes from outside the User Interface: The user can adjust any preference settings required to meet the User Agent Accessibility Guidelines (UAAG) 2.0 from outside the UA user interface. (Level AAA) |
| 2.7.5 | 185 | 02.07.05 | h3 | Make Preference Settings Transferable | The user can transfer all compatible user agent preference settings between devices. | AAA | 2.7.5 Make Preference Settings Transferable: The user can transfer all compatible user agent preference settings between devices. (Level AAA) |
| 2.8 | 186 | 02.08 | h2 | Customize display of graphical controls | Customize display of graphical controls | Guideline 2.8 - Customize display of graphical controls | |
| 2.8-N1 | 187 | 02.08-N01 | note | Customize display of graphical controls | Summary: It's recommended that users can add, remove, reposition, and assign shortcuts to user agent controls, and restore them to their default settings (2.8.1, Level AA). | Summary: It's recommended that users can add, remove, reposition, and assign shortcuts to user agent controls, and restore them to their default settings (2.8.1, Level AA). | |
| 2.8.1 | 188 | 02.08.01 | h3 | Customize Display of Controls for User Interface Commands, Functions, and Extensions | The user can customize which user agent commands, functions, and extensions are displayed within the user agent user interface as follows: | AA | 2.8.1 Customize Display of Controls for User Interface Commands, Functions, and Extensions: The user can customize which user agent commands, functions, and extensions are displayed within the user agent user interface as follows: (Level AA) |
| 2.8.1.1 | 189 | 02.08.01.01 | h4 | Customize Display of Controls for User Interface Commands, Functions, and Extensions | Show: The user can choose to display any controls available within the user agent user interface, including user-installed extensions. It is acceptable to limit the total number of controls that are displayed onscreen. | AA | * Show: The user can choose to display any controls available within the user agent user interface, including user-installed extensions. It is acceptable to limit the total number of controls that are displayed onscreen. |
| 2.8.1.2 | 190 | 02.08.01.02 | h4 | Customize Display of Controls for User Interface Commands, Functions, and Extensions | Simplify: The user can simplify the default user interface by choosing to display only commands essential for basic operation (e.g. by hiding some controls). | AA | * Simplify: The user can simplify the default user interface by choosing to display only commands essential for basic operation (e.g. by hiding some controls). |
| 2.8.1.3 | 191 | 02.08.01.03 | h4 | Customize Display of Controls for User Interface Commands, Functions, and Extensions | Reposition: The user can choose to reposition individual controls within containers (e.g. toolbars or tool palettes), as well as reposition the containers themselves to facilitate physical access (e.g. to minimize hand travel on touch screens, or to facilitate preferred hand access on handheld mobile devices). | AA | * Reposition: The user can choose to reposition individual controls within containers (e.g. toolbars or tool palettes), as well as reposition the containers themselves to facilitate physical access (e.g. to minimize hand travel on touch screens, or to facilitate preferred hand access on handheld mobile devices). |
| 2.8.1.4 | 192 | 02.08.01.04 | h4 | Customize Display of Controls for User Interface Commands, Functions, and Extensions | Assign Activation Keystrokes or Gestures: The user can choose to view, assign or change default keystrokes or gestures used to activate controls. | AA | * Assign Activation Keystrokes or Gestures: The user can choose to view, assign or change default keystrokes or gestures used to activate controls. |
| 2.8.1.5 | 193 | 02.08.01.05 | h4 | Customize Display of Controls for User Interface Commands, Functions, and Extensions | Reset: The user has the option to reset the containers and controls to their default configuration. | AA | * Reset: The user has the option to reset the containers and controls to their default configuration. |
| 2.9 | 194 | 02.09 | h2 | Allow time-independent interaction | Allow time-independent interaction | Guideline 2.9 - Allow time-independent interaction | |
| 2.9-N1 | 195 | 02.09-N01 | note | Allow time-independent interaction | Summary: Users can extend the time limits for user input when such limits are controllable by the user agent (2.9.1, Level A). | Summary: Users can extend the time limits for user input when such limits are controllable by the user agent (2.9.1, Level A). | |
| 2.9.1 | 196 | 02.09.01 | h3 | Adjustable Time Limits | The UA user interface does not include time limits or at least one of the following is true: | A | 2.9.1 Adjustable Time Limits: The UA user interface does not include time limits or at least one of the following is true: (Level A) |
| 2.9.1.a | 197 | 02.09.01.A | h4 | Adjustable Time Limits | Turn Off: Users are allowed to turn off the time limit before encountering it; or | A | (a) Turn Off: Users are allowed to turn off the time limit before encountering it; or |
| 2.9.1.b | 198 | 02.09.01.B | h4 | Adjustable Time Limits | Adjust: Users are allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or | A | (b) Adjust: Users are allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or |
| 2.9.1.c | 199 | 02.09.01.C | h4 | Adjustable Time Limits | Extend: Users are warned before time expires and given at least 20 seconds to extend the time limit with a simple action (e.g. "press the space bar"), and users are allowed to extend the time limit at least ten times; or | A | (c) Extend: Users are warned before time expires and given at least 20 seconds to extend the time limit with a simple action (e.g. "press the space bar"), and users are allowed to extend the time limit at least ten times; or |
| 2.9.1.d | 200 | 02.09.01.D | h4 | Adjustable Time Limits | Real-time Exception: The time limit is a required part of a real-time event and no alternative to the time limit is possible; or | A | (d) Real-time Exception: The time limit is a required part of a real-time event and no alternative to the time limit is possible; or |
| 2.9.1.e | 201 | 02.09.01.E | h4 | Adjustable Time Limits | Essential Exception: The time limit is essential and extending it would invalidate the activity; or | A | (e) Essential Exception: The time limit is essential and extending it would invalidate the activity; or |
| 2.9.1.f | 202 | 02.09.01.F | h4 | Adjustable Time Limits | 20 Hour Exception: The time limit is longer than 20 hours. | A | (f) 20 Hour Exception: The time limit is longer than 20 hours. |
| 2.10 | 203 | 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 | 204 | 02.10-N01 | note | Help users avoid flashing that could cause seizures | Summary: To help users avoid seizures, the default configuration prevents the browser user interface from flashing more than three times a second above luminescence or color thresholds (2.10.1, Level A), or even below the thresholds (2.10.2, Level AAA). | Summary: To help users avoid seizures, the default configuration prevents the browser user interface from flashing more than three times a second above luminescence or color thresholds (2.10.1, Level A), or even below the thresholds (2.10.2, Level AAA). | |
| 2.10.1 | 205 | 02.10.01 | h3 | Three Flashes or Below Threshold | In its default configuration, the user agent does not display any user interface components that flashes more than three times in any one-second period, unless the flash is below 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 that flashes more than three times in any one-second period, unless the flash is below general flash and red flash thresholds. (Level A) |
| 2.10.2 | 206 | 02.10.02 | h3 | Three Flashes | In its default configuration, the user agent does not display any user interface components 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 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 | 207 | 02.11 | h2 | Provide control of time-based media | Provide control of time-based media | Guideline 2.11 - Provide control of time-based media | |
| 2.11-N1 | 208 | 02.11-N01 | note | Provide control of time-based media | Summary: The user can present placeholders for time-based media (2.11.1, Level A) and executable regions (2.11.2, Level A), or block all executable content (2.11.3, Level A), adjust playback (2.11.4, Level A), stop/pause/resume (2.11.5, Level A), navigate by time (2.11.6, Level A) or semantic structures such as chapter (2.11.7, Level AA). It is recommended that the user can adjust contrast and brightness of visual time-based media (2.11.8, Level AAA). Enable or disable tracks is included in 1.1.1 Render Alternative Content. | Summary: The user can present placeholders for time-based media (2.11.1, Level A) and executable regions (2.11.2, Level A), or block all executable content (2.11.3, Level A), adjust playback (2.11.4, Level A), stop/pause/resume (2.11.5, Level A), navigate by time (2.11.6, Level A) or semantic structures such as chapter (2.11.7, Level AA). It is recommended that the user can adjust contrast and brightness of visual time-based media (2.11.8, Level AAA). Enable or disable tracks is included in 1.1.1 Render Alternative Content. | |
| 2.11.1 | 209 | 02.11.01 | h3 | Time-Based Media Load-Only | The user can override the play on load of recognized time-based media content such that the content is not played until explicit user request. | A | 2.11.1 Time-Based Media Load-Only: The user can override the play on load of recognized time-based media content such that the content is not played until explicit user request. (Level A) |
| 2.11.2 | 210 | 02.11.02 | h3 | Execution Placeholder | The user can request 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.2 Execution Placeholder: The user can request 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.3 | 211 | 02.11.03 | h3 | Execution Toggle | The user can turn on/off the execution of dynamic or executable content (e.g. Javascript, canvas, media). | A | 2.11.3 Execution Toggle: The user can turn on/off the execution of dynamic or executable content (e.g. Javascript, canvas, media). (Level A) |
| 2.11.4 | 212 | 02.11.04 | h3 | Adjustable Playback Rate for Prerecorded Content | The user can adjust the playback rate of prerecorded time-based media content, such that all of the following are true: | AA | 2.11.4 Adjustable Playback Rate 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 AA) |
| 2.11.4.1 | 213 | 02.11.04.01 | h4 | Adjustable Playback Rate for Prerecorded Content | Playback Rate: The user can adjust the playback rate of the time-based media tracks to between 50% and 250% of real time. | AA | * Playback Rate: The user can adjust the playback rate of the time-based media tracks to between 50% and 250% of real time. |
| 2.11.4.2 | 214 | 02.11.04.02 | h4 | Adjustable Playback Rate for Prerecorded Content | Pitch: Speech whose playback rate has been adjusted by the user maintains pitch in order to limit degradation of the speech quality. | AA | * Pitch: Speech whose playback rate has been adjusted by the user maintains pitch in order to limit degradation of the speech quality. |
| 2.11.4.3 | 215 | 02.11.04.03 | h4 | Adjustable Playback Rate for Prerecorded Content | Synchronization: Audio and video tracks remain synchronized across this required range of playback rates. | AA | * Synchronization: Audio and video tracks remain synchronized across this required range of playback rates. |
| 2.11.4.4 | 216 | 02.11.04.04 | h4 | Adjustable Playback Rate for Prerecorded Content | Reset: The user agent provides a function that resets the playback rate to normal (100%). | AA | * Reset: The user agent provides a function that resets the playback rate to normal (100%). |
| 2.11.5 | 217 | 02.11.05 | h3 | Stop/Pause/Resume Time-Based Media | The user can stop, pause, and resume rendered audio and animation content (e.g video, animation, changing text) that lasts three or more seconds at the default playback rate. | A | 2.11.5 Stop/Pause/Resume Time-Based Media: The user can stop, pause, and resume rendered audio and animation content (e.g video, animation, changing text) that lasts three or more seconds at the default playback rate. (Level A) |
| 2.11.6 | 218 | 02.11.06 | h3 | Navigation of Time-Based media by Time | If time-based media lasts three or more seconds at the default playback rate, the user can navigate it using a continuous scale and by relative time units. | A | 2.11.6 Navigation of Time-Based media by Time: If time-based media lasts three or more seconds at the default playback rate, the user can navigate it using a continuous scale and by relative time units. (Level A) |
| 2.11.7 | 219 | 02.11.07 | h3 | Navigation of Time-Based Media by Semantics | 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.7 Navigation of Time-Based Media by Semantics: 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.8 | 220 | 02.11.08 | h3 | Video Contrast and Brightness | Users can adjust the contrast and brightness of visual time-based media. | AAA | 2.11.8 Video Contrast and Brightness: Users can adjust the contrast and brightness of visual time-based media. (Level AAA) |
| 2.12 | 221 | 02.12 | h2 | Support other input devices | Support other input devices | Guideline 2.12 - Support other input devices | |
| 2.12-N1 | 222 | 02.12-N01 | note | Support other input devices | Summary: User agents support all of the platform text input devices (2.12.1, Level A), and for all input devices the user can input text (2.12.3, Level AAA) and perform all other functions (2.12.2, Level AA). | Summary: User agents support all of the platform text input devices (2.12.1, Level A), and for all input devices the user can input text (2.12.3, Level AAA) and perform all other functions (2.12.2, Level AA). | |
| 2.12.1 | 223 | 02.12.01 | h3 | 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 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 | 224 | 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 | 225 | 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 | 226 | 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 | 227 | 03.01 | h2 | Help users avoid and correct mistakes | Help users avoid and correct mistakes | Guideline 3.1 - Help users avoid and correct mistakes | |
| 3.1-N1 | 228 | 03.01-N01 | note | Help users avoid and correct mistakes | Summary: Users can undo text entry (3.1.1, Level A), avoid or undo settings changes (3.1.2, Level A), and receive indications of progress activity (3.1.3, Level A). It is recommended that users can have their text checked for spelling errors (3.1.4, Level AA), go back after navigating (3.1.5, Level AA), have form submissions require confirmation (3.1.6, Level AA), have auto-form fill of basic information (3.1.7, Level AA), and save form entry data with a local save (3.1.8, Level AA). | Summary: Users can undo text entry (3.1.1, Level A), avoid or undo settings changes (3.1.2, Level A), and receive indications of progress activity (3.1.3, Level A). It is recommended that users can have their text checked for spelling errors (3.1.4, Level AA), go back after navigating (3.1.5, Level AA), have form submissions require confirmation (3.1.6, Level AA), have auto-form fill of basic information (3.1.7, Level AA), and save form entry data with a local save (3.1.8, Level AA). | |
| 3.1.1 | 229 | 03.01.01 | h3 | Text Entry Undo | The user can reverse recognized text entry actions prior to submission. | A | 3.1.1 Text Entry Undo: The user can reverse recognized text entry actions prior to submission. (Level A) |
| 3.1.1-N1 | 230 | 03.01.01-N01 | note | Text Entry Undo | Submission can be triggered in many different ways, such as clicking a submit button, typing a key in a control with an onkeypress event, or by a script responding to a timer. | Note: Submission can be triggered in many different ways, such as clicking a submit button, typing a key in a control with an onkeypress event, or by a script responding to a timer. | |
| 3.1.2 | 231 | 03.01.02 | h3 | Settings Changes can be Reversed or Confirmed | If the user agent provides mechanisms for changing its user interface settings, it either allows the user to reverse the setting changes, or the user can require user confirmation to proceed. | A | 3.1.2 Settings Changes can be Reversed or Confirmed: If the user agent provides mechanisms for changing its user interface settings, it either allows the user to reverse the setting changes, or the user can require user confirmation to proceed. (Level A) |
| 3.1.3 | 232 | 03.01.03 | h3 | Retrieval Progress | By default, the user agent shows the state of content retrieval activity. | A | 3.1.3 Retrieval Progress: By default, the user agent shows the state of content retrieval activity. (Level A) |
| 3.1.4 | 233 | 03.01.04 | h3 | Spell Check | The user can have spelling assistance for editable text in rendered content.. | AA | 3.1.4 Spell Check: The user can have spelling assistance for editable text in rendered content.. (Level AA) |
| 3.1.5 | 234 | 03.01.05 | h3 | Back Button | The user can reverse recognized navigation between web addresses (e.g. standard "back button" functionality). | AA | 3.1.5 Back Button: The user can reverse recognized navigation between web addresses (e.g. standard "back button" functionality). (Level AA) |
| 3.1.6 | 235 | 03.01.06 | h3 | Form Submission Confirm | The user can specify whether or not recognized form submissions must be confirmed. | AA | 3.1.6 Form Submission Confirm: The user can specify whether or not recognized form submissions must be confirmed. (Level AA) |
| 3.1.7 | 236 | 03.01.07 | h3 | Form Auto-Fill | The user can have the following information stored and used to auto-fill form fields by request: | AA | 3.1.7 Form Auto-Fill: The user can have the following information stored and used to auto-fill form fields by request: (Level AA) |
| 3.1.7.a | 237 | 03.01.07.A | h4 | Form Auto-Fill | user's name | AA | (a) user's name |
| 3.1.7.b | 238 | 03.01.07.B | h4 | Form Auto-Fill | user's email address | AA | (b) user's email address |
| 3.1.7.c | 239 | 03.01.07.C | h4 | Form Auto-Fill | user's phone number | AA | (c) user's phone number |
| 3.1.8 | 240 | 03.01.08 | h3 | Save Form Entries | If the user agent provides a feature to save local versions of web content, then any form fields the user has filled retain any entries in the saved version. | AA | 3.1.8 Save Form Entries: If the user agent provides a feature to save local versions of web content, then any form fields the user has filled retain any entries in the saved version. (Level AA) |
| 3.2 | 241 | 03.02 | h2 | Document the user agent user interface including accessibility features | Document the user agent user interface including accessibility features | Guideline 3.2 - Document the user agent user interface including accessibility features | |
| 3.2-N1 | 242 | 03.02-N01 | note | Document the user agent user interface including accessibility features | Summary: User documentation is available in an accessible format (3.2.1, Level A), it includes accessibility features (3.2.2, Level A), it documents all the user features (3.2.3, Level AA), it delineates differences between versions (3.2.4, Level AA), and provides a centralized view of conformance UAAG2.0 (3.2.5, Level AAA). | Summary: User documentation is available in an accessible format (3.2.1, Level A), it includes accessibility features (3.2.2, Level A), it documents all the user features (3.2.3, Level AA), it delineates differences between versions (3.2.4, Level AA), and provides a centralized view of conformance UAAG2.0 (3.2.5, Level AAA). | |
| 3.2.1 | 243 | 03.02.01 | h3 | Accessible Documentation | Product documentation is available in a format that meets success criteria of WCAG 2.0 level "A" or greater. | A | 3.2.1 Accessible Documentation: Product documentation is available in a format that meets success criteria of WCAG 2.0 level "A" or greater. (Level A) |
| 3.2.2 | 244 | 03.02.02 | h3 | Describe Accessibility Features | For each user agent feature that is used to meet UAAG 2.0, at least one of the following is true: | A | 3.2.2 Describe Accessibility Features: For each user agent feature that is used to meet UAAG 2.0, at least one of the following is true: (Level A) |
| 3.2.2.a | 245 | 03.02.02.A | h4 | Describe Accessibility Features | Described in the Documentation: Use of the feature is explained in the user agent's documentation; or | A | (a) Described in the Documentation: Use of the feature is explained in the user agent's documentation; or |
| 3.2.2.b | 246 | 03.02.02.B | h4 | Describe Accessibility Features | Described in the Interface: Use of the feature is explained in the UA user interface; or | A | (b) Described in the Interface: Use of the feature is explained in the UA user interface; or |
| 3.2.2.c | 247 | 03.02.02.C | h4 | Describe Accessibility Features | Platform Service: The feature is a service provided by an underlying platform; or | A | (c) Platform Service: The feature is a service provided by an underlying platform; or |
| 3.2.2.d | 248 | 03.02.02.D | h4 | Describe Accessibility Features | Not Used by Users: The feature is not used directly by users (e.g., passing information to a platform accessibility service). | A | (d) Not Used by Users: The feature is not used directly by users (e.g., passing information to a platform accessibility service). |
| 3.2.3 | 249 | 03.02.03 | h3 | Document All Features | For each user agent feature, at least one of the following is true: | AA | 3.2.3 Document All Features: For each user agent feature, at least one of the following is true: (Level AA) |
| 3.2.3.a | 250 | 03.02.03.A | h4 | Document All Features | Described in the Documentation: Use of the feature is explained in the user agent's documentation; or | AA | (a) Described in the Documentation: Use of the feature is explained in the user agent's documentation; or |
| 3.2.3.b | 251 | 03.02.03.B | h4 | Document All Features | Described in the Interface: Use of the feature is explained in the UA user interface; or | AA | (b) Described in the Interface: Use of the feature is explained in the UA user interface; or |
| 3.2.3.c | 252 | 03.02.03.C | h4 | Document All Features | Platform Service: The feature is a service provided by an underlying platform; or | AA | (c) Platform Service: The feature is a service provided by an underlying platform; or |
| 3.2.3.d | 253 | 03.02.03.D | h4 | Document All Features | Not Used by Users: The feature is not used directly by users (e.g., passing information to a platform accessibility service). | AA | (d) Not Used by Users: The feature is not used directly by users (e.g., passing information to a platform accessibility service). |
| 3.2.4 | 254 | 03.02.04 | h3 | Changes Between Versions | Changes to features that meet UAAG 2.0 success criteria since the previous user agent release are documented. | AA | 3.2.4 Changes Between Versions: Changes to features that meet UAAG 2.0 success criteria since the previous user agent release are documented. (Level AA) |
| 3.2.5 | 255 | 03.02.05 | 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.2.5 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.3 | 256 | 03.03 | h2 | Make the user agent behave in predictable ways | Make the user agent behave in predictable ways | Guideline 3.3 - Make the user agent behave in predictable ways | |
| 3.3-N1 | 257 | 03.03-N01 | note | Make the user agent behave in predictable ways | Summary: Users can prevent non-requested focus changes (3.3.1, Level A). | Summary: Users can prevent non-requested focus changes (3.3.1, Level A). | |
| 3.3.1 | 258 | 03.03.01 | h3 | Avoid Unpredictable Focus | The user can prevent focus changes that are not a result of explicit user request. | A | 3.3.1 Avoid Unpredictable Focus: The user can prevent focus changes that are not a result of explicit user request. (Level A) |
| 4 | 259 | 04 | h1 | Facilitate programmatic access | Facilitate programmatic access | PRINCIPLE 4: Facilitate programmatic access | |
| 4.1 | 260 | 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 | 261 | 04.01-N01 | note | Facilitate programmatic access to assistive technology | Summary: The user agent supports platform accessibility services (4.1.1, Level A) that are quick and responsive (4.1.7, Level A), including providing information about all controls and operation (4.1.2, Level A & 4.1.6, Level AA), access to DOMs (4.1.4, Level A). Controls can be adjusted programmatically (4.1.5, Level A). 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, Level A). | Summary: The user agent supports platform accessibility services (4.1.1, Level A) that are quick and responsive (4.1.7, Level A), including providing information about all controls and operation (4.1.2, Level A & 4.1.6, Level AA), access to DOMs (4.1.4, Level A). Controls can be adjusted programmatically (4.1.5, Level A). 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, Level A). | |
| 4.1-N2 | 262 | 04.01-N02 | note | Facilitate programmatic access to assistive technology | UAAG 2.0 assumes that a platform accessibility API will be built on top of underlying security architectures that will allow user agents to comply with both the success criteria and security needs. | Note: UAAG 2.0 assumes that a platform accessibility API will be built on top of underlying security architectures that will allow user agents to comply with both the success criteria and security needs. | |
| 4.1.1 | 263 | 04.01.01 | h3 | Support Platform Accessibility Services | The user agent supports relevant platform accessibility services. | A | 4.1.1 Support Platform Accessibility Services: The user agent supports relevant platform accessibility services. (Level A) |
| 4.1.2 | 264 | 04.01.02 | h3 | Expose Basic Properties | For all user interface components, including UA user interface, rendered content, and generated content, the user agent makes available the following via a platform accessibility service: | A | 4.1.2 Expose Basic Properties: For all user interface components, including UA user interface, rendered content, and generated content, the user agent makes available the following via a platform accessibility service: (Level A) |
| 4.1.2.1 | 265 | 04.01.02.01 | h4 | Expose Basic Properties | Name | A | * Name |
| 4.1.2.2 | 266 | 04.01.02.02 | h4 | Expose Basic Properties | Role | A | * Role |
| 4.1.2.3 | 267 | 04.01.02.03 | h4 | Expose Basic Properties | State | A | * State |
| 4.1.2.4 | 268 | 04.01.02.04 | h4 | Expose Basic Properties | Value | A | * Value |
| 4.1.2.5 | 269 | 04.01.02.05 | h4 | Expose Basic Properties | Selection | A | * Selection |
| 4.1.2.6 | 270 | 04.01.02.06 | h4 | Expose Basic Properties | Focus | A | * Focus |
| 4.1.3 | 271 | 04.01.03 | h3 | Provide Equivalent Accessible Alternatives | If a component of the UA user interface cannot be exposed through platform accessibility services, then the user agent provides an equivalent alternative that is exposed through the platform accessibility service. | A | 4.1.3 Provide Equivalent Accessible Alternatives: If a component of the UA user interface cannot be exposed through platform accessibility services, then the user agent provides an equivalent alternative that is exposed through the platform accessibility service. (Level A) |
| 4.1.4 | 272 | 04.01.04 | h3 | Make DOMs Programmatically Available | If the user agent implements one or more Document Object Models (DOM), they must be made programmatically available to assistive technologies. | A | 4.1.4 Make DOMs Programmatically Available: If the user agent implements one or more Document Object Models (DOM), they must be made programmatically available to assistive technologies. (Level A) |
| 4.1.5 | 273 | 04.01.05 | h3 | Make Write Access Programmatically Available | 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 programmatically available. | A | 4.1.5 Make Write Access Programmatically Available: 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 programmatically available. (Level A) |
| 4.1.6 | 274 | 04.01.06 | h3 | Expose Additional Properties | For all user interface components, including the UA user interface, rendered content, and generated content, the user agent makes available the following, via a platform accessibility service, if the properties are supported by the service: | AA | 4.1.6 Expose Additional Properties: For all user interface components, including the UA user interface, rendered content, and generated content, the user agent makes available the following, via a platform accessibility service, if the properties are supported by the service: (Level AA) |
| 4.1.6.1 | 275 | 04.01.06.01 | h4 | Expose Additional Properties | Bounding dimensions and coordinates | AA | * Bounding dimensions and coordinates |
| 4.1.6.2 | 276 | 04.01.06.02 | h4 | Expose Additional Properties | Font family of text | AA | * Font family of text |
| 4.1.6.3 | 277 | 04.01.06.03 | h4 | Expose Additional Properties | Font size of text | AA | * Font size of text |
| 4.1.6.4 | 278 | 04.01.06.04 | h4 | Expose Additional Properties | Foreground and background color for text | AA | * Foreground and background color for text |
| 4.1.6.5 | 279 | 04.01.06.05 | h4 | Expose Additional Properties | Change state/value notifications | AA | * Change state/value notifications |
| 4.1.6.6 | 280 | 04.01.06.06 | h4 | Expose Additional Properties | Highlighting | AA | * Highlighting |
| 4.1.6.7 | 281 | 04.01.06.07 | h4 | Expose Additional Properties | Keyboard commands | AA | * Keyboard commands |
| 5 | 282 | 05 | h1 | Comply with applicable specifications and conventions | Comply with applicable specifications and conventions | PRINCIPLE 5: Comply with applicable specifications and conventions | |
| 5.1 | 283 | 05.01 | h2 | Comply with applicable specifications and conventions | Comply with applicable specifications and conventions | Guideline 5.1 - Comply with applicable specifications and conventions | |
| 5.1-N1 | 284 | 05.01-N01 | note | Comply with applicable specifications and conventions | Summary: When the browser's controls are authored in HTML or similar standards, they need to meet W3C's Web Content Accessibility Guidelines (5.1.1, Levels A, AA, AAA). The user agent supports the accessibility features of content formats (5.1.2, Level A) and of the platform (5.1.3, Level A), allows handling of unrendered technologies (5.1.4, Level A), allows alternative viewers (5.1.5, Level AA), and allows users to report accessibility issues (5.1.6, Level AAA). | Summary: When the browser's controls are authored in HTML or similar standards, they need to meet W3C's Web Content Accessibility Guidelines (5.1.1, Levels A, AA, AAA). The user agent supports the accessibility features of content formats (5.1.2, Level A) and of the platform (5.1.3, Level A), allows handling of unrendered technologies (5.1.4, Level A), allows alternative viewers (5.1.5, Level AA), and allows users to report accessibility issues (5.1.6, Level AAA). | |
| 5.1.1 | 285 | 05.01.01 | h3 | Comply with WCAG | Web-based UA user interfaces meet the WCAG 2.0 success criteria. | A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; and Level AAA to meet WCAG 2.0 Level A, AA, and AAA success criteria | 5.1.1 Comply with WCAG: Web-based UA user interfaces meet the WCAG 2.0 success criteria. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; and Level AAA to meet WCAG 2.0 Level A, AA, and AAA success criteria) |
| 5.1.1-N1 | 286 | 05.01.01-N01 | note | Comply with WCAG | This success criterion does not apply to non-web-based UA user interfaces, but does include any parts of non-web-based user agents that are web-based (e.g. help systems). However, it is recommended that developers of non-web-based user agent user interfaces follow the Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) . | Note: This success criterion does not apply to non-web-based UA user interfaces, but does include any parts of non-web-based user agents that are web-based (e.g. help systems). However, it is recommended that developers of non-web-based user agent user interfaces follow the Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) . | |
| 5.1.2 | 287 | 05.01.02 | h3 | Implement Accessibility Features of Content Specifications | Implement the accessibility features of content specifications. Accessibility features are those that are either * Identified as such in the content specifications or | A | 5.1.2 Implement Accessibility Features of Content Specifications: Implement the accessibility features of content specifications. Accessibility features are those that are either (Level A): * Identified as such in the content specifications or |
| 5.1.2.1 | 288 | 05.01.02.01 | h4 | Implement Accessibility Features of Content Specifications | Allow authors to satisfy a requirement of WCAG 2.0 | A | * Allow authors to satisfy a requirement of WCAG 2.0 |
| 5.1.2-N 1 | 289 | 05.01.02-N01 | note | Implement Accessibility Features of Content Specifications | If a conformance claim is filed, cite the implemented specifications in the conformance claim. | Note 1: If a conformance claim is filed, cite the implemented specifications in the conformance claim. | |
| 5.1.2-N 2 | 290 | 05.01.02-N02 | note | Implement Accessibility Features of Content Specifications | 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. | Note 2: 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. | |
| 5.1.3 | 291 | 05.01.03 | h3 | Implement Accessibility Features of the Platform | If the user agent contains non-web-based user interfaces, then those user interfaces follow user interface accessibility guidelines for the platform. | A | 5.1.3 Implement Accessibility Features of the Platform: If the user agent contains non-web-based user interfaces, then those user interfaces follow user interface accessibility guidelines for the platform. (Level A) |
| 5.1.3-N1 | 292 | 05.01.03-N01 | note | Implement Accessibility Features of the Platform | When a 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. | Note: When a 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. | |
| 5.1.5 | 293 | 05.01.05 | h3 | Allow Content Elements to be Rendered in Alternative Viewers | The user can select content elements and have them rendered in alternative viewers. | AA | 5.1.5 Allow Content Elements to be Rendered in Alternative Viewers: The user can select content elements and have them rendered in alternative viewers. (Level AA) |
| 5.1.6 | 294 | 05.01.06 | h3 | Enable Reporting of User Agent Accessibility Faults | The user agent provides a mechanism for users to report user agent accessibility issues. | AAA | 5.1.6 Enable Reporting of User Agent Accessibility Faults: The user agent provides a mechanism for users to report user agent accessibility issues. (Level AAA) |