WAI: Strategies, guidelines, resources to make the Web accessible to people with disabilities
Site Navigation: W3C Home > WAI Home > UAWG Home > UAAG Implementations
Examples of each success criteria informally identified by members of the User Agent Accessibility Guidelines Working Group, but not formally tested.
This report from the User Agent Accessibility Guidelines Working Group (UAWG) was initially started in anticipation of implementation testing during an anticipated W3C Candidate Recommendation stage for the User Agent Accessibility Guidelines (UAAG) 2.0.
This report identifies implementations of User Agent Accessibility Guidelines (UAAG) 2.0 success criteria based on informal evaluation of these features in a variety of user agents. Even though this stage of work on UAAG 2.0 concluded with a Working Group Note instead of a W3C Recommendation, the Working Group continued to identify candidate implementations of UAAG 2.0 features, as these may be useful examples for other potential implementers to consider. The more consistent the support of basic accessibility is across browsers, media players, and other user agents, the greater access people with disabilities have to Web content that has been made accessible by conforming to the Web Content Accessibility Guidelines (WCAG) 2.0.
Because the implementations listed below have not been definitively tested, they should not be considered as confirmation of conformance. Those interested in further testing of candidate implementations may be interested in the draft UAAG 2.0 test suite which is publicly available. Please let us know if you have any questions.
If the block is blank, it means that UAWG has not yet discussed it.
Success criteria: 112
Success criteria w/ zero implementations: 3
Success criteria with one implementation: 8
Percentage implemented with two identified examples: 90.1%
See also:
UAAG 2.0 Working Group Note
UAAG 2.0 Reference Working Group Note
UAAG 2.0 Tests for CR Overview
| Success Criteria | Priority | Implementation 1 | Implementation 2 | |
|---|---|---|---|---|
| 16 | 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) Note: It is recommended that the user agent allow the user to choose whether the alternative content replaces or supplements the original content element. |
A | https://www.w3.org/WAI/UA/work/wiki/Appendix_E:_Alternative_Content Abbreviations
ClickToPlugin - safari http://hoyois.github.io/safariextensions/clicktoplugin/ Chrome londesc
|
Image Alt Text Viewer
Firefox - Long Descriptions https://addons.mozilla.org/en-US/firefox/addon/longdesc/
|
| 18 | 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) | A | media players - Youtube player https://www.youtube.com/watch?v=9K4WJs94FfY youtube with captions CC button is not grayed out |
A user stylesheet in any browser supporting user stylesheets: [Greg will send a link to his stylesheet] |
| 19 | 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) | A | images |
|
| 20 | 1.1.4 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 A) Note: Depending on the screen area available, the display of the primary time-based media can need to be reduced in size to meet this requirement. |
A | media player settings A & B. quicktime |
html5 vido caption placement - CSS https://developer.mozilla.org/en-US/Apps/Build/Audio_and_video_delivery/Adding_captions_and_subtitles_to_HTML5_video |
| 22 | 1.1.5 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) | AA | media players let the user choose to display captions with video Extensions that do this: http://www.howtogeek.com/139916/how-to-view-and-disable-installed-browser-plug-ins-in-any-browser/ http://www.howtogeek.com/188059/how-to-enable-click-to-play-plugins-in-every-web-browser/ |
|
| 23 | 1.1.6 Use Configurable Text for Time-based Media Captions: For recognized on-screen alternative content for time-based media (e.g. captions, sign language video), the user can configure recognized text within time-based media alternatives (e.g. captions) in conformance with 1.4.1. (Level AA) | AA | User stylesheet can be used to configure the caption text in any browser that supports user stylesheets
|
User stylesheet can be used to configure the caption text in any browser that supports user stylesheets |
| 24 | 1.1.7 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) Note 1: Depending on the screen area available, the display of the primary time-based media can need to be reduced in size or hidden to meet this requirement. Note 2: Implementation can involve displaying alternative content for time-based media in a separate viewport, but this is not required. |
AAA | youtube - captions on top or bottom of video http://www.whooshtranscription.com/how-to-set-the-position-of-subtitles-on-youtube/ |
vlc player - captions/subtitles https://wiki.videolan.org/Documentation:Subtitles/ |
| 29 | 1.2.1 Support Repair by Assistive Technologies: If text alternatives for non-text content are missing or empty, the user agent doesn't attempt to repair the text alternatives by substituting text values that are also available to assistive technologies (e.g. image file name). (Level AA) | AA | Firefox, Chrome, IE, Opera, Safari | Firefox, Chrome, IE, Opera, Safari |
| 32 | 1.3.1 Distinguishable Highlighting: The user can have the following types of content uniquely highlighted, overriding any values specified by the author: (Level A) a. Selection b. In-page search results c. Active keyboard focus (indicated by focus cursors and/or text cursors) d. Unvisited links e. Visited links |
A | a,b,c,e: Firefox, IE, Opera, Safari; d: extension Opera (Chaals extension) |
|
| 33 | 1.3.2 Highlighting Options: The user can set all of the following characteristics of selection highlighting, overriding any values specified by the author: (Level AA) * Foreground color * Background color |
AA | Firefox, IE, Opera, Safari | |
| 34 | 1.3.3 Highlighting Active Keyboard Focus: The user can set all of the following characteristics of active keyboard focus highlighting, overriding any values specified by the author: (Level AA) * Foreground color * Background color * Border (color, style, and thickness) * Text cursor blink rate |
AA | extension Stylish works on chrome, ff, safari, opera | extension Stylish works on chrome, ff, safari, opera |
| 35 | 1.3.4 Distinguishing Enabled Elements: The user can set all of the following characteristics of enabled element highlighting, overriding any values specified by the author: (Level AA) * Foreground color * Background color * Border (color, style, and thickness) |
AA | Firefox, IE, Opera, Safari - user stylesheets | |
| 36 | 1.3.5 Distinguishing Enabled Elements: The user can set all of the following characteristics for visited links and separately for unvisited links, overriding any values specified by the author: (Level AA) * Foreground color * Underline |
AA | Firefox - settings | IE settings |
| 41 | 1.4.1 Basic text formatting (Globally): The user can globally set all of the following characteristics of visually rendered text content: (Level A) * Text scale with preserved size distinctions (e.g. keeping headings proportional to main font) * Text color and background color, choosing from all platform color options * Font family, choosing from all installed fonts * Line spacing, choosing from a range with at least three values up to at least 2 times the default * Text style, choosing to turn on/off underline, italic, bold |
A | a,b,c - Firefox, IE, Opera, Safari (user style sheets) stylish - https://addons.mozilla.org/en-US/firefox/addon/stylish/?src=search |
stylish - https://chrome.google.com/webstore/detail/stylish/fjnbnpbmkenffdnngjfgmeleoegfcffe |
| 42 | 1.4.2 Basic text formatting (by Element): The user can set all of the following characteristics of visually rendered text content for text element types including at least headings, input fields, and links: (Level AA) * Text size (e.g. 18 point) or scale (e.g. 150%) * Text color and background color, choosing from all platform color options * Font family, choosing from at least all installed fonts * Line spacing, choosing from a range with at least three values * Text style (underline, italic, bold) |
AA | Firefox, IE, Opera, Safari - user style sheet | |
| 43 | 1.4.3 Blocks of text (Globally): The user can globally set all of the following characteristics of visually rendered blocks of text: (Level AA) * Character spacing, choosing from a range with at least 5 values * Justification (left or right, including turning off full justification) * Margins around blocks of text |
AA | Firefox, IE, Opera, Safari - user style sheet | |
| 44 | 1.4.4 Configured and Reflowed Text Printing: The user can print the rendered content, and the following are all true: (Level AA) * any visual, non-time-based, rendered content can be printed * the user can choose between available printing devices * the user can have content printed as it is rendered on screen, reflecting any user scaling, highlighting, and other modifications * the user can have printed content reflow as if the top-level viewports had been resized to match the horizontal dimension of the printing device's printable area |
AA | directions for using the debugger in Chrome to print the rendered view. |
|
| 45 | 1.4.5 Default to platform text settings: The user can specify that platform text settings be used as the default values for text configuration.. (Level AA) | AA | Many examples of high contrast settings carrying over from OS to the browser. But we couldn't find OS text configuration settings that carried over to the browser. May need more research | |
| 46 | 1.4.6 Advanced text formatting: The user can globally set all of the following characteristics of visually rendered blocks of text: (Level AAA) 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. |
AAA | Firefox, IE, Opera, Safari - user style sheet including capitalization, auto-hypenation, borders, word-spacing. | Firefox, IE, Opera, Safari - user style sheet including capitalization, auto-hypenation, borders, word-spacing. |
| 50 | 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) | A | media players (youtube volume is different from global volume) lots of media players do this. what about video tag in html 5 - volume independent of global? | |
| 54 | 1.6.1 Speech Rate, Volume, and Voice: If synthesized speech is produced, the user can specify the following: (Level A) a. Speech rate b. Speech volume (independently of other sources of audio) c. Voice, when more than one voice is available |
A | chrome vox - chromevox - rate, volume, voice | |
| 55 | 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) 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. |
AA | chromevox - pitch only. http://www.chromevox.com/keyboard_shortcuts.html | |
| 57 | 1.6.3 Advanced Speech Characteristics: If synthesized speech is produced, the user can adjust all of the speech characteristics provided by the speech synthesizer. (Level AAA) | AAA | none known | |
| 58 | 1.6.4 Synthesized Speech Features: If synthesized speech is produced, the following features are provided: (Level AA) * User-defined extensions to the synthesized speech dictionary. * "Spell-out": text is spelled one character at a time, or according to language-dependent pronunciation rules. * 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). * At least two ways of speaking punctuation: spoken literally, and with punctuation understood from speech characteristics like pauses. |
AA | all - only for external screen readers. chromevox - read character by character, punctuation - on/off, no exceptions, one way to read numbers, |
|
| 59 | 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) | AA | chromevox - yes | |
| 62 | 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) | A | Firefox, Chrome, IE, Opera, Safari - Authors can have multiple style sheet. Chrome, Firefox-Stylish extension https://chrome.google.com/webstore/detail/fjnbnpbmkenffdnngjfgmeleoegfcffe, https://addons.mozilla.org/en-US/firefox/addon/stylish/ | |
| 63 | 1.7.2 Apply User Stylesheets: If user stylesheets are supported, then the user can enable or disable user stylesheets for: (Level A) a. All pages on specified websites, or b. All pages |
A | a. Chrome, Firefox-Stylish extension https://chrome.google.com/webstore/detail/fjnbnpbmkenffdnngjfgmeleoegfcffe, https://addons.mozilla.org/en-US/firefox/addon/stylish/ for individual sites b. Firefox, Chrome, IE, Opera, Safari can do all pages, |
|
| 64 | 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) | A | Firefox, Chrome, IE, Opera, Safari can do all pages, there are also many extensions the can turn off styles. Current page may be an issue |
|
| 65 | 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) | AA | Firefox, Chrome, IE, Opera, Safari | |
| 68 | 1.8.1 Highlight Viewport: The user can have the viewport with the input focus be highlighted. (Level A) | A | IE provides a focus for frames and other viewports, don't know if you can style the highlight. | |
| 69 | 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) | A | O. this is widely supported through scroll bars on desktop browsers, need to check mobile devices. Safari on IOS has scroll bars |
|
| 70 | 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) | A | although overriding author is not widely implemented, there is usually a way to get around it. | |
| 71 | 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) | A | Firefox, Chrome, IE, Opera, Safari | |
| 72 | 1.8.5 Allow Zoom: The user can rescale content within top-level graphical viewports as follows: (Level A) * Zoom in: to 500% or more of the default size * Zoom out: to 10% or less of the default size, so the content fits within the height or width of the viewport |
A | All zoom, but the user must use Stylish to constrain horizontal scrolling | All zoom, but the user must use Stylish to constrain horizontal scrolling |
| 73 | 1.8.6 Maintain Point of Regard: The point of regard remains visible within the viewport when the viewport is resized, when content is zoomed or scaled, or when content formatting is changed. (Level A) Note: When the point of regard is larger than the viewport, the user agent keeps visible the beginning of the point of regard according to the current language's reading order (e.g. top-left in English) |
A | Chrome | Internet Explorer, Safari |
| 75 | 1.8.7 Customize Viewport Highlighting: When highlighting viewports as specified by 1.8.1 Highlight Viewport, the user can customize attributes of the viewport highlighting mechanism (e.g. color and width of borders). (Level AA) | AA | @@ Firefox highlights frames, no one else. No customizations. FF puts dotted line around viewports.Can use F6 to move between viewports in all major browsers | |
| 76 | 1.8.8 Allow Viewport Resize: The user can resize viewports within restrictions imposed by the platform, overriding any values specified by the author. (Level AA) | AA | youtube player allow resizing per video, as do most other players. Chrome supports this for edit fields, but F does not. New HTML5 form attrib (resize) in Chome, Safari, and Firefox allows changing size of edit field, but no user override. No keyboard access to the resize handle is implemented. No resize available for single line edit box.I wonder who supports it for browser generated dialog boxes (need to find these) letting user override any author settings fixing the window size. 1.8.8 is doable for textarea, video players, frames, and iframes with the mouse. May need the addition of Stylish to add resizability in FF, Safari, Chrome. none have functionality from the keyboard. IE8 does not resize textarea. |
youtube player allow resizing per video, as do most other players. May need the addition of Stylish to add resizability in FF, Safari, Chrome. |
| 77 | 1.8.9 Provide Viewport History: For user agents that implement a history mechanism for top-level viewports (e.g. "back" button), the user can return to any state in the viewport history that is allowed by the content, including: (Level AA) Note: It is recommended that selection also be restored. |
AA | IE maintains point of regard and form content and input focus chrome maintains point of regard and form content but not input focus change - safari maintains point of regard and form content and input focus all tested on https://www.cs.tut.fi/~jkorpela/www/testel.html (plain and simple html)
|
FF maintains point of regard and form content and input focus ff is the only browser to maintain selection highlighting |
| 79 | 1.8.10 Allow Top-Level Viewport Open on Request: The user can specify whether author content can open new top-level viewports (e.g. windows or tabs). (Level AA) | AA | FCIOS | all desktop browsers have a configuration setting for blocking popup window |
| 80 | 1.8.11 Allow Top-Level Viewport Focus Control: If new top-level viewports (e.g. windows or tabs) are configured to open without explicit user request, the user can specify whether or not top-level viewports take the active keyboard focus when they open. (Level AA) | AA | ff Open new windows in a new tab instead and When a link is opened in a new tab, switch to it immediately safari, IE, chrome, no focus control. Note: test pages to popup a window. |
|
| 81 | 1.8.12 Allow Same User Interface: The user can specify that all top-level viewports (e.g. windows or tabs) follow the defined user interface configuration. (Level AA) | AA | Opening applications in a new tab (FCIOS) Especially important for web applications where you log in a separate window, then a new window pops up with no browser user interface, so there are no controls or extensions for accessibility. |
Opening applications in a new tab (FCIOS) |
| 82 | 1.8.13 Multi-Column Text Reflow: The user can specify that recognized multi-column text blocks each be reflowed into a single column. (Level AA) Note: Some layouts may become unusable if author-specified layout is overridden. In this case, the user can turn linearization off and try another strategy. It is recommended that user agents provide a convenient way for the user to turn this behavior on and off. |
AA | Stylish addon for Firefox, Chrome and Safari | Stylish addon for Firefox, Chrome and Safari |
| 84 | 1.8.14 Ignore Fixed Unit Dimensions: The user can have the user agent override author-specified unit dimensions. (Level AA) | AA | Stylish addon for Firefox, Chrome and Safari | Stylish addon for Firefox, Chrome and Safari |
| 85 | 1.8.15 Linearize Content: The user can have recognized content rendered as a single column, overriding author-specified formatting of columns, tables, and positioning. (Level AA) Note: Some layouts may become unusable if author-specified layout is overridden. In this case, the user can turn linearization off and try another strategy. It is recommended that user agents provide a convenient way for the user to turn this behavior on and off. |
AA | Turn off stylesheets FCIOS webdeveloper - firefox - (MIscellaneous menu -> Linearize page) |
Opera - http://help.opera.com/Windows/12.10/en/stylemodes.html Web Developer Toolbar for Chrome: https://chrome.google.com/webstore/detail/yourhere/fkandkgadbpobooanbmiiinlelnhbabm |
| 87 | 1.8.16 Provide Web Page Bookmarks: The user can mark items in a web page, then use shortcuts to navigate back to marked items. The user can specify whether a navigation mark disappears after a session, or is persistent across sessions. (Level AAA) | AAA | Chrome - scroll marker - chrome - https://chrome.google.com/webstore/detail/scroll-marker/jdoinodpdahlmpgmpmhonheidpjhhnid?hl=en Chrome -yourhere placemarker - chrome - https://chrome.google.com/webstore/detail/yourhere/fkandkgadbpobooanbmiiinlelnhbabm |
Safari - canisbos Placemarker - safari http://canisbos.com/placemarker |
| 90 | 1.9.1 Outline View: Users can view a navigable outline of the headings in rendered content that allows focus to be moved to the corresponding element in the main viewport. (Level AA) Note: Note: An outline view might also include other named elements such as document landmarks. |
AA | https://addons.mozilla.org/es/firefox/addon/headingsmap/ http://fae20.cita.illinois.edu/ |
|
| 92 | 1.9.2 Source View: The user can view all source text that is available to the user agent. (Level AAA) | AAA | Firefox, Chrome, IE, Opera, Safari | |
| 95 | 1.10.1 Show Related Elements: The user can access the information from explicitly-defined relationships in the content, including at least the following: (Level AA) (a) calculated accessible name for images (b) calculated accessible name for controls (e.g. form fields, buttons) (c) caption for a table (d) row and column labels for a table cell |
AA | Firefox, Chrome, IE, Opera, Safari | |
| 96 | 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) | AAA | web inspector - chrome https://chrome.google.com/webstore/detail/web-inspector/enibedkmbpadhfofcgjcphipflcbpelf?hl=en | webdeveloper for chrome and opera also |
| 101 | 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) | A | Firefox, Chrome, IE, Opera, Safari - except tooltips for title element, scrolling in overflow (css) elements. | |
| 102 | 2.1.2 Has Keyboard Focus: Every viewport has an active or inactive keyboard focus at all times. (Level A) | A | Firefox, Chrome, IE, Opera, Safari Everyone except some mobile browsers (e.g. Safari for iOS). |
|
| 103 | 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) | A | Firefox, Chrome, IE, Opera, Safari - need more checking | |
| 104 | 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) | A | Everyone does it except the radio button. Does it behave this way because it is specified in HTML5? 2007 wiki page with instructions for that behavior: http://www.w3.org/wiki/RadioButton - should be an example for Meets WCAG by default | Everyone does this for everything except the radio button. |
| 105 | 2.1.5 Follow Text Keyboard Conventions: The user agent follows keyboard conventions for the operating environment. (Level A) | A | Firefox, Chrome, IE, Opera, Safari | |
| 106 | 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) | A | Firefox, Chrome, IE, Opera, Safari, IOS(mac) browsers have no keyboard | |
| 109 | 2.2.1 Sequential Navigation Between Elements: The user can move the keyboard focus backwards and forwards through all recognized enabled elements in the rendered content of the current top-level viewports. (Level A) | A | Firefox, Chrome, IE, Opera, Safari - generally using F6 key | |
| 110 | 2.2.2 Sequential Navigation Between Landmarks: The user can move the keyboard focus backwards and forwards between regions identified by document landmarks. Note: The user agent might also include other regions, such as viewports, in the sequential navigation. |
A | Firefox - https://github.com/matatk/landmarks
|
|
| 112 | 2.2.3 Default Navigation Order: If the author has not specified a navigation order, the user can have the default sequential navigation order be the source order. (Level AA) | AA | Firefox, Chrome, IE, Opera, Safari | |
| 113 | 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) | AA | We know of no examples. It could be implemented using an add-on. |
|
| 116 | 2.3.1 Allow Direct Navigation to Enabled Elements: The user can move keyboard focus directly to any enabled element in the rendered content. (Level AA) | AA | Firefox - mouseless browsing | IE - Accessibility toolbar |
| 117 | 2.3.2 Allow Direct Activation of Enabled Elements: The user can, in a single action, move keyboard focus directly to any enabled element in the rendered content and perform an activation action on that element. (Level AA) | AA | Firefox - mouseless browsing | |
| 118 | 2.3.3 Present Direct Commands from Rendered Content: The user can have any recognized direct commands in rendered content (e.g. accesskey, landmark) be presented with their associated elements (e.g. Alt+R to reply to a web email). (Level AA) | AA | landmarks - https://github.com/davidtodd/landmarks | accesskey - https://chrome.google.com/webstore/detail/xkey-discover-website-key/hhkgjbankdehdhlgpnbhnbeodknolokk |
| 119 | 2.3.4 Present Direct Commands in User Interface: The user can have any direct commands in the UA user interface (e.g. keyboard shortcuts) be presented with their associated user interface controls (e.g. "Ctrl+S" displayed on the "Save" menu item and toolbar button). (Level AA) | AA | Firefox, Chrome, IE, Opera, Safari majority of menu options are assigned keyboard shortcuts | |
| 120 | 2.3.5 Allow Customized Keyboard Commands: The user can remap any keyboard shortcut including recognized author supplied shortcuts (e.g. accesskeys) and UA user interface controls, except for conventional bindings for the operating environment (e.g. arrow keys for navigating within menus). (Level AA) | AA | F add-ons KeyConfig and GreaseMonkey; Opera addons; |
Office allows changing UI keystrokes. |
| 123 | 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) | A | Firefox, Chrome, IE, Opera, Safari | |
| 124 | 2.4.2 Search Direction: The user can search forward or backward in rendered content. (Level A) | A | Firefox, Chrome, IE, Opera, Safari | |
| 125 | 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) | A | Firefox, Chrome, IE, Opera, Safari | |
| 126 | 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) | A | Firefox, Chrome, IE, Opera, Safari | |
| 127 | 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) | AA | for alt text - webdeveloper - firefox - https://chrome.google.com/webstore/detail/yourhere/fkandkgadbpobooanbmiiinlelnhbabm reveal alt then you can search The extension reveals it and then it is searchable. The extension doesn't make it searchable. |
webdeveloper - chrome https://chrome.google.com/webstore/detail/web-developer/bfbameneiokkgbdmiekhjnmfkcnldhhm?hl=en reveal alt then search |
| 131 | 2.5.1 Provide Structural Navigation by Heading and within Tables: The user agent provides at least the following types of structural navigation, where the structure types are recognized: (Level AA) * By heading * By content sections * Within tables |
AA | headingsMap - Firefox https://addons.mozilla.org/en-us/firefox/addon/headingsmap/ landmark nav - Firefox - https://github.com/matatk/landmarks Chrome with ChromeVox add-on provides next/previous navigation through elements of various types. |
scrollbar of content - chrome https://chrome.google.com/webstore/detail/scrollbar-of-contents/cfmkncejaemmcobmaabfigljmnkeecdm |
| 138 | 2.6.1 Allow Persistent Accessibility Settings: User agent accessibility preference settings persist between sessions. (Level A) Note: User agents may have a public access setting that turns this off. |
A | Firefox, Chrome, IE, Opera, Safari | |
| 140 | 2.6.2 Allow Restore All to Default: The user can restore all preference settings to default values. (Level A) | A | Chrome "reset browser", Google Chrome has an option that will reset itself to its default settings. To find this option, open Chrome's menu and select Settings. Perform a search for “reset browser” and you'll see the Reset browser settings button. IE has a button in Settings |
Refresh Firefox - reset add-ons and settings | Firefox Help https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings |
| 141 | 2.6.3 Allow Multiple Sets of Preference Settings: The user can save and retrieve multiple sets of user agent preference settings. (Level AA) | AA | Firefox can do Profiles https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles | Chrome - Browser User Profile (can it be used across one Google ID?) http://www.pcworld.com/article/2089364/how-to-create-and-manage-multiple-user-profiles-in-chrome.html |
| 142 | 2.6.4 Allow Preference Changes from outside the User Interface: The user can adjust any preference settings required to meet the User Agent Accessibility Guidelines (UAAG) 2.0 from outside the UA user interface. (Level AAA) | AAA | All Desktop browsers used to have .ini files in WIndows. Firefox profile files can be changed by expert users. On Mac, Profiles folder under User -> Libraries -> Application Support -> Firefox. There is access from Inside FF Help menu. Stupid Geek Tricks: Hacking the Firefox Profile Data Storage |
Chrome Windows - %LOCALAPPDATA%\Google\Chrome\User Data\ huge folder - not user friendly , but it is possible to edit |
| 143 | 2.6.5 Make Preference Settings Transferable: The user can transfer all compatible user agent preference settings between devices. (Level AAA) | AAA | Transfer the Profile to Another Computer. Close Mozilla Firefox, press "Windows-X" to open the Windows Power User menu and then click "Run" to open the Run utility. Type "%APPDATA%\Mozilla\Firefox\Profiles\" (without the quotation marks) and press "Enter" to open Firefox's Profiles folder. http://smallbusiness.chron.com/transfer-firefox-profile-new-computer-78755.html | chrome - windows - %LOCALAPPDATA%\Google\Chrome\User Data\ huge folder - just transfer the "default" folder |
| 146 | 2.7.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) * 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. * 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). * 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). * Assign Activation Keystrokes or Gestures: The user can choose to view, assign or change default keystrokes or gestures used to activate controls. * Reset: The user has the option to reset the containers and controls to their default configuration. |
AA | a) SHOW: Firefox and IE allow hiding and revealing toolbars and putting them in different orders. b) SIMPLIFY: Firefox allows show and hide, and hide = Simplify. S3 & Menu Wizard extensions c) REPOSITION: FIrefox has reposition in Menu Wizard at the item level https://addons.mozilla.org/en-us/firefox/addon/s3menu-wizard/ d) GESTURES: FIrefox can assign keystrokes with an extension: Customizable Shortcuts https://addons.mozilla.org/en-US/firefox/addon/customizable-shortcuts/ e) RESET: IE and Firefox have a "restore to default" Firefox: "The menu button new fx menu gives you convenient access to your favorite Firefox features. Don't like the default arrangement? It's easy to customize." Customize Your Menus in Firefox http://www.howtogeek.com/howto/6985/customize-your-menus-in-firefox/ "Would you like a way to edit menus and remove the extra entries that you do not use or need? Now you can with the Menu Editor extension for Firefox." Chrome Customize Toolbar: https://support.google.com/toolbar/answer/2392132?hl=en Mercury browser can turn controls on/off but won't allow positioning.
|
a) SHOW: Firefox and IE allow hiding and revealing toolbars and putting them in different orders. Chrome - Proper Menubar - https://chrome.google.com/webstore/detail/proper-menubar/egclcjdpndeoioimlbbbmdhcaopnedkp?hl=en b) SIMPLIFY:IE allows hiding toolbars c) REPOSITION: IE has reposition of toolbars d) GESTURES: Opera keyboard control mapper. Apple has Gesture Wizard on iOS. Safari: Swipe Safari Adds Configurable Gestures to Safari on iPhone http://lifehacker.com/5911935/swipe-safari-adds-tons-of-configurable-gestures-to-safari-on-iphone e) RESET: IE has a "restore to default"
|
| 149 | 2.8.1 Adjustable Time Limits: The UA user interface does not include time limits or at least one of the following is true: (Level A) (a) Turn Off: Users are allowed to turn off the time limit before encountering it; or (b) Adjust: Users are allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or (c) Extend: Users are warned before time expires and given at least 20 seconds to extend the time limit with a simple action (e.g. "press the space bar"), and users are allowed to extend the time limit at least ten times; or (d) Real-time Exception: The time limit is a required part of a real-time event and no alternative to the time limit is possible; or (e) Essential Exception: The time limit is essential and extending it would invalidate the activity; or (f) 20 Hour Exception: The time limit is longer than 20 hours. |
A | For the brower UI, not content UI. Hard to find examples of UI events that time out. Suggest Time Out on Hover on links. Firefox and Chrome don't have timeouts. IE times out in 5 seconds on hover on link (failure). FIrefox has no timeouts No examples of customized timeouts, but 2 examples with no timeouts is sufficient for implementations. |
Chrome has no timeouts |
| 152 | 2.9.1 Three Flashes or Below Threshold: In its default configuration, the user agent does not display any UA 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) | A | All browsers pass. No examples of flashing UI. | All browsers pass. No examples of flashing UI. |
| 153 | 2.9.2 Three Flashes: In its default configuration, the user agent does not display any UA 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) | AAA | All browsers pass. No examples of flashing UI. | All browsers pass. No examples of flashing UI. |
| 156 | 2.10.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) | A | Chrome: native Open Plug-in On Request |
Safari Firefox Options -> Applications allows option of Always Ask.
|
| 157 | 2.10.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) | A | Firefox shows placeholder when "Always Ask" is selected | Also Chrome and Safari automatically show placeholder. |
| 158 | 2.10.3 Execution Toggle: The user can turn on/off the execution of dynamic or executable content (e.g. Javascript, canvas, media). (Level A) | A | Firefox extension: NoScript | Safari (native): execution toggle by site |
| 159 | 2.10.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) * Playback Rate: The user can adjust the playback rate of the time-based media tracks to between 50% and 250% of real time. * Pitch: Speech whose playback rate has been adjusted by the user maintains pitch in order to limit degradation of the speech quality. * Synchronization: Audio and video tracks remain synchronized across this required range of playback rates. * Reset: The user agent provides a function that resets the playback rate to normal (100%). |
AA | Accessible media players: BBC Player, JW Player, VLC, OzPlayer Adjustable playback rate is built into HTML5. How to enable in YouTube: http://lifehacker.com/5491852/enable-variable-speed-playback-in-youtube BBC Player: BBC player Html5 Youtube Video Speed Controller :: Add-ons for Firefox https://addons.mozilla.org/en-uS/firefox/addon/youtubevideospeedcontroller/ "Html5 Youtube Video Speed Controller helps to change the playback speed of html5 video on youtube." Enounce MySpeed Player https://www.raymond.cc/blog/download/did/2987/ |
Chrome: https://chrome.google.com/webstore/detail/video-speed-controller/nffaoalbilbmmfgbnbgppjihopabppdk?hl=en Learning API http://www.learningapi.com/2012/04/variable-speed-playback-html5-video-feature/
|
| 160 | 2.10.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) | A | IE supports this by hitting Escape to stop recognized animation. | Toggle animated GIFs :: Add-ons for Firefox https://addons.mozilla.org/en-us/firefox/addon/toggle-animated-gifs/ Firefox intentionally disabled the ability to stop animated gifs in 2012. 825486 – Escape no longer stops animated GIFs https://bugzilla.mozilla.org/show_bug.cgi?id=825486. [Insert insulting term here.] |
| 161 | 2.10.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) | A | All major players do this: Quicktime, Real and Windows Media player, JWPlayer, YouTube, Oz Player, and Paypal player. All of these allow relative units (5, 10, 15, 20, 30 seconds). | All major players do this: Quicktime, Real and Windows Media player,JWPlayer, YouTube |
| 162 | 2.10.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) | AA | Quicktime, JWplayer | Youtube allows nav by chapter (section) they are highlighted in the timeline(sample https://www.youtube.com/watch?v=O8Ja4u8_RGQ) |
| 163 | 2.10.8 Video Contrast and Brightness: Users can adjust the contrast and brightness of visual time-based media. (Level AAA) | AAA | Quicktime, REAL, VLC and WMP stand alone players (VLC -> http://www.addictivetips.com/windows-tips/15-features-of-vlc-player-that-you-probably-dont-know-about/) | Quicktime, REAL, VLC and WMP stand alone players |
| 166 | 2.11.1 Platform Text Input Devices: If an input device is supported by the platform, all user agent functionality including text input can be operated using that device. (Level AA) | A | Braille keyboard, onscreen keyboards, onscreen keyboards all work on all major browsers. On mobile iOS see: https://support.apple.com/kb/PH13833?locale=en_US | All major desktop browsers. |
| 172 | 3.1.1 Text Entry Undo: The user can reverse recognized text entry actions prior to submission. (Level A) 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. |
A | All desktop browsers support (Chrome, IE, Firefox, Safari). Not on mobile at this time. | Chrome, IE, Firefox, Safari |
| 174 | 3.1.2 Settings Changes can be Reversed or Confirmed: If the user agent provides mechanisms for changing its user interface settings, it either allows the user to reverse the setting changes, or the user agent can require user confirmation to proceed. (Level A) | A | IE has reset, FIrefox has refresh which removes all extenstions sets browser to default settings | Chrome has reset. |
| 175 | 3.1.3 Retrieval Progress: By default, the user agent shows the state of content retrieval activity. (Level A) | A | Firefox, Chrome, IE, Opera, Safari | Chrome |
| 176 | 3.1.4 Spell Check: The user can have spelling assistance for editable text in rendered content. (Level AA) | AA | FF checks spelling in 'area' but not in type="text" | Safari on OS X has both spell-checking and auto-correct, in both multi-line and single-line input fields. |
| 177 | 3.1.5 Back Button: The user can reverse recognized navigation between web addresses (e.g. standard "back button" functionality). (Level AA) | AA | All Browsers | All Browsers |
| 178 | 3.1.6 Form Submission Confirm: The user can specify whether or not recognized form submissions must be confirmed. (Level AA) | AA | None Known | |
| 179 | 3.1.7 Form Auto-Fill: The user can have the following information stored and used to auto-fill form fields by request: (Level AA) (a) user's name (b) user's email address (c) user's phone number |
AA | Firefox | Chrome |
| 180 | 3.1.8 Save Form Entries: If the user agent provides a feature to save local versions of web content, then any form fields the user has filled retain any entries in the saved version. (Level AA) | AA | Firefox - Form History Control | Chrome - Lazarus From Recovery |
| 183 | 3.2.1 Accessible Documentation: Product documentation is available in a format that meets success criteria of WCAG 2.0 level "A" or greater. (Level A) | A | All browsers | Puffin (mobile) |
| 184 | 3.2.2 Describe Accessibility Features: For each user agent feature that is used to meet UAAG 2.0, at least one of the following is true: (Level A) (a) Described in the Documentation: Use of the feature is explained in the user agent's documentation; or (b) Described in the Interface: Use of the feature is explained in the UA user interface; or (c) Platform Service: The feature is a service provided by an underlying platform; or (d) Not Used by Users: The feature is not used directly by users (e.g., passing information to a platform accessibility service). |
A | Note: we did not test every browser feature to document implementation Firefox Documentation |
Chrome Documentation |
| 185 | 3.2.3 Document All Features: For each user agent feature, at least one of the following is true: (Level AA) (a) Described in the Documentation: Use of the feature is explained in the user agent's documentation; or (b) Described in the Interface: Use of the feature is explained in the UA user interface; or (c) Platform Service: The feature is a service provided by an underlying platform; or (d) Not Used by Users: The feature is not used directly by users (e.g., passing information to a platform accessibility service). |
AA | Note: we did not test every browser feature to document implementation Firefox Documentation |
Chrome Documentation |
| 186 | 3.2.4 Changes Between Versions: Changes to features that meet UAAG 2.0 success criteria since the previous user agent release are documented. (Level AA) | AA | chrome: log of all revisions by version | Firefox changelogs for each version |
| 187 | 3.2.5 Centralized View: There is a dedicated section of the documentation that presents a view of all features of the user agent necessary to meet the requirements of User Agent Accessibility Guidelines 2.0. (Level AAA) | AAA | Documentation of accessibility features in Firefox | chrome accessibility features for all products (chrome listed on the page) |
| 190 | 3.3.1 Avoid Unpredictable Focus: The user can prevent focus changes that are not a result of explicit user request. (Level A) | A | greasemonkey or something similar for IE, Chrome, Safari, FF is a possible solution. No other implementation or extensions were found. | |
| 195 | 4.1.1 Support Platform Accessibility Services: The user agent supports relevant platform accessibility services. (Level A) | A | Chrome, IE, Firefox, Safari | Chrome, IE, Firefox, Safari |
| 196 | 4.1.2 Expose Accessible Properties: For all user interface components (including UA user interface, rendered content, and generated content) the user agent makes available the following properties and any change notifications via a platform accessibility service(Level A)
|
A | Chrome, IE, Firefox, Safari support all except selection. Need further investigation on selection | |
| 197 | 4.1.3 Provide Equivalent Accessible Alternatives: If UA user interface functionality cannot be exposed through platform accessibility services, then the user agent provides equivalent functionality that can be exposed through the platform accessibility service. (Level A) | A | All Browsers - if the user agent has no custom controls it passes by default. | |
| 198 | 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) | A | all major browsers (except EDGE) on desktops provide some access to DOMs that are being used by assistive technologies. | |
| 199 | 4.1.5 Make Content Interaction Programmatically Available: If the user can interact with content (e.g. by checking a box or editing a text area), the same degree of interaction is programmatically available. (Level A) | A | we assume based on group experience and comments from AT folks that desktop browsers do this. Seems not available on mobile browsers. | |
| 204 | 5.1.1 Comply with WCAG: Web-based UA user interfaces meet the WCAG 2.0 success criteria. (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; and Level AAA to meet WCAG 2.0 Level A, AA, and AAA success criteria) Note: This success criterion does not apply to non-web-based UA user interfaces, but does include any parts of non-web-based user agents that are web-based (e.g. help systems). However, it is recommended that developers of non-web-based user agent user interfaces follow the Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) . |
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 | Exceeds available resources to test individual user agents for WCAG. | |
| 206 | 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): Note 1: If a conformance claim is filed, cite the implemented specifications in the conformance claim. Note 2: When a rendering requirement of another specification contradicts a requirement of UAAG 2.0, the user agent can disregard the rendering requirement of the other specification and still satisfy this guideline. |
A | See: http://caniuse.com/ and http://html5accessibility.com/ According to HTML5Accessibility.com Chrome & Opera are at 94.5% and Firefox 91% |
According to HTML5Accessibility.com Chrome & Opera are at 94.5% and Firefox 91% |
| 209 | 5.1.3 Implement Accessibility Features of the Platform: If the user agent contains non-web-based user interfaces, then those non-web-based user interfaces follow user interface accessibility guidelines for the platform. (Level A) | A | Internet Explorer on Windows | Safari on Macintosh |
| 210 | 5.1.4 Allow Content Elements to be Rendered in Alternative Viewers: The user can select content elements and have them rendered in alternative viewers. (Level AA) | AA | PDF can be rendered in the browser or an alternative viewer All major browsers and most mobile browsers |
PDF can be rendered in the browser or an alternative viewer All major browsers and most mobile browsers |
| 211 | 5.1.5 Enable Reporting of User Agent Accessibility Faults: The user agent provides a mechanism for users to report user agent accessibility issues. (Level AAA) | AAA | See https://www.paciellogroup.com/blog/2014/06/filing-bugs/ Microsoft Disability Answer Desk Microsoft Edge Feedback & Reporting menu option |
Chrome has Help -> Report an Issue |
Based on "ED-UAAG20-20150402-SC.txt" dated Thu Apr 2 09:59:34 2015 (W3C WAI UAAG 2.0 format).
Skip to Content 