WD-UAAG20-20131107 in Table Form

ID Line Number Canonical ID Type Title Text Priority Whole Line
0 0 00 h2 UAAG 2.0 Conformance Applicability Notes UAAG 2.0 Conformance Applicability Notes
0.1 1 00.01 h3 Recognized Content Only UAAG 2.0 success criteria only apply to web content and its behaviors that can be recognized by user agents. Recognized Content Only: UAAG 2.0 success criteria only apply to web content and its behaviors that can be recognized by user agents.
0.2 2 00.02 h3 Optional Settings Throughout UAAG 2.0, all required behaviors may be provided as optional preference settings unless a success criterion explicitly says otherwise. For example, if a success criteria requires high contrast between foreground text and its background, the user agent may also provide choices with low contrast. A required behavior does not need to be the default option unless the success criteria explicitly says otherwise. Optional Settings: Throughout UAAG 2.0, all required behaviors may be provided as optional preference settings unless a success criterion explicitly says otherwise. For example, if a success criteria requires high contrast between foreground text and its background, the user agent may also provide choices with low contrast. A required behavior does not need to be the default option unless the success criteria explicitly says otherwise.
0.3 3 00.03 h3 2119 language not used UAAG 2.0 does not use RFC 2119 language (must, may, should) because these are guidelines and not interoperable specifications. These words in UAAG 2.0 don't have the same sense as they do in RFC 2119. RFC 2119 language not used: UAAG 2.0 does not use RFC 2119 language (must, may, should) because these are guidelines and not interoperable specifications. These words in UAAG 2.0 don't have the same sense as they do in RFC 2119.
0.4 4 00.04 h2 Simultaneous satisfaction of success criteria Users can access all behaviors required by UAAG 2.0 at the same time (e.g. when the user resizes the viewport per 1.8.9, content is reflowed per 1.8.6), except where those behaviors are mutually exclusive. Simultaneous satisfaction of success criteria: Users can access all behaviors required by UAAG 2.0 at the same time (e.g. when the user resizes the viewport per 1.8.9, content is reflowed per 1.8.6), except where those behaviors are mutually exclusive.
1 5 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 6 01.01 h2 Provide access to alternative content Provide access to alternative content Guideline 1.1 - Provide access to alternative content
1.1-N1 7 01.01-N01 note Provide access to alternative content Summary: The user can choose to render any type of alternative content available. (1.1.1). The user can also choose at least one alternative such as alt text to be always displayed (1.1.3), but it's recommended that users also be able to specify a cascade (1.1.5), such as alt text if it's there, otherwise longdesc, otherwise filename, etc. It's recommended that the user can configure the caption text and that text or sign language alternative cannot obscure the video or the controls (1.1.4). 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). The user can also choose at least one alternative such as alt text to be always displayed (1.1.3), but it's recommended that users also be able to specify a cascade (1.1.5), such as alt text if it's there, otherwise longdesc, otherwise filename, etc. It's recommended that the user can configure the caption text and that text or sign language alternative cannot obscure the video or the controls (1.1.4). The user can configure the size and position of media alternatives (1.1.6).
1.1.1 8 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 9 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 10 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 11 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 12 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 13 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 14 01.01.05.01 h4 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 * Don't obscure controls: Displaying time-based media alternatives doesn't obscure recognized controls for the primary time-based media.
1.1.5.2 15 01.01.05.02 h4 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 * 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 16 01.01.05.03 h4 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 * 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 17 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 18 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 19 01.01.06.01 h4 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 * 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 20 01.01.06.02 h4 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 * 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 21 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 22 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 23 01.02 h2 Repair missing content Repair missing content Guideline 1.2 - Repair missing content
1.2-N1 24 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 25 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 26 01.02.01.01 h4 Support Repair by Assistive Technologies If text alternatives for non-text content are missing or empty then both of the following are true: 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 27 01.02.01.02 h4 Support Repair by Assistive Technologies If text alternatives for non-text content are missing or empty then both of the following are true: 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 28 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 29 01.02.02.01 h4 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 * Headers (e.g. heading markup, table headers)
1.3 30 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 31 01.03-N01 note Provide highlighting for selection, keyboard focus, enabled elements, visited links Summary: The user can visually distinguish selected, focused, and enabled items, and recently visited links (1.3.1), with a choice of highlighting options that at least include foreground and background colors, and border color and thickness (1.3.2). Summary: The user can visually distinguish selected, focused, and enabled items, and recently visited links (1.3.1), with a choice of highlighting options that at least include foreground and background colors, and border color and thickness (1.3.2).
1.3.1 32 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 33 01.03.01.01 h4 Highlighted Items The user can specify that the following classes be highlighted so that each is uniquely distinguished: A *  Selection
1.3.1.2 34 01.03.01.02 h4 Highlighted Items The user can specify that the following classes be highlighted so that each is uniquely distinguished: A * Active keyboard focus (indicated by focus cursors and/or text cursors)
1.3.1.3 35 01.03.01.03 h4 Highlighted Items The user can specify that the following classes be highlighted so that each is uniquely distinguished: A * Recognized enabled input elements (distinguished from disabled elements)
1.3.1.4 36 01.03.01.04 h4 Highlighted Items The user can specify that the following classes be highlighted so that each is uniquely distinguished: A * Recently visited links
1.3.2 37 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 38 01.03.02.01 h4 Highlighting Options When highlighting classes specified by 1.3.1 Highlighted Items, the user can specify highlighting options that include at least: AA * Foreground colors
1.3.2.2 39 01.03.02.02 h4 Highlighting Options When highlighting classes specified by 1.3.1 Highlighted Items, the user can specify highlighting options that include at least: AA * Background colors
1.3.2.3 40 01.03.02.03 h4 Highlighting Options When highlighting classes specified by 1.3.1 Highlighted Items, the user can specify highlighting options that include at least: AA * Borders (color, style, and thickness)
1.3.2.4 41 01.03.02.04 h4 Highlighting Options When highlighting classes specified by 1.3.1 Highlighted Items, the user can specify highlighting options that include at least: AA * Size when the indicator is an image
1.3.2.5 42 01.03.02.05 h4 Highlighting Options When highlighting classes specified by 1.3.1 Highlighted Items, the user can specify highlighting options that include at least: AA * Blink rate (where implemented)
1.4 43 01.04 h2 Provide text configuration Provide text configuration Guideline 1.4 - Provide text configuration
1.4-N1 44 01.04-N01 note Provide text configuration Summary: The user can set text scale, color, and font family globally (1.4.1, Level A); set text size, color, and font family for element types (1.4.2, Level AA); set line spacing, character spacing, word spacing, text style, and justification globally (1.4.3, Level AA); set text style, margins, and borders for elements (1.4.5, Level AAA); set line spacing, capitalization, hyphenation, margins, and borders globally (1.4.6, Level AAA); and print configured and reflowed text (1.4.4 Level AA). Summary: The user can set text scale, color, and font family globally (1.4.1, Level A); set text size, color, and font family for element types (1.4.2, Level AA); set line spacing, character spacing, word spacing, text style, and justification globally (1.4.3, Level AA); set text style, margins, and borders for elements (1.4.5, Level AAA); set line spacing, capitalization, hyphenation, margins, and borders globally (1.4.6, Level AAA); and print configured and reflowed text (1.4.4 Level AA).
1.4-N 1 45 01.04-N01 note Provide text configuration Success criteria 1.4.1, 1.4.3, and 1.4.6 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.6 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 46 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 47 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 48 01.04.01 h3 Text Scale, Color, Font (Globally) The user can globally set all of the following characteristics of visually rendered text content: A 1.4.1 Text Scale, Color, Font (Globally): The user can globally set all of the following characteristics of visually rendered text content: (Level A)
1.4.1.1 49 01.04.01.01 h4 Text Scale, Color, Font (Globally) The user can globally set all of the following characteristics of visually rendered text content: A * Text scale with preserved size distinctions (e.g. keeping headings proportional to main font)
1.4.1.2 50 01.04.01.02 h4 Text Scale, Color, Font (Globally) The user can globally set all of the following characteristics of visually rendered text content: A * Text color and background color, choosing from all platform color options
1.4.1.3 51 01.04.01.03 h4 Text Scale, Color, Font (Globally) The user can globally set all of the following characteristics of visually rendered text content: A * Font family, choosing from all platform fonts
1.4.2 52 01.04.02 h3 Text Size, Color and Font (by Element) The user can set all of the following characteristics of visually rendered text content for text element types including at least headings and input fields: AA 1.4.2 Text Size, Color and Font (by Element): The user can set all of the following characteristics of visually rendered text content for text element types including at least headings and input fields:(Level AA)
1.4.2.1 53 01.04.02.01 h4 Text Size, Color and Font (by Element) The user can set all of the following characteristics of visually rendered text content for text element types including at least headings and input fields: AA * Text size
1.4.2.2 54 01.04.02.02 h4 Text Size, Color and Font (by Element) The user can set all of the following characteristics of visually rendered text content for text element types including at least headings and input fields: AA * Text color and background color, choosing from all platform color options
1.4.2.3 55 01.04.02.03 h4 Text Size, Color and Font (by Element) The user can set all of the following characteristics of visually rendered text content for text element types including at least headings and input fields: AA * Font family, choosing from all platform fonts
1.4.3 56 01.04.03 h3 Text Spacing and Style (Globally) The user can globally set all of the following characteristics of visually rendered blocks of text: AA 1.4.3 Text Spacing and Style (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 Text Spacing and Style (Globally) The user can globally set all of the following characteristics of visually rendered blocks of text: AA * Line spacing of at least 1.0, 1.3, 1.5, and 2.0 times the font height
1.4.3.2 58 01.04.03.02 h4 Text Spacing and Style (Globally) The user can globally set all of the following characteristics of visually rendered blocks of text: AA * Character spacing of at least 0.01, 0.03, 0.06, 0.09 times the base character width
1.4.3.3 59 01.04.03.03 h4 Text Spacing and Style (Globally) The user can globally set all of the following characteristics of visually rendered blocks of text: AA * Word spacing of at least 0.01, 0.03, 0.06, 0.09 times the base character width
1.4.3.4 60 01.04.03.04 h4 Text Spacing and Style (Globally) The user can globally set all of the following characteristics of visually rendered blocks of text: AA * Text style (underline, italic, bold)
1.4.3.5 61 01.04.03.05 h4 Text Spacing and Style (Globally) The user can globally set all of the following characteristics of visually rendered blocks of text: AA * Justification (left, right, or full)
1.4.3-N1 62 01.04.03-N01 note Text Spacing and Style (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 63 01.04.04 h3 Configured and Reflowed Text Printing The user can print any rendered visual, non-time-based content to the user's choice of available printing devices. AA 1.4.4 Configured and Reflowed Text Printing: The user can print any rendered visual, non-time-based content to the user's choice of available printing devices. (Level AA)
1.4.4-N1 64 01.04.04-N01 note Configured and Reflowed Text Printing The user must be able to print content as it is rendered on screen, reflecting user scaling, highlighting, and other modifications, but reflowable content is reflowed for the print margins. Note: The user must be able to print content as it is rendered on screen, reflecting user scaling, highlighting, and other modifications, but reflowable content is reflowed for the print margins.
1.4.5 65 01.04.05 h3 Text Style, Margins, Borders (by Element) The user can set all of the following characteristics of visually rendered text content for main text and for text element types including at least headings and input fields: AAA 1.4.5 Text Style, Margins, Borders (by Element): The user can set all of the following characteristics of visually rendered text content for main text and for text element types including at least headings and input fields: (Level AAA)
1.4.5.1 66 01.04.05.01 h4 Text Style, Margins, Borders (by Element) The user can set all of the following characteristics of visually rendered text content for main text and for text element types including at least headings and input fields: AAA * Text style (underline, italic, bold)
1.4.5.2 67 01.04.05.02 h4 Text Style, Margins, Borders (by Element) The user can set all of the following characteristics of visually rendered text content for main text and for text element types including at least headings and input fields: AAA * Margins (for example, space above headings, indentation of lists)
1.4.5.3 68 01.04.05.03 h4 Text Style, Margins, Borders (by Element) The user can set all of the following characteristics of visually rendered text content for main text and for text element types including at least headings and input fields: AAA * Borders
1.4.6 69 01.04.06 h3 Spacing, Capitalization and Hyphenation (Globally) The user can globally set all of the following characteristics of visually rendered blocks of text: AAA 1.4.6 Spacing, Capitalization and Hyphenation (Globally): The user can globally set all of the following characteristics of visually rendered blocks of text: (Level AAA)
1.4.6.1 70 01.04.06.01 h4 Spacing, Capitalization and Hyphenation (Globally) The user can globally set all of the following characteristics of visually rendered blocks of text: AAA * Line spacing between 0.7 and 3.0 times the font height, at increments of 0.10
1.4.6.2 71 01.04.06.02 h4 Spacing, Capitalization and Hyphenation (Globally) The user can globally set all of the following characteristics of visually rendered blocks of text: AAA * Capitalization (overriding upper case and small caps style)
1.4.6.3 72 01.04.06.03 h4 Spacing, Capitalization and Hyphenation (Globally) The user can globally set all of the following characteristics of visually rendered blocks of text: AAA * Word-breaking properties (auto-hyphenation)
1.4.6.4 73 01.04.06.04 h4 Spacing, Capitalization and Hyphenation (Globally) The user can globally set all of the following characteristics of visually rendered blocks of text: AAA * Margins
1.4.6.5 74 01.04.06.05 h4 Spacing, Capitalization and Hyphenation (Globally) The user can globally set all of the following characteristics of visually rendered blocks of text: AAA * Borders
1.4.6-N1 75 01.04.06-N01 note Spacing, Capitalization and Hyphenation (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 76 01.05 h2 Provide volume configuration Provide volume configuration Guideline 1.5 - Provide volume configuration
1.5-N1 77 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 78 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 79 01.06 h2 Provide synthesized speech configuration Provide synthesized speech configuration Guideline 1.6 - Provide synthesized speech configuration
1.6-N1 80 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 81 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 82 01.06.01.01 h4 Speech Rate, Volume, and Voice If synthesized speech is produced, the user can specify the following: A * Speech rate
1.6.1.2 83 01.06.01.02 h4 Speech Rate, Volume, and Voice If synthesized speech is produced, the user can specify the following: A * Speech volume (independently of other sources of audio)
1.6.1.3 84 01.06.01.03 h4 Speech Rate, Volume, and Voice If synthesized speech is produced, the user can specify the following: A * Voice, when more than one voice is available
1.6.2 85 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 86 01.06.02.01 h4 Speech Pitch and Range If synthesized speech is produced, the user can specify the following if offered by the speech synthesizer: AA * Pitch (average frequency of the speaking voice)
1.6.2.2 87 01.06.02.02 h4 Speech Pitch and Range If synthesized speech is produced, the user can specify the following if offered by the speech synthesizer: AA * Pitch range (variation in average frequency)
1.6.2-N1 88 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 89 01.06.03 h3 Advanced Speech Characteristics The user can adjust all of the speech characteristics provided by the speech synthesizer. AAA 1.6.3 Advanced Speech Characteristics: The user can adjust all of the speech characteristics provided by the speech synthesizer. (Level AAA)
1.6.4 90 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 91 01.06.04.01 h4 Synthesized Speech Features If synthesized speech is produced, the following features are provided: AA * User-defined extensions to the synthesized speech dictionary.
1.6.4.2 92 01.06.04.02 h4 Synthesized Speech Features If synthesized speech is produced, the following features are provided: AA * "Spell-out": text is spelled one character at a time, or according to language-dependent pronunciation rules.
1.6.4.3 93 01.06.04.03 h4 Synthesized Speech Features If synthesized speech is produced, the following features are provided: 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 94 01.06.04.04 h4 Synthesized Speech Features If synthesized speech is produced, the following features are provided: AA * At least two ways of speaking punctuation: spoken literally, and with punctuation understood from speech characteristics like pauses.
1.6.5 95 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 96 01.07 h2 Enable configuration of user stylesheets Enable configuration of user stylesheets Guideline 1.7 - Enable configuration of user stylesheets
1.7-N1 97 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 98 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 99 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 100 01.07.02.01 h4 Apply User Stylesheets If user stylesheets are supported, then the user can enable or disable user stylesheets for: A * All pages on specified websites, or
1.7.2.2 101 01.07.02.02 h4 Apply User Stylesheets If user stylesheets are supported, then the user can enable or disable user stylesheets for: A * All pages
1.7.3 102 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 103 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 104 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 105 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.8, Level AA), keeping the focus within the viewport (1.8.2 & 1.8.6, Level A), resizing the viewport (1.8.9, 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.10, Level AA). The user can specify that all viewports have the same user interface elements (1.8.13, Level AA), if and how new viewports open (1.8.11, Level AA), and whether the new viewport automatically gets focus (1.8.12, Level AA). The user can mark items in a webpage and use shortcuts to navigate back to marked items. (1.8.14, 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.8, Level AA), keeping the focus within the viewport (1.8.2 & 1.8.6, Level A), resizing the viewport (1.8.9, 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.10, Level AA). The user can specify that all viewports have the same user interface elements (1.8.13, Level AA), if and how new viewports open (1.8.11, Level AA), and whether the new viewport automatically gets focus (1.8.12, Level AA). The user can mark items in a webpage and use shortcuts to navigate back to marked items. (1.8.14, Level AAA).
1.8.1 106 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 107 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 108 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 109 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 110 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 111 01.08.05.01 h4 Allow Zoom The user can rescale content within top-level graphical viewports as follows: A * Zoom in: to 500% or more of the default size
1.8.5.2 112 01.08.05.02 h4 Allow Zoom The user can rescale content within top-level graphical viewports as follows: 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 113 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 114 01.08.07 h3 Reflow Text The user can specify that text content in a graphical top-level viewport reflows so the text forms a single column that fits within the width of the viewport. A 1.8.7 Reflow Text: The user can specify that text content in a graphical top-level viewport reflows so the text forms a single column that fits within the width of the viewport. (Level A)
1.8.7-N 1 115 01.08.07-N01 note Reflow Text Reflow applies even when text is rescaled or zoomed. Note 1: Reflow applies even when text is rescaled or zoomed.
1.8.7-N 2 116 01.08.07-N02 note Reflow Text For vertical layout languages (e.g. Mongolian, Han), text should fit within the height of the viewport, rather than its width, to reduce vertical scrolling. Note 2: For vertical layout languages (e.g. Mongolian, Han), text should fit within the height of the viewport, rather than its width, to reduce vertical scrolling.
1.8.8 117 01.08.08 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.8 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.9 118 01.08.09 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.9 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.10 119 01.08.10 h3 Provide Viewport History For user 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 a restored point of regard, input focus and selection. AA 1.8.10 Provide Viewport History: For user 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 a restored point of regard, input focus and selection. (Level AA)
1.8.11 120 01.08.11 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.11 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.12 121 01.08.12 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.12 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.13 122 01.08.13 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.13 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.14 123 01.08.14 h3 Provide Webpage Bookmarks The user can mark items in a webpage, then use shortcuts to navigate back to marked items. The user can specify whether a navigation mark disappears after a session, or is persistent across sessions. AAA 1.8.14 Provide Webpage Bookmarks: The user can mark items in a webpage, then use shortcuts to navigate back to marked items. The user can specify whether a navigation mark disappears after a session, or is persistent across sessions. (Level AAA)
1.9 124 01.09 h2 Provide alternative views Provide alternative views Guideline 1.9 - Provide alternative views
1.9-N1 125 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 important elements. (1.9.1, Level AA). Summary: The user can view the source of content (1.9.2, Level AAA), and an outline view of important elements. (1.9.1, Level AA).
1.9.1 126 01.09.01 h3 Outline View Users can view a navigable outline of rendered content composed of labels for important elements, and can move focus efficiently to these elements in the main viewport. AA 1.9.1 Outline View: Users can view a navigable outline of rendered content composed of labels for important elements, and can move focus efficiently to these elements in the main viewport. (Level AA)
1.9.1-N1 127 01.09.01-N01 note Outline View The important elements depend on the web content technology, but may include headings, table captions, and content sections. Note: The important elements depend on the web content technology, but may include headings, table captions, and content sections.
1.9.2 128 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 129 01.10 h2 Provide element information Provide element information Guideline 1.10 - Provide element information
1.10-N1 130 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 131 01.10.01 h3 Show Related Elements The user can access related elements based on the user's position in content (e.g. show the label of a form control, show the headers of a table cell). AA 1.10.1 Show Related Elements: The user can access related elements based on the user's position in content (e.g. show the label of a form control, show the headers of a table cell). (Level AA)
1.10.2 132 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 133 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 134 02-N01 note Ensure that the user interface is operable 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 works best for a given situation. If every potential user task is made accessible via modality independent controls that any input technology can access, a user can use 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. See Independent User Interface: Events for additional information on APIs and techniques for modality independent controls. Note: 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 works best for a given situation. If every potential user task is made accessible via modality independent controls that any input technology can access, a user can use 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. See Independent User Interface: Events for additional information on APIs and techniques for modality independent controls.
2.1 135 02.01 h2 Ensure full keyboard access Ensure full keyboard access Guideline 2.1 - Ensure full keyboard access
2.1-N1 136 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 137 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 138 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 139 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 140 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 141 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 142 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 143 02.02 h2 Provide sequential navigation Provide sequential navigation Guideline 2.2 - Provide sequential navigation
2.2-N1 144 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 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 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 145 02.02.01 h3 Sequential Navigation Between Elements The user can move the keyboard focus backwards and forwards through all recognized enabled elements in the current viewport. A 2.2.1 Sequential Navigation Between Elements: The user can move the keyboard focus backwards and forwards through all recognized enabled elements in the current viewport. (Level A)
2.2.2 146 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 147 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 148 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 149 02.03 h2 Provide direct navigation and activation Provide direct navigation and activation Guideline 2.3 - Provide direct navigation and activation
2.3-N1 150 02.03-N01 note Provide direct navigation and activation Summary: Users can navigate directly (e.g. using keyboard shortcuts) to important elements (2.3.1, Level AA) with the option of immediate activation of the operable elements (2.3.3, Level A). Display commands with the elements to make it easier for users to discover the commands (2.3.2 & 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 important elements (2.3.1, Level AA) with the option of immediate activation of the operable elements (2.3.3, Level A). Display commands with the elements to make it easier for users to discover the commands (2.3.2 & 2.3.4, Level AA). The user can remap and save direct commands (2.3.5, Level AA).
2.3.1 151 02.03.01 h3 Allow Direct Navigation to Important Elements The user can navigate directly to important elements in rendered content. AA 2.3.1 Allow Direct Navigation to Important Elements: The user can navigate directly to important elements in rendered content. (Level AA)
2.3.2 152 02.03.02 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.2 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.3 153 02.03.03 h3 Allow Direct Activation of Enabled Elements The user can move directly to and activate any enabled element in rendered content. A 2.3.3 Allow Direct Activation of Enabled Elements: The user can move directly to and activate any enabled element in rendered content. (Level A)
2.3.4 154 02.03.04 h3 Present Direct Commands in User Interface The user can have any direct commands in the user agent user interface (e.g. keyboard shortcuts) be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). AA 2.3.4 Present Direct Commands in User Interface: The user can have any direct commands in the user agent user interface (e.g. keyboard shortcuts) be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). (Level AA)
2.3.5 155 02.03.05 h3 Allow Customized Keyboard Commands The user can remap any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and user agent user interface controls, except for conventional bindings for the operating environment (e.g. arrow keys for navigating within menus). AA 2.3.5 Allow Customized Keyboard Commands: The user can remap any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and user agent user interface controls, except for conventional bindings for the operating environment (e.g. arrow keys for navigating within menus). (Level AA)
2.4 156 02.04 h2 Provide text search Provide text search Guideline 2.4 - Provide text search
2.4-N1 157 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 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 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 158 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 159 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 160 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 161 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 162 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 163 02.05 h2 Provide structural navigation Provide structural navigation Guideline 2.5 - Provide structural navigation
2.5-N1 164 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 165 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 166 02.05.02 h3 Provide Navigation by Heading and within Tables The user agent provides at least the following types of structural navigation, where the structure types exist: AA 2.5.2 Provide Navigation by Heading and within Tables: The user agent provides at least the following types of structural navigation, where the structure types exist: (Level AA)
2.5.2.1 167 02.05.02.01 h4 Provide Navigation by Heading and within Tables The user agent provides at least the following types of structural navigation, where the structure types exist: AA * By heading
2.5.2.2 168 02.05.02.02 h4 Provide Navigation by Heading and within Tables The user agent provides at least the following types of structural navigation, where the structure types exist: AA * Within tables
2.5.3 169 02.05.03 h3 Allow Elements to be Configured for Structural Navigation The user can configure a set of important elements (including element type) for structured navigation and hierarchical/outline view. AAA 2.5.3 Allow Elements to be Configured for Structural Navigation: The user can configure a set of important elements (including element type) for structured navigation and hierarchical/outline view. (Level AAA)
2.6 170 02.06 h2 Provide access to event handlers Provide access to event handlers Guideline 2.6 - Provide access to event handlers
2.6-N1 171 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 172 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 173 02.07 h2 Configure and store preference settings Configure and store preference settings Guideline 2.7 - Configure and store preference settings
2.7-N1 174 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 setting 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 setting 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 175 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.2 176 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 177 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 178 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 user agent 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 user agent user interface. (Level AAA)
2.7.5 179 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 180 02.08 h2 Customize display of graphical controls Customize display of graphical controls Guideline 2.8 - Customize display of graphical controls
2.8-N1 181 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 182 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 183 02.08.01.01 h4 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 * 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 184 02.08.01.02 h4 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 * 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 185 02.08.01.03 h4 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 * 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 186 02.08.01.04 h4 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 * 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 187 02.08.01.05 h4 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 * Reset: The user has the option to reset the containers and controls to their default configuration.
2.9 188 02.09 h2 Allow time-independent interaction Allow time-independent interaction Guideline 2.9 - Allow time-independent interaction
2.9-N1 189 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 190 02.09.01 h3 Adjustable Time Limits Where time limits for user input are recognized and controllable by the user agent, the user can extend the time limits. A 2.9.1 Adjustable Time Limits: Where time limits for user input are recognized and controllable by the user agent, the user can extend the time limits. (Level A)
2.10 191 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 192 02.10-N01 note Help users avoid flashing that could cause seizures Summary: To help users avoid seizures, the default configuration prevents the browser user interface and rendered content from flashing more than three times a second above 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 and rendered content 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 193 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 194 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 195 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 196 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.1.7, Level AA), enable or disable tracks (2.11.8, Level AA), and adjust contrast and brightness of visual time-based media (2.11.9, Level AAA). 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.1.7, Level AA), enable or disable tracks (2.11.8, Level AA), and adjust contrast and brightness of visual time-based media (2.11.9, Level AAA).
2.11.1 197 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 198 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 199 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 200 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 201 02.11.04.01 h4 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 * 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 202 02.11.04.02 h4 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 * 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 203 02.11.04.03 h4 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 * Synchronization: Audio and video tracks remain synchronized across this required range of playback rates.
2.11.4.4 204 02.11.04.04 h4 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 * Reset: The user agent provides a function that resets the playback rate to normal (100%).
2.11.5 205 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 206 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 207 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 208 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 209 02.12 h2 Support other input devices Support other input devices Guideline 2.12 - Support other input devices
2.12-N1 210 02.12-N01 note Support other input devices Summary: User agents support all of the platform's 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's 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 211 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 212 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 213 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 214 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 215 03.01 h2 Help users avoid unnecessary messages Help users avoid unnecessary messages Guideline 3.1 - Help users avoid unnecessary messages
3.1-N1 216 03.01-N01 note Help users avoid unnecessary messages Summary: Users can turn off non-essential messages from the author or user-agent (3.1.1, Level AA). Summary: Users can turn off non-essential messages from the author or user-agent (3.1.1, Level AA).
3.1.1 217 03.01.01 h3 Reduce Interruptions The user can avoid or defer: AA 3.1.1 Reduce Interruptions: The user can avoid or defer: (Level AA)
3.1.1-N1 218 03.01.01-N01 note Reduce Interruptions (a) Recognized messages that are non-essential or low priority (a) Recognized messages that are non-essential or low priority
3.1.1-N2 219 03.01.01-N02 note Reduce Interruptions (b) Information in the user agent user interface that is being updated or changing (b) Information in the user agent user interface that is being updated or changing
3.1.1-N3 220 03.01.01-N03 note Reduce Interruptions (c) Rendered content that is being updated or changing (c)  Rendered content that is being updated or changing
3.2 221 03.02 h2 Help users avoid and correct mistakes Help users avoid and correct mistakes Guideline 3.2 - Help users avoid and correct mistakes
3.2-N1 222 03.02-N01 note Help users avoid and correct mistakes Summary: Users can have form submissions require confirmation (3.2.1, Level AA), go back after navigating (3.2.2, Level AA), have their text checked for spelling errors (3.2.3, Level AA), undo text entry (3.2.4, Level A), avoid or undo settings changes (3.2.5, Level A), and receive indications of progress activity (3.2.6, Level A). Summary: Users can have form submissions require confirmation (3.2.1, Level AA), go back after navigating (3.2.2, Level AA), have their text checked for spelling errors (3.2.3, Level AA), undo text entry (3.2.4, Level A), avoid or undo settings changes (3.2.5, Level A), and receive indications of progress activity (3.2.6, Level A).
3.2.1 223 03.02.01 h3 Form Submission Confirm The user can specify whether or not recognized form submissions must be confirmed. AA 3.2.1 Form Submission Confirm: The user can specify whether or not recognized form submissions must be confirmed. (Level AA)
3.2.2 224 03.02.02 h3 Back Button The user can reverse recognized navigation between web addresses (e.g. standard "back button" functionality). AA 3.2.2 Back Button: The user can reverse recognized navigation between web addresses (e.g. standard "back button" functionality). (Level AA)
3.2.3 225 03.02.03 h3 Spell Check User agents provide spell checking functionality for text created inside the user agent. AA 3.2.3 Spell Check: User agents provide spell checking functionality for text created inside the user agent. (Level AA)
3.2.4 226 03.02.04 h3 Text Entry Undo The user can reverse recognized text entry actions prior to submission. A 3.2.4 Text Entry Undo: The user can reverse recognized text entry actions prior to submission. (Level A)
3.2.4-N1 227 03.02.04-N01 note Text Entry Undo Submission can be triggered in many different ways, such as clicking a submit button, typing a key in a control with an onkeypress event, or by a script responding to a timer. Note: Submission can be triggered in many different ways, such as clicking a submit button, typing a key in a control with an onkeypress event, or by a script responding to a timer.
3.2.5 228 03.02.05 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.2.5 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.2.6 229 03.02.06 h3 Retrieval Progress By default, the user agent shows the state of content retrieval activity. A 3.2.6 Retrieval Progress: By default, the user agent shows the state of content retrieval activity. (Level A)
3.3 230 03.03 h2 Document the user agent user interface including accessibility features Document the user agent user interface including accessibility features Guideline 3.3 - Document the user agent user interface including accessibility features
3.3-N1 231 03.03-N01 note Document the user agent user interface including accessibility features Summary: User documentation is available in an accessible format (3.3.1, Level A), it includes accessibility features (3.3.2, Level A), delineates differences between versions (3.3.3, Level AA), provides a centralized view of conformance UAAG2.0 (3.3.4, Level AAA). Summary: User documentation is available in an accessible format (3.3.1, Level A), it includes accessibility features (3.3.2, Level A), delineates differences between versions (3.3.3, Level AA), provides a centralized view of conformance UAAG2.0 (3.3.4, Level AAA).
3.3.1 232 03.03.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.3.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.3.2 233 03.03.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.3.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.3.2-N1 234 03.03.02-N01 note Describe Accessibility Features (a) Described in the Documentation: Use of the feature is explained in the user agent's documentation; or (a) Described in the Documentation: Use of the feature is explained in the user agent's documentation; or
3.3.2-N2 235 03.03.02-N02 note Describe Accessibility Features (b) Described in the Interface: Use of the feature is explained in the user agent user interface; or (b) Described in the Interface: Use of the feature is explained in the user agent user interface; or
3.3.2-N3 236 03.03.02-N03 note Describe Accessibility Features (c) Platform Service: The feature is a service provided by an underlying platform; or (c) Platform Service: The feature is a service provided by an underlying platform; or
3.3.2-N4 237 03.03.02-N04 note Describe Accessibility Features (d) Not Used by Users: The feature is not used directly by users (e.g., passing information to a platform accessibility service). (d) Not Used by Users: The feature is not used directly by users (e.g., passing information to a platform accessibility service).
3.3.3 238 03.03.03 h3 Changes Between Versions Changes to features that meet UAAG 2.0 success criteria since the previous user agent release are documented. AA 3.3.3 Changes Between Versions: Changes to features that meet UAAG 2.0 success criteria since the previous user agent release are documented. (Level AA)
3.3.4 239 03.03.04 h3 Centralized View There is a dedicated section of the documentation that presents a view of all features of the user agent necessary to meet the requirements of User Agent Accessibility Guidelines 2.0. AAA 3.3.4 Centralized View: There is a dedicated section of the documentation that presents a view of all features of the user agent necessary to meet the requirements of User Agent Accessibility Guidelines 2.0. (Level AAA)
3.4 240 03.04 h2 Make the user agent behave in predictable ways Make the user agent behave in predictable ways Guideline 3.4 - Make the user agent behave in predictable ways
3.4-N1 241 03.04-N01 note Make the user agent behave in predictable ways Summary: Users can prevent non-requested focus changes (3.4.1, Level A). Summary: Users can prevent non-requested focus changes (3.4.1, Level A).
3.4.1 242 03.04.01 h3 Avoid Unpredictable Focus The user can prevent focus changes that are not a result of explicit user request. A 3.4.1 Avoid Unpredictable Focus: The user can prevent focus changes that are not a result of explicit user request. (Level A)
4 243 04 h1 Facilitate programmatic access Facilitate programmatic access PRINCIPLE 4: Facilitate programmatic access
4.1 244 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 245 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 246 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 247 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 248 04.01.02 h3 Expose Basic Properties For all user interface components, including user agent 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 user agent 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 249 04.01.02.01 h4 Expose Basic Properties For all user interface components, including user agent user interface, rendered content, and generated content, the user agent makes available the following via a platform accessibility service: A *  Name
4.1.2.2 250 04.01.02.02 h4 Expose Basic Properties For all user interface components, including user agent user interface, rendered content, and generated content, the user agent makes available the following via a platform accessibility service: A * Role
4.1.2.3 251 04.01.02.03 h4 Expose Basic Properties For all user interface components, including user agent user interface, rendered content, and generated content, the user agent makes available the following via a platform accessibility service: A * State
4.1.2.4 252 04.01.02.04 h4 Expose Basic Properties For all user interface components, including user agent user interface, rendered content, and generated content, the user agent makes available the following via a platform accessibility service: A * Value
4.1.2.5 253 04.01.02.05 h4 Expose Basic Properties For all user interface components, including user agent user interface, rendered content, and generated content, the user agent makes available the following via a platform accessibility service: A * Selection
4.1.2.6 254 04.01.02.06 h4 Expose Basic Properties For all user interface components, including user agent user interface, rendered content, and generated content, the user agent makes available the following via a platform accessibility service: A * Focus
4.1.3 255 04.01.03 h3 Provide Equivalent Accessible Alternatives If a component of the user agent 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 user agent 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 256 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 257 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 258 04.01.06 h3 Expose Additional Properties For all user interface components, including the user agent 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 user agent 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 259 04.01.06.01 h4 Expose Additional Properties For all user interface components, including the user agent 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 * Bounding dimensions and coordinates
4.1.6.2 260 04.01.06.02 h4 Expose Additional Properties For all user interface components, including the user agent 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 * Font family of text
4.1.6.3 261 04.01.06.03 h4 Expose Additional Properties For all user interface components, including the user agent 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 * Font size of text
4.1.6.4 262 04.01.06.04 h4 Expose Additional Properties For all user interface components, including the user agent 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 * Foreground and background color for text
4.1.6.5 263 04.01.06.05 h4 Expose Additional Properties For all user interface components, including the user agent 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 * Change state/value notifications
4.1.6.6 264 04.01.06.06 h4 Expose Additional Properties For all user interface components, including the user agent 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 * Highlighting
4.1.6.7 265 04.01.06.07 h4 Expose Additional Properties For all user interface components, including the user agent 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 * Keyboard commands
4.1.7 266 04.01.07 h3 Make Programmatic Exchanges Timely For APIs implemented to satisfy the requirements of UAAG 2.0, ensure that programmatic exchanges proceed at a rate such that users do not perceive a delay. A 4.1.7 Make Programmatic Exchanges Timely: For APIs implemented to satisfy the requirements of UAAG 2.0, ensure that programmatic exchanges proceed at a rate such that users do not perceive a delay. (Level A)
5 267 05 h1 Comply with applicable specifications and conventions Comply with applicable specifications and conventions PRINCIPLE 5: Comply with applicable specifications and conventions
5.1 268 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 269 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) including by 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) including by alternative viewers (5.1.5, Level AA), and allows users to report accessibility issues (5.1.6, Level AAA).
5.1.1 270 05.01.01 h3 Comply with WCAG Web-based user agent 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 user agent 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 271 05.01.01-N01 note Comply with WCAG This success criterion does not apply to non-web-based user agent user interfaces, but does include any parts of non-web-based user agents that are web-based (e.g. help systems). Note: This success criterion does not apply to non-web-based user agent user interfaces, but does include any parts of non-web-based user agents that are web-based (e.g. help systems).
5.1.2 272 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 273 05.01.02.01 h4 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 * Allow authors to satisfy a requirement of WCAG 2.0
5.1.2-N 1 274 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 275 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 276 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 277 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 278 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 279 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)