- 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.

Extensions needed for Implementation Examples

From WAI UA Wiki
Jump to: navigation, search

UAAG 2.0 has success criteria (SC) that are in need of implementations in the form of browser extensions. Please list any SC (with wording) for which you have found an extension(s) that can be used as an implementation example to meet the SC.


Contents

1.1.1 Render Alternative Content: For any content element, the user can choose to render any types of alternative content that are present. (Level A)

1.1.2 Configurable Alternative Content Defaults: For each type of non-text content, the user can specify a type of alternative content that, if present, will be rendered by default. (Level AA)

1.1.3 Display of Time-Based Media Alternatives: For recognized on-screen alternatives for time-based media (e.g. captions, sign language video), the following are all true: (Level AA)

1.1.4 Default Rendering of Alternative Content (Enhanced): For each type of non-text content, the user can specify the cascade order in which to render different types of alternative content when preferred types are not present. (Level AAA)

1.1.5 Size and Position of Time-Based Media Alternatives: The user can configure recognized on-screen alternatives for time-based media (e.g. captions, sign language video) as follows: (Level AAA)

1.2.1 Support Repair by Assistive Technologies: If text alternatives for non-text content are missing or empty then both of the following are true: (Level AA)

1.2.2 Repair Missing Structure: The user can specify whether or not the user agent should attempt to insert the following types of structural markup on the basis of author-specified presentation attributes (e.g.. position and appearance): (Level AAA) [labels and headers]

1.3.1 Highlighted Items: The user can specify that the following classes be highlighted so that each is uniquely distinguished: (Level A) a) selection b) active keyboard focus (indicated by focus cursors and/or text cursors) c) recognized enabled input d) elements (distinguished from disabled elements) e) elements with alternative content f) recently visited links

1.3.2 Highlighting Options: When highlighting classes specified by 1.3.1 Highlighted Items, the user can specify highlighting options that include at least: (Level AA) a) foreground colors, b) background colors, and c) borders (configurable color, style, and thickness)

1.4.1 bullet 4 change line spacing. Stylish - line height 200%, Greasemonkey. Advanced users could use "inspect element" to change the css.

  • 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. (Level A)
    • Excesskey - allows for reconfiguration of accesskeys to match what the user finds helpful

https://addons.opera.com/en/addons/extensions/details/excesskey/

    • xkey - Make browsing more productive - Discover web accessibility shortcuts

https://github.com/startupjockey/xKey

extensions that need an SC home

  • TellMeMore - provides indication that longdescs are available, and shows them associated to thumbnails

https://addons.opera.com/en/addons/extensions/details/tellmemore/

  • Cleanpages - improves the readability by de-cluttering the page

https://addons.opera.com/en/addons/extensions/details/cleanpages/

  • MouseTrail - puts a trail behind the mouse to aid in finding it

https://addons.opera.com/en/addons/extensions/details/mouse-trail/

  • BusComplete - auto completion for text entry

https://addons.opera.com/en/addons/extensions/details/buscomplete/

  • Greyed - reduces contrast by making white background grey (there are people who want this and with high contrast as the most beneficial default, it's a helpful option)

https://addons.opera.com/en/addons/extensions/details/grayed/

  • KeyTitle - makes title attributes show up when navigating by keyboard

https://addons.opera.com/en/addons/extensions/details/key-title/

  • Switch Accessible Puzzles' for iPad -

It has robust switch options and features https://itunes.apple.com/us/app/switch-accessible-puzzles/id562623287?ls=1&mt=8

  • Caret browsing - chrome - google accessibility extension
    • bubble cursor - chrome - With the bubble cursor you can click on links and type inside text fields just by having your cursor near them.

http://bubblecursor.com/


  • ARIA Landmark navigation by keyboard - Firefox

https://github.com/davidtodd/landmarks

Retrieved from "https://www.w3.org/WAI/UA/work/wiki/index.php?title=Extensions_needed_for_Implementation_Examples&oldid=949"