41. Links to Accessible Players

If your product’s accessibility relies on more than the user’s assistive technology and a common Web browser, provide a link to an accessible download location for each add-on (e.g. plugin, player, script).

Rationale

Some technologies are only accessible when used with particular browsers, plugins, players and scripts.

For example, some accessible FLEX UI components require scripts for compatibility with the JAWS screen reader. Even with thorough accessibility coding and testing, JAWS users won’t be able to access the affected UI elements unless the information about the need for the scripts is made available to them.

Technology Specifics

HTML | XHTML | CSS | JavaScript

1. Users who use keyboard access without a screen reader will require a special tool to use headings navigation:
   • the Opera Web browser
     OR
   • the Pearson-sponsored Headings Navigation Firefox Add-on (The add-on is currently in testing. Details will be provided here when the extension is ready.)
2. Otherwise, the tools needed for accessible HTML/XHTML are so well-known that we don’t have to provide the information with our products.

Related Guidelines

508 Web § 1194.22 (m)

When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).