- Important note: This Wiki page is edited by participants of the User Agent Accessibility Guidelines working group (UAWG). It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

Browser Compliance Notes

From WAI UA Wiki
Revision as of 19:02, 22 February 2012 by Glowney (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This is currently based on http://www.w3.org/WAI/UA/2012/ED-UAAG20-20120119/.

PRINCIPLE 1 - Ensure that the user interface and rendered content are perceivable

Guideline 1.1 - Provide access to alternative content.

1.1.1 Configurable Alternative Content Defaults

The user can specify which types of alternative content to render by default. (A)

Chrome notes for 1.1.1

You can turn off display of images, but they are replaced by a box, not their alt text. (Chrome 17: Options -> Under the Hood -> Privacy -> Content Settings -> Do not show any images)

Firefox notes for 1.1.1

You can turn off display of images, and they are replaced by their alt text, although not demarcated from surrounding content. (Firefox 10: Tools -> Options -> Content -> Load Images Automatically)

Internet Explorer notes for 1.1.1
Opera notes for 1.1.1
Safari notes for 1.1.1
Others notes for 1.1.1

1.1.2 Browse and Render

When a rendered element has alternative content, the user can render alternatives according to the following: * synchronized alternatives for time-based media (e.g. captions, audio descriptions, sign language) can be rendered at the same time as their associated audio tracks and visual tracks, and * non-synchronized alternatives (e.g. short text alternatives, long descriptions) can be rendered as replacements for the original rendered content. (A)

Chrome notes for 1.1.2
Firefox notes for 1.1.2
Internet Explorer notes for 1.1.2
Opera notes for 1.1.2
Safari notes for 1.1.2
Others notes for 1.1.2

1.1.3 Identify Presence of Unrendered Alternative Content

The user can specify that content be rendered with an adjacent indicator when unrendered alternative content is present (e.g. an icon to indicate an image has a short text alternative). (A)

Chrome notes for 1.1.3
Firefox notes for 1.1.3
Internet Explorer notes for 1.1.3
Opera notes for 1.1.3
Safari notes for 1.1.3
Others notes for 1.1.3

1.1.4 Rendering Alternative Cascade Order

The user can specify the cascade order in which to render alternative content. (AA)

Chrome notes for 1.1.4
Firefox notes for 1.1.4
Internet Explorer notes for 1.1.4
Opera notes for 1.1.4
Safari notes for 1.1.4
Others notes for 1.1.4

Guideline 1.2 - Repair missing content.

1.2.1 Repair Missing Alternatives

The user can specify whether or not the user agent should generate and render repair text (e.g. file name) when it recognizes that the author has not provided alternative content. (A)

Chrome notes for 1.2.1
Firefox notes for 1.2.1
Internet Explorer notes for 1.2.1
Opera notes for 1.2.1
Safari notes for 1.2.1
Others notes for 1.2.1

1.2.2 Repair Empty Alternatives

The user can specify whether or not the user agent should generate and render repair text (e.g. file name) when it recognizes that the author has provided empty alternative content. (AAA)

Chrome notes for 1.2.2
Firefox notes for 1.2.2
Internet Explorer notes for 1.2.2
Opera notes for 1.2.2
Safari notes for 1.2.2
Others notes for 1.2.2

1.2.3 Repair Missing Associations

The user can specify whether or not the user agent should attempt to predict associations from author-specified presentation attributes (i.e. position and appearance). (AAA)

Chrome notes for 1.2.3
Firefox notes for 1.2.3
Internet Explorer notes for 1.2.3
Opera notes for 1.2.3
Safari notes for 1.2.3
Others notes for 1.2.3

1.2.4 Broken Alternative Content

The user can be notified when the user agent cannot render alternative content (e.g. when captions are broken). (AAA)

Chrome notes for 1.2.4
Firefox notes for 1.2.4
Internet Explorer notes for 1.2.4
Opera notes for 1.2.4
Safari notes for 1.2.4
Others notes for 1.2.4

Guideline 1.3 - Provide highlighting for selection, keyboard focus, enabled elements, visited links.

1.3.1 Highlighted Items

The user can globally specify that the following be highlighted so that each class is uniquely distinguished. It is not the intention that all recognized enabled elements be uniquely distinguished, just that they be distinguished from disabled elements. (a) selection (b) active keyboard focus (indicated by focus cursors and/or text cursors) (c) recognized enabled elements (d) elements with alternative content (e) recently visited links (A)

Chrome notes for 1.3.1
Firefox notes for 1.3.1
Internet Explorer notes for 1.3.1
Opera notes for 1.3.1
Safari notes for 1.3.1
Others notes for 1.3.1

1.3.2 Highlighting Options

When highlighting classes specified by 1.3.1 Highlighted Items and 1.3.3 Highlighted Input Controls, The user can specify highlighting options that include at least: [@@Editor's Note: Review for editorial rewording to compensate for a reference to an SC the reader hasn't read yet.@@ ] (a) foreground colors, (b) background colors, and (c) border (configurable color, style, and thickness) (A)

Chrome notes for 1.3.2
Firefox notes for 1.3.2
Internet Explorer notes for 1.3.2
Opera notes for 1.3.2
Safari notes for 1.3.2
Others notes for 1.3.2

1.3.3 Highlighted Input Controls

The user can have the following highlighted when they are recognized: (a) enabled controls that take input (e.g. push buttons, radio buttons, check boxes, and text input fields, but not groupings or static text and images) regardless of whether they are read-write or read-only, and (b) elements with scripted input handlers (e.g. images or text ranges that have onClick or onKeyPress events) regardless of whether the current state allows them to operate. (AA)

Chrome notes for 1.3.3
Firefox notes for 1.3.3
Internet Explorer notes for 1.3.3
Opera notes for 1.3.3
Safari notes for 1.3.3
Others notes for 1.3.3

Guideline 1.4 - Provide text configuration.

1.4.1 Configure Rendered Text

The user can globally set any or all of the following characteristics of visually rendered text content, overriding any specified by the author or user agent defaults: (a) text scale (i.e. the general size of text) , (b) font family, (c) text color (i.e. foreground and background), (d) line spacing, and (e) character spacing. (A)

Chrome notes for 1.4.1
Firefox notes for 1.4.1
Internet Explorer notes for 1.4.1
Opera notes for 1.4.1
Safari notes for 1.4.1
Others notes for 1.4.1

1.4.2 Preserving Size Distinctions

The user can specify whether or not distinctions in the size of rendered text are preserved when that text is rescaled (e.g. headers continue to be larger than body text). (A)

Chrome notes for 1.4.2
Firefox notes for 1.4.2
Internet Explorer notes for 1.4.2
Opera notes for 1.4.2
Safari notes for 1.4.2
Others notes for 1.4.2

Guideline 1.5 - Provide volume configuration.

1.5.1 Global Volume

The user can independently adjust the volume of all audio tracks, relative to the global volume level set through operating environment mechanisms. If the global setting is mute, the user agent may override a global mute on explicit user request that cautions the user about the implication. (A)

Chrome notes for 1.5.1
Firefox notes for 1.5.1
Internet Explorer notes for 1.5.1
Opera notes for 1.5.1
Safari notes for 1.5.1
Others notes for 1.5.1

Guideline 1.6 - Provide synthesized speech configuration.

1.6.1 Speech Rate, Volume, and Voice

If synthesized speech is produced, the user can specify the following: (a) speech rate, (b) speech volume (independently of other sources of audio), and (c) voice, when more than one voice option is available (A)

Chrome notes for 1.6.1
Firefox notes for 1.6.1
Internet Explorer notes for 1.6.1
Opera notes for 1.6.1
Safari notes for 1.6.1
Others notes for 1.6.1

1.6.2 Speech Pitch and Range

If synthesized speech is produced, the user can specify the following: (a) pitch (i.e. the average frequency of the speaking voice), and (b) pitch range (i.e. specifies a variation in average frequency), (AA)

Chrome notes for 1.6.2
Firefox notes for 1.6.2
Internet Explorer notes for 1.6.2
Opera notes for 1.6.2
Safari notes for 1.6.2
Others notes for 1.6.2

1.6.3 Advanced Speech Characteristics

The user can adjust all of the speech characteristics offered by the speech synthesizer. (AAA)

Chrome notes for 1.6.3
Firefox notes for 1.6.3
Internet Explorer notes for 1.6.3
Opera notes for 1.6.3
Safari notes for 1.6.3
Others notes for 1.6.3

1.6.4 Synthesized Speech Features

If synthesized speech is produced, the following features are provided: (a) user-defined extensions to the synthesized speech dictionary, (b) ""spell-out"", where text is spelled one character at a time, or according to language-dependent pronunciation rules, (c) at least two ways of speaking numerals: one where numerals are spoken as individual digits and punctuation (e.g. ""one two zero three point five"" for 1203.5 or ""one comma two zero three point five"" for 1,203.5), and one where full numbers are spoken (e.g. ""one thousand, two hundred and three point five""). (d) at least two ways of speaking punctuation: one where punctuation is spoken literally, and one where punctuation is rendered as natural pauses. (AA)

Chrome notes for 1.6.4
Firefox notes for 1.6.4
Internet Explorer notes for 1.6.4
Opera notes for 1.6.4
Safari notes for 1.6.4
Others notes for 1.6.4

Guideline 1.7 - Enable Configuration of Style Profiles.

1.7.1 Support User Style Profiles

User agents that support a mechanism for authors to supply style profiles shall also provide an equally effective mechanism for users to supply profiles. (A)

Chrome notes for 1.7.1
Firefox notes for 1.7.1
Internet Explorer notes for 1.7.1
Opera notes for 1.7.1
Safari notes for 1.7.1
Others notes for 1.7.1

1.7.2 Apply User Style Profiles

The user can turn on the use of user style profiles and for every user style profile defined, the user can choose whether or not it should be applied to: (a) the current page, or (b) all pages on specified web sites, or (c) all pages. (A)

Chrome notes for 1.7.2
Firefox notes for 1.7.2
Internet Explorer notes for 1.7.2
Opera notes for 1.7.2
Safari notes for 1.7.2
Others notes for 1.7.2

1.7.3 Author Style Sheets

The user can turn off the use of author style profiles, and for every author style sheet defined the user can choose whether or not it should be applied to: (a) the current page, or (b) all pages for which it is defined. (A)

Chrome notes for 1.7.3
Firefox notes for 1.7.3
Internet Explorer notes for 1.7.3
Opera notes for 1.7.3
Safari notes for 1.7.3
Others notes for 1.7.3

1.7.4 Save copies of style profiles

The user can save copies of the style profiles referenced by the current page, so that they can edit and load them as user style profiles. (AA)

Chrome notes for 1.7.4
Firefox notes for 1.7.4
Internet Explorer notes for 1.7.4
Opera notes for 1.7.4
Safari notes for 1.7.4
Others notes for 1.7.4

Guideline 1.8 - Help users to use and orient within windows and viewports.

1.8.1 Highlight Viewport

The viewport with the input focus (including nested viewports and their containers) is highlighted, and the user can customize attributes of the highlighted mechanism, including, but not limited to, shape, size, stroke width, color, and blink rate (if any). (A)

Chrome notes for 1.8.1
Firefox notes for 1.8.1
Internet Explorer notes for 1.8.1
Opera notes for 1.8.1
Safari notes for 1.8.1
Others notes for 1.8.1

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. (A)

Chrome notes for 1.8.2
Firefox notes for 1.8.2
Internet Explorer notes for 1.8.2
Opera notes for 1.8.2
Safari notes for 1.8.2
Others notes for 1.8.2

1.8.3 Resize Viewport

The user can make viewports resizable, within the limits of the display, overriding any values specified by the author. (A)

Chrome notes for 1.8.3
Firefox notes for 1.8.3
Internet Explorer notes for 1.8.3
Opera notes for 1.8.3
Safari notes for 1.8.3
Others notes for 1.8.3

1.8.4 Viewport Scrollbars

Graphical viewports include scrollbars if the rendered content (including after user preferences have been applied) extends beyond the viewport dimensions, overriding any values specified by the author. (A)

Chrome notes for 1.8.4
Firefox notes for 1.8.4
Internet Explorer notes for 1.8.4
Opera notes for 1.8.4
Safari notes for 1.8.4
Others notes for 1.8.4

1.8.11 Indicate Viewport Position

The user can determine the viewport's position relative to the full extent of the rendered content. (A)

Chrome notes for 1.8.11
Firefox notes for 1.8.11
Internet Explorer notes for 1.8.11
Opera notes for 1.8.11
Safari notes for 1.8.11
Others notes for 1.8.11

1.8.5 Viewport History

For user agents that implement a viewport history mechanism (e.g. ""back"" button), the user can return to any state in the viewport history, restoring the prior point of regard, input focus and selection. (A)

Chrome notes for 1.8.5
Firefox notes for 1.8.5
Internet Explorer notes for 1.8.5
Opera notes for 1.8.5
Safari notes for 1.8.5
Others notes for 1.8.5

1.8.6 Open on Request

The user can specify whether author content can open new top-level viewports (e.g. windows or tabs). (A)

Chrome notes for 1.8.6
Firefox notes for 1.8.6
Internet Explorer notes for 1.8.6
Opera notes for 1.8.6
Safari notes for 1.8.6
Others notes for 1.8.6

1.8.7 Do Not Take Focus

If new top-level viewports (e.g. windows or tabs) are configured to open without explicit user request, the user can specify whether or not top-level viewports take the active keyboard focus when they open. (AA)

Chrome notes for 1.8.7
Firefox notes for 1.8.7
Internet Explorer notes for 1.8.7
Opera notes for 1.8.7
Safari notes for 1.8.7
Others notes for 1.8.7

1.8.10 Same UI

The user can specify that all top-level viewports (e.g. windows or tabs) follow the current user interface configuration. (AA)

Chrome notes for 1.8.10
Firefox notes for 1.8.10
Internet Explorer notes for 1.8.10
Opera notes for 1.8.10
Safari notes for 1.8.10
Others notes for 1.8.10

Guideline 1.10 - Provide alternative views.

1.10.1 Source View

The user can view all source text that is available to the user agent. (AA)

Chrome notes for 1.10.1
Firefox notes for 1.10.1
Internet Explorer notes for 1.10.1
Opera notes for 1.10.1
Safari notes for 1.10.1
Others notes for 1.10.1

1.10.2 Outline View

An outline view of rendered content is provided, composed of labels for important structural elements (e.g. heading text, table titles, form titles, and other labels that are part of the content). (AA)

Chrome notes for 1.10.2
Firefox notes for 1.10.2
Internet Explorer notes for 1.10.2
Opera notes for 1.10.2
Safari notes for 1.10.2
Others notes for 1.10.2

1.10.3 Configure Elements for Outline View

The user can configure the set of important elements for the outline view, including by element type (e.g. headers). (AAA)

Chrome notes for 1.10.3
Firefox notes for 1.10.3
Internet Explorer notes for 1.10.3
Opera notes for 1.10.3
Safari notes for 1.10.3
Others notes for 1.10.3

Guideline 1.11 - Provide element information.

1.11.1 Access Relationships

The user can access explicitly-defined relationships based on the user's position in content (e.g. show form control's label, show label's form control, show a cell's table headers). (A)

Chrome notes for 1.11.1
Firefox notes for 1.11.1
Internet Explorer notes for 1.11.1
Opera notes for 1.11.1
Safari notes for 1.11.1
Others notes for 1.11.1

1.11.2 Extended Link Information

The user agent provides for each link: * link title * technology type (of the linked Web resource) * internal/external (whether the link is internal to the resource e.g. the link is to a target in the same Web page) (AAA)

Chrome notes for 1.11.2
Firefox notes for 1.11.2
Internet Explorer notes for 1.11.2
Opera notes for 1.11.2
Safari notes for 1.11.2
Others notes for 1.11.2

PRINCIPLE 2. Ensure that the user interface is operable

Guideline 2.1 - Ensure full keyboard access.

2.1.1 Keyboard Operation

All functionality can be operated via the keyboard using sequential or direct keyboard commands that do not require specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (e.g. free hand drawing). This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation. (A)

Chrome notes for 2.1.1
Firefox notes for 2.1.1
Internet Explorer notes for 2.1.1
Opera notes for 2.1.1
Safari notes for 2.1.1
Others notes for 2.1.1

2.1.2 Keyboard Focus

Every viewport has an active or inactive keyboard focus at all times. (A)

Chrome notes for 2.1.2
Firefox notes for 2.1.2
Internet Explorer notes for 2.1.2
Opera notes for 2.1.2
Safari notes for 2.1.2
Others notes for 2.1.2

2.1.3 Viewport Navigation

The user can move the active keyboard focus to any viewport. (A)

Chrome notes for 2.1.3
Firefox notes for 2.1.3
Internet Explorer notes for 2.1.3
Opera notes for 2.1.3
Safari notes for 2.1.3
Others notes for 2.1.3

2.1.4 Specify preferred keystrokes

The user can override any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and user interface controls, except for conventional bindings for the operating environment (e.g. arrow keys for navigating within menus). (A)

Chrome notes for 2.1.4
Firefox notes for 2.1.4
Internet Explorer notes for 2.1.4
Opera notes for 2.1.4
Safari notes for 2.1.4
Others notes for 2.1.4

2.1.5 No Keyboard Trap

If keyboard focus can be moved to a component using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, users are advised of the method for moving focus away. The user agent prevents keyboard traps as follows: (a) in the UI: if keyboard focus can be moved to a component using the keyboard, then focus can be moved away from that component using standard sequential keyboard commands (e.g. TAB key) (b) in the rendered content: provides a documented direct keyboard command that will always restore keyboard focus to a known location (e.g. the address bar). (c) in the rendered content: provides a documented direct keyboard command that will always move keyboard focus to a subsequent focusable element (A)

Chrome notes for 2.1.5
Firefox notes for 2.1.5
Internet Explorer notes for 2.1.5
Opera notes for 2.1.5
Safari notes for 2.1.5
Others notes for 2.1.5

2.1.6 Separate Selection from Activation

The user can specify that selection is separate from activation (e.g. navigating through a set of radio buttons without changing which is the active/selected option). (A)

Chrome notes for 2.1.6
Firefox notes for 2.1.6
Internet Explorer notes for 2.1.6
Opera notes for 2.1.6
Safari notes for 2.1.6
Others notes for 2.1.6

2.1.7 Follow Text Keyboard Conventions

Views that render text support the standard text area conventions for the operating environment. (A)

Chrome notes for 2.1.7
Firefox notes for 2.1.7
Internet Explorer notes for 2.1.7
Opera notes for 2.1.7
Safari notes for 2.1.7
Others notes for 2.1.7

2.1.8 Efficient Keyboard Access

The user agent user interface includes mechanisms to make keyboard access more efficient than sequential keyboard access. (A)

Chrome notes for 2.1.8
Firefox notes for 2.1.8
Internet Explorer notes for 2.1.8
Opera notes for 2.1.8
Safari notes for 2.1.8
Others notes for 2.1.8

2.1.9 Allow Override of User Interface Keyboard Commands

The user can override any keyboard shortcut binding for the user agent user interface except for conventional bindings for the operating environment (e.g. access to help). The rebinding options must include single-key and key-plus-modifier keys if available in the operating environment. (AA)

Chrome notes for 2.1.9
Firefox notes for 2.1.9
Internet Explorer notes for 2.1.9
Opera notes for 2.1.9
Safari notes for 2.1.9
Others notes for 2.1.9

Guideline 2.2 - Provide sequential navigation

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. (A)

Chrome notes for 2.2.1
Firefox notes for 2.2.1
Internet Explorer notes for 2.2.1
Opera notes for 2.2.1
Safari notes for 2.2.1
Others notes for 2.2.1

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. (A)

Chrome notes for 2.2.2
Firefox notes for 2.2.2
Internet Explorer notes for 2.2.2
Opera notes for 2.2.2
Safari notes for 2.2.2
Others notes for 2.2.2

2.2.3 Default Navigation Order

If the author has not specified a navigation order, the default sequential navigation order is the document order. (A)

Chrome notes for 2.2.3
Firefox notes for 2.2.3
Internet Explorer notes for 2.2.3
Opera notes for 2.2.3
Safari notes for 2.2.3
Others notes for 2.2.3

2.2.4 Options for Wrapping in Navigation

When user interaction with web content causes focus wrapping at the, the user can prevent wrapping or the user can receive feedback when wrapping. (AA)

Chrome notes for 2.2.4
Firefox notes for 2.2.4
Internet Explorer notes for 2.2.4
Opera notes for 2.2.4
Safari notes for 2.2.4
Others notes for 2.2.4

Guideline 2.3 - Provide direct navigation and activation

2.3.1 Direct Navigation to Important Elements

The user can navigate directly to important (structural and operable) elements in rendered content. (A)

Chrome notes for 2.3.1
Firefox notes for 2.3.1
Internet Explorer notes for 2.3.1
Opera notes for 2.3.1
Safari notes for 2.3.1
Others notes for 2.3.1

2.3.2 Present Direct Commands in Rendered Content

The user can have any recognized direct commands in rendered content (e.g. accesskey, landmark) be presented with their associated elements. (A)

Chrome notes for 2.3.2
Firefox notes for 2.3.2
Internet Explorer notes for 2.3.2
Opera notes for 2.3.2
Safari notes for 2.3.2
Others notes for 2.3.2

2.3.x Discover navigation and activation keystrokes

The user can discover direct navigation and activation keystrokes both programmatically and via perceivable labels. (A)

Chrome notes for 2.3.x
Firefox notes for 2.3.x
Internet Explorer notes for 2.3.x
Opera notes for 2.3.x
Safari notes for 2.3.x
Others notes for 2.3.x

2.3.3 Direct activation

The user can move directly to and activate any operable elements in rendered content. (AA)

Chrome notes for 2.3.3
Firefox notes for 2.3.3
Internet Explorer notes for 2.3.3
Opera notes for 2.3.3
Safari notes for 2.3.3
Others notes for 2.3.3

2.3.4 Present Direct Commands in User Interface

The user can have any direct commands (e.g. keyboard shortcuts) in the user agent user interface be presented with their associated user interface controls (e.g. ""Ctrl+S"" displayed on the ""Save"" menu item and toolbar button). (AA)

Chrome notes for 2.3.4
Firefox notes for 2.3.4
Internet Explorer notes for 2.3.4
Opera notes for 2.3.4
Safari notes for 2.3.4
Others notes for 2.3.4

2.3.5 Allow Override of Accesskeys

The user can override any recognized author supplied content keybinding (i.e. access key). The user must have an option to save the override of user interface keyboard shortcuts so that the rebinding persists beyond the current session. (AA)

Chrome notes for 2.3.5
Firefox notes for 2.3.5
Internet Explorer notes for 2.3.5
Opera notes for 2.3.5
Safari notes for 2.3.5
Others notes for 2.3.5

Guideline 2.4 - Provide text search.

2.4.1 Find

The user can perform a search within rendered content (e.g. not hidden with a style), including rendered text alternatives and rendered generated content, for any sequence of printing characters from the document character set. (A)

Chrome notes for 2.4.1
Firefox notes for 2.4.1
Internet Explorer notes for 2.4.1
Opera notes for 2.4.1
Safari notes for 2.4.1
Others notes for 2.4.1

2.4.2 Find Direction

The user can search forward or backward in rendered content. (A)

Chrome notes for 2.4.2
Firefox notes for 2.4.2
Internet Explorer notes for 2.4.2
Opera notes for 2.4.2
Safari notes for 2.4.2
Others notes for 2.4.2

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. (A)

Chrome notes for 2.4.3
Firefox notes for 2.4.3
Internet Explorer notes for 2.4.3
Opera notes for 2.4.3
Safari notes for 2.4.3
Others notes for 2.4.3

2.4.4 Alert on Wrap or No Match

The user can be notified when there is no match to a search operation. The user can be notified when the search continues from the beginning or end of content. (A)

Chrome notes for 2.4.4
Firefox notes for 2.4.4
Internet Explorer notes for 2.4.4
Opera notes for 2.4.4
Safari notes for 2.4.4
Others notes for 2.4.4

2.4.5 Advanced Find

The user can search with a case-sensitivity option and the ability to search all content (including alternative content, hidden content, and captions) for any sequence of characters from the document character set. (AA)

Chrome notes for 2.4.5
Firefox notes for 2.4.5
Internet Explorer notes for 2.4.5
Opera notes for 2.4.5
Safari notes for 2.4.5
Others notes for 2.4.5

Guideline 2.5 - Provide structural navigation.

2.5.3 Location in Hierarchy

The user can view the path of nodes leading from the root of any content hierarchy in which the structure and semantics are implied by presentation, as opposed to an explicit logical structure with defined semantics (such as the HTML5 Canvas Element), or as a consequence of decentralized-extensibility (such as the HTML5 item / itemprop microdata elements), and only if the user agent keeps an internal model of the hierarchy that it does not expose via the DOM or some other accessibility mechanism. . (A)

Chrome notes for 2.5.3
Firefox notes for 2.5.3
Internet Explorer notes for 2.5.3
Opera notes for 2.5.3
Safari notes for 2.5.3
Others notes for 2.5.3

2.5.5 Access to Relationships which Aid Navigation

The user can access explicitly-defined relationships based on the user's position in content, and the path of nodes leading from the root of any content hierarchy to that position. (AA)

Chrome notes for 2.5.5
Firefox notes for 2.5.5
Internet Explorer notes for 2.5.5
Opera notes for 2.5.5
Safari notes for 2.5.5
Others notes for 2.5.5

2.5.7 Configure Elements for Structural Navigation

The user can configure the sets of important elements (including element types) for structured navigation and hierarchical/outline view. (AAA)

Chrome notes for 2.5.7
Firefox notes for 2.5.7
Internet Explorer notes for 2.5.7
Opera notes for 2.5.7
Safari notes for 2.5.7
Others notes for 2.5.7

Guideline 2.6 - Provide access to event handlers

2.6.1 List event handlers

The user can call up a list of input device event handlers explicitly associated with the keyboard focus element, and activate any one or more of the event handlers. (A)

Chrome notes for 2.6.1
Firefox notes for 2.6.1
Internet Explorer notes for 2.6.1
Opera notes for 2.6.1
Safari notes for 2.6.1
Others notes for 2.6.1

Guideline 2.7 - Configure and store preference settings.

2.7.2 Persistent Accessibility Settings

User agent accessibility preference settings persist between sessions. (A)

Chrome notes for 2.7.2
Firefox notes for 2.7.2
Internet Explorer notes for 2.7.2
Opera notes for 2.7.2
Safari notes for 2.7.2
Others notes for 2.7.2

2.7.3 Restore all to default

The user can restore all preference settings to default values. (A)

Chrome notes for 2.7.3
Firefox notes for 2.7.3
Internet Explorer notes for 2.7.3
Opera notes for 2.7.3
Safari notes for 2.7.3
Others notes for 2.7.3

2.7.4 Multiple Sets of Preference Settings

The user can save and retrieve multiple sets of user agent preference settings. (AA)

Chrome notes for 2.7.4
Firefox notes for 2.7.4
Internet Explorer notes for 2.7.4
Opera notes for 2.7.4
Safari notes for 2.7.4
Others notes for 2.7.4

2.7.6 Change preference setting outside the user interface

The user can adjust preference settings from outside the user agent user interface. (AA)

Chrome notes for 2.7.6
Firefox notes for 2.7.6
Internet Explorer notes for 2.7.6
Opera notes for 2.7.6
Safari notes for 2.7.6
Others notes for 2.7.6

2.7.7 Portable Preference Settings

The user can transfer preference settings across locations onto a compatible system. (AAA)

Chrome notes for 2.7.7
Firefox notes for 2.7.7
Internet Explorer notes for 2.7.7
Opera notes for 2.7.7
Safari notes for 2.7.7
Others notes for 2.7.7

2.7.8 Preferences Wizard

One or more wizards help the user to configure the accessibility-related user agent preferences. (AAA)

Chrome notes for 2.7.8
Firefox notes for 2.7.8
Internet Explorer notes for 2.7.8
Opera notes for 2.7.8
Safari notes for 2.7.8
Others notes for 2.7.8

Guideline 2.8 - Provide toolbar configuration.

2.8.1 Configure Position

The user can add, remove, and reorder any toolbars and similar containers, and the items within them. (AA)

Chrome notes for 2.8.1
Firefox notes for 2.8.1
Internet Explorer notes for 2.8.1
Opera notes for 2.8.1
Safari notes for 2.8.1
Others notes for 2.8.1

2.8.2 Restore Default Toolbars

The user can restore the default toolbar, panel, or inspector configuration. (AAA)

Chrome notes for 2.8.2
Firefox notes for 2.8.2
Internet Explorer notes for 2.8.2
Opera notes for 2.8.2
Safari notes for 2.8.2
Others notes for 2.8.2

Guideline 2.9 - Allow time-independent interaction.

2.9.1 Adjustable Timing

Where time limits for user input are recognized and controllable by the user agent, the user can extend the time limits. (A)

Chrome notes for 2.9.1
Firefox notes for 2.9.1
Internet Explorer notes for 2.9.1
Opera notes for 2.9.1
Safari notes for 2.9.1
Others notes for 2.9.1

2.9.2 Retrieval Progress

By default, the user agent shows the progress of content retrieval. (A)

Chrome notes for 2.9.2
Firefox notes for 2.9.2
Internet Explorer notes for 2.9.2
Opera notes for 2.9.2
Safari notes for 2.9.2
Others notes for 2.9.2

Guideline 2.10 - Help users avoid flashing that could cause seizures.

2.10.1 Three Flashes or Below Threshold

In its default configuration, the user agent does not display any user interface components or recognized content that flashes more than three times in any one-second period, unless the flash is below the general flash and red flash thresholds. (A)

Chrome notes for 2.10.1
Firefox notes for 2.10.1
Internet Explorer notes for 2.10.1
Opera notes for 2.10.1
Safari notes for 2.10.1
Others notes for 2.10.1

2.10.2 Three Flashes

In its default configuration, the user agent does not display any user interface components or recognized content that flashes more than three times in any one-second period (regardless of whether not the flash is below the general flash and red flash thresholds). (AAA)

Chrome notes for 2.10.2
Firefox notes for 2.10.2
Internet Explorer notes for 2.10.2
Opera notes for 2.10.2
Safari notes for 2.10.2
Others notes for 2.10.2

Guideline 2.11 - Provide control of content that may reduce accessibility.

2.11.1 Background Image Toggle

The user has the global option to hide or show background images. (A)

Chrome notes for 2.11.1
Firefox notes for 2.11.1
Internet Explorer notes for 2.11.1
Opera notes for 2.11.1
Safari notes for 2.11.1
Others notes for 2.11.1

2.11.2 Time-Based Media Load-Only

The user can have placeholders rendered for time-based media content, such that the content is not played until explicit user request. (A)

Chrome notes for 2.11.2
Firefox notes for 2.11.2
Internet Explorer notes for 2.11.2
Opera notes for 2.11.2
Safari notes for 2.11.2
Others notes for 2.11.2

2.11.3 Execution Placeholder

The user can render a placeholder instead of executable content that would normally be contained within an on-screen area (e.g. Applet, Flash), until explicit user request to execute. (A)

Chrome notes for 2.11.3
Firefox notes for 2.11.3
Internet Explorer notes for 2.11.3
Opera notes for 2.11.3
Safari notes for 2.11.3
Others notes for 2.11.3

2.11.4 Execution Toggle

The user can turn on/off the execution of executable content that would not normally be contained within a particular area (e.g. Javascript). (A)

Chrome notes for 2.11.4
Firefox notes for 2.11.4
Internet Explorer notes for 2.11.4
Opera notes for 2.11.4
Safari notes for 2.11.4
Others notes for 2.11.4

2.11.5 Playback Rate Adjustment for Prerecorded Content

The user can adjust the playback rate of prerecorded time-based media content, such that all of the following are true: * The user can adjust the playback rate of the time-based media tracks to between 50% and 250% of real time. * Speech whose playback rate has been adjusted by the user maintains pitch in order to limit degradation of the speech quality. * Audio and video tracks remain synchronized across this required range of playback rates. * The user agent provides a function that resets the playback rate to normal (100%). (A)

Chrome notes for 2.11.5
Firefox notes for 2.11.5
Internet Explorer notes for 2.11.5
Opera notes for 2.11.5
Safari notes for 2.11.5
Others notes for 2.11.5

2.11.6 Stop/Pause/Resume Time-Based Media

The user can stop, pause, and resume rendered audio and animation content (including video, animated images, and changing text) that last three or more seconds at their default playback rate. (A)

Chrome notes for 2.11.6
Firefox notes for 2.11.6
Internet Explorer notes for 2.11.6
Opera notes for 2.11.6
Safari notes for 2.11.6
Others notes for 2.11.6

2.11.7 Navigate Time-Based Media

The user can navigate along the timebase using a continuous scale, and by relative time units within rendered audio and animations (including video and animated images) that last three or more seconds at their default playback rate. (A)

Chrome notes for 2.11.7
Firefox notes for 2.11.7
Internet Explorer notes for 2.11.7
Opera notes for 2.11.7
Safari notes for 2.11.7
Others notes for 2.11.7

2.11.8 Semantic Navigation of Time-Based Media

The user can navigate by semantic structure within the time-based media, such as by chapters or scenes present in the media . (AA)

Chrome notes for 2.11.8
Firefox notes for 2.11.8
Internet Explorer notes for 2.11.8
Opera notes for 2.11.8
Safari notes for 2.11.8
Others notes for 2.11.8

2.11.9 Track Enable/Disable of Time-Based Media

During time-based media playback, the user can determine which tracks are available and select or deselect tracks, overriding global default settings for captions, audio descriptions, etc. (AA)

Chrome notes for 2.11.9
Firefox notes for 2.11.9
Internet Explorer notes for 2.11.9
Opera notes for 2.11.9
Safari notes for 2.11.9
Others notes for 2.11.9

2.11.11 Scale and position visual alternative media tracks

The user can scale and position alternative media tracks independent of base video. (AAA)

Chrome notes for 2.11.11
Firefox notes for 2.11.11
Internet Explorer notes for 2.11.11
Opera notes for 2.11.11
Safari notes for 2.11.11
Others notes for 2.11.11

2.11.12 Video Contrast and Brightness

Users can adjust the contrast and brightness of visual time-based media. (AAA)

Chrome notes for 2.11.12
Firefox notes for 2.11.12
Internet Explorer notes for 2.11.12
Opera notes for 2.11.12
Safari notes for 2.11.12
Others notes for 2.11.12

Guideline 2.12 - Other Input Devices

2.12.1 Support Platform Text Input Devices

If the platform supports text input using an input device, the user agent is compatible with this functionality. (A)

Chrome notes for 2.12.1
Firefox notes for 2.12.1
Internet Explorer notes for 2.12.1
Opera notes for 2.12.1
Safari notes for 2.12.1
Others notes for 2.12.1

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. (AA)

Chrome notes for 2.12.2
Firefox notes for 2.12.2
Internet Explorer notes for 2.12.2
Opera notes for 2.12.2
Safari notes for 2.12.2
Others notes for 2.12.2

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. (AAA)

Chrome notes for 2.12.3
Firefox notes for 2.12.3
Internet Explorer notes for 2.12.3
Opera notes for 2.12.3
Safari notes for 2.12.3
Others notes for 2.12.3

PRINCIPLE 3: Ensure that the user interface is understandable

Guideline 3.1 - Help users avoid unnecessary messages.

3.1.2 Option to Ignore

The user can turn off rendering of non-essential or low priority text messages or updating/changing information in the content based on priority properties defined by the author or the user agent. (AA)

Chrome notes for 3.1.2
Firefox notes for 3.1.2
Internet Explorer notes for 3.1.2
Opera notes for 3.1.2
Safari notes for 3.1.2
Others notes for 3.1.2

Guideline 3.2 - Help users avoid and correct mistakes.

3.2.1 Form Submission

The user can specify whether or not recognized form submissions must be confirmed. (AA)

Chrome notes for 3.2.1
Firefox notes for 3.2.1
Internet Explorer notes for 3.2.1
Opera notes for 3.2.1
Safari notes for 3.2.1
Others notes for 3.2.1

Guideline 3.3 - Document the user agent user interface including accessibility features.

3.3.1 Accessible documentation

The product documentation is available in a format that meets success criteria of WCAG 2.0 Level ""A"" or greater. (A)

Chrome notes for 3.3.1
Firefox notes for 3.3.1
Internet Explorer notes for 3.3.1
Opera notes for 3.3.1
Safari notes for 3.3.1
Others notes for 3.3.1

3.3.2 Document Accessibility Features

All features of the user agent that meet User Agent Accessibility Guidelines 2.0 success criteria are documented. (A)

Chrome notes for 3.3.2
Firefox notes for 3.3.2
Internet Explorer notes for 3.3.2
Opera notes for 3.3.2
Safari notes for 3.3.2
Others notes for 3.3.2

3.3.3 Changes Between Versions

Changes to features that meet UAAG 2.0 success criteria since the previous user agent release are documented. (AA)

Chrome notes for 3.3.3
Firefox notes for 3.3.3
Internet Explorer notes for 3.3.3
Opera notes for 3.3.3
Safari notes for 3.3.3
Others notes for 3.3.3

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. (AAA)

Chrome notes for 3.3.4
Firefox notes for 3.3.4
Internet Explorer notes for 3.3.4
Opera notes for 3.3.4
Safari notes for 3.3.4
Others notes for 3.3.4

Guideline 3.4 - The user agent must behave in a predictable fashion.

3.4.1 Avoid unpredictable focus

The user can prevent focus changes that are not a result of explicit user request. (A)

Chrome notes for 3.4.1
Firefox notes for 3.4.1
Internet Explorer notes for 3.4.1
Opera notes for 3.4.1
Safari notes for 3.4.1
Others notes for 3.4.1

3.4.2 Avoid Side Effects of Navigation

The user can move the keyboard focus without causing the user agent to take any further action, other than the presentation of information (e.g. scrolling or pop-ups that do not change the focus or selection). (A)

Chrome notes for 3.4.2
Firefox notes for 3.4.2
Internet Explorer notes for 3.4.2
Opera notes for 3.4.2
Safari notes for 3.4.2
Others notes for 3.4.2

PRINCIPLE 4: Facilitate programmatic access

Guideline 4.1 - Facilitate programmatic access to assistive technology

4.1.1 Platform Accessibility Architecture

The user agent supports a platform accessibility architecture relevant to the operating environment. (A)

Chrome notes for 4.1.1
Firefox notes for 4.1.1
Internet Explorer notes for 4.1.1
Opera notes for 4.1.1
Safari notes for 4.1.1
Others notes for 4.1.1

4.1.2 Name, Role, State, Value, Description

For all user interface components including user interface, rendered content, generated content, and alternative content, the user agent makes available the name, role, state, value, and description via a platform accessibility architecture. (A)

Chrome notes for 4.1.2
Firefox notes for 4.1.2
Internet Explorer notes for 4.1.2
Opera notes for 4.1.2
Safari notes for 4.1.2
Others notes for 4.1.2

4.1.3 Accessible Alternative

If a component of the user agent user interface cannot be exposed through the platform accessibility architecture, then the user agent provides an equivalent alternative that is exposed through the platform accessibility architecture. (A)

Chrome notes for 4.1.3
Firefox notes for 4.1.3
Internet Explorer notes for 4.1.3
Opera notes for 4.1.3
Safari notes for 4.1.3
Others notes for 4.1.3

4.1.4 Programmatic Availability of DOMs

If the user agent implements one or more DOMs, they must be made programmatically available to assistive technologies. (A)

Chrome notes for 4.1.4
Firefox notes for 4.1.4
Internet Explorer notes for 4.1.4
Opera notes for 4.1.4
Safari notes for 4.1.4
Others notes for 4.1.4

4.1.5 Write Access

If the user agent keeps an internal representation of the user content in terms of element structure, relationships between elements, element meaning, or some combination thereof, it must expose this internal representation via an appropriate means (normally by using the platform accessibility architecture or a programmatically available DOM). (A)

Chrome notes for 4.1.5
Firefox notes for 4.1.5
Internet Explorer notes for 4.1.5
Opera notes for 4.1.5
Safari notes for 4.1.5
Others notes for 4.1.5

4.1.6 Expose Accessible Properties

If any of the following properties are supported by the platform accessibility architecture, make the properties available to the accessibility platform architecture: (1) the bounding dimensions and coordinates of onscreen elements (2) font family of text (3) font size of text (4) foreground color of text (5) background color of text. (6) change state/value notifications (7) selection (8) highlighting (9) input device focus (10) direct keyboard commands (A)

Chrome notes for 4.1.6
Firefox notes for 4.1.6
Internet Explorer notes for 4.1.6
Opera notes for 4.1.6
Safari notes for 4.1.6
Others notes for 4.1.6

4.1.7 Timely Communication

For APIs implemented to satisfy the requirements of UAAG 2.0, ensure that programmatic exchanges proceed at a rate such that users do not perceive a delay. (A)

Chrome notes for 4.1.7
Firefox notes for 4.1.7
Internet Explorer notes for 4.1.7
Opera notes for 4.1.7
Safari notes for 4.1.7
Others notes for 4.1.7

Guideline 4.2 - Facilitate programmatic access to nested user agents

4.2.1 Hand-Off Focus

The user agent programmatically notifies any nested user agent(s) (e.g. plug-ins) when active input focus moves to a nested agent. (A)

Chrome notes for 4.2.1
Firefox notes for 4.2.1
Internet Explorer notes for 4.2.1
Opera notes for 4.2.1
Safari notes for 4.2.1
Others notes for 4.2.1

4.2.2 Retrieve Focus

At any time, the user is able to retrieve input focus from a nested viewport (including a nested viewport that is a user agent). (A)

Chrome notes for 4.2.2
Firefox notes for 4.2.2
Internet Explorer notes for 4.2.2
Opera notes for 4.2.2
Safari notes for 4.2.2
Others notes for 4.2.2

4.2.3 Return Focus

At any time, the user agent can retrieve input focus from a nested viewport (including nested viewports that are user agents). (A)

Chrome notes for 4.2.3
Firefox notes for 4.2.3
Internet Explorer notes for 4.2.3
Opera notes for 4.2.3
Safari notes for 4.2.3
Others notes for 4.2.3

PRINCIPLE 5: Comply with applicable specifications and conventions

Guideline 5.2 - Ensure that Web-based functionality is accessible.

5.2.1 Web-Based Accessible (Level A)

User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level ""A"". (A)

Chrome notes for 5.2.1
Firefox notes for 5.2.1
Internet Explorer notes for 5.2.1
Opera notes for 5.2.1
Safari notes for 5.2.1
Others notes for 5.2.1

5.2.2 Web-Based Accessible (Level AA)

User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level ""AA"". (AA)

Chrome notes for 5.2.2
Firefox notes for 5.2.2
Internet Explorer notes for 5.2.2
Opera notes for 5.2.2
Safari notes for 5.2.2
Others notes for 5.2.2

5.2.3 Web-Based Accessible (Level AAA)

User agent user interfaces that are rendered using Web standard technologies conform to WCAG Level ""AAA"". (AAA)

Chrome notes for 5.2.3
Firefox notes for 5.2.3
Internet Explorer notes for 5.2.3
Opera notes for 5.2.3
Safari notes for 5.2.3
Others notes for 5.2.3

Guideline 5.3 - Support accessibility features of technologies.

5.3.1 Implement accessibility features of content specs

Implement and cite in the conformance claim the accessibility features of content specifications. Accessibility features are those that are either * identified as such in the specification or * allow authors to satisfy a requirement of WCAG. (A)

Chrome notes for 5.3.1
Firefox notes for 5.3.1
Internet Explorer notes for 5.3.1
Opera notes for 5.3.1
Safari notes for 5.3.1
Others notes for 5.3.1

5.3.2 Implement Accessibility Features of platform

Implement and cite in the conformance claim the accessibility features of platform technology specifications. Accessibility features are those that are either * identified as such in the specification or * allow authors to satisfy a requirement of WCAG. (A)

Chrome notes for 5.3.2
Firefox notes for 5.3.2
Internet Explorer notes for 5.3.2
Opera notes for 5.3.2
Safari notes for 5.3.2
Others notes for 5.3.2

Guideline 5.4 - Render content according to specification.

5.4.2 Handle Unrendered Technologies

If the user agent does not render a technology, the user can choose a way to handle content in that technology (e.g. by launching another application or by saving it to disk). (A)

Chrome notes for 5.4.2
Firefox notes for 5.4.2
Internet Explorer notes for 5.4.2
Opera notes for 5.4.2
Safari notes for 5.4.2
Others notes for 5.4.2

5.4.3 Alternative content handlers

The user can select content elements and have them rendered in alternative viewers. (AA)

Chrome notes for 5.4.3
Firefox notes for 5.4.3
Internet Explorer notes for 5.4.3
Opera notes for 5.4.3
Safari notes for 5.4.3
Others notes for 5.4.3