 |
Page History
...
Ways to Test Your Output | For more information, see |
|---|---|
Refer to the HHS accessibility checklists. | |
In ePublisher, run the accessibility report. Ignore errors about missing long descriptions and table summaries. If you use alternate text for graphics and include either a text introduction or caption for tables, you're covered on those. | |
Download the WAVE Firefox toolbar and view the help in Text-only view. | |
Download an evaluation copy of JAWS and read the document out loud. | |
Use the Adobe Read Out Loud feature to simulate what it would be like for other assistive technology (such as JAWS) to read your PDFs out loud. |
|
Turn off your monitor when you use either JAWS or Adobe Read Out Loud (this takes some practice with each tool) to simulate what it is like not to see what you are doing. |
|
Tab through the output to make sure that the reading order is logical. |
|
The Problem with Automated Tools
Credit for the content of the following two sections goes this section belongs to WebAIM.
...
In the same ways in which we don't always accept the results of a spell and grammar check (or they don't catch the real errors we have because words are spelled correctly), web accessibility requires more than just accessibility tools; it requires human judgment. All accessibility tools vary slightly in their interpretation of WCAG 1.0 and Section 508, and depending on the interpretation, accessibility tools can give users some automated results that require human judgment.
...
Accessibility Tools Need Human Judgment
Credit for the content of the this section belongs to WebAIM.
It is important to remember that accessibility tools can only partially check accessibility through automation. Of the sixteen standards in Section 508, only seven standards can be partially evaluated automatically. Similarly, of the combined 65 checkpoints in WCAG 1.0 Priority 1 through Priority 3, only nineteen can be partially evaluated automatically. The real key is to learn and understand the web accessibility standards rather than relying on a tool to determine if a page is accessible or not.
...
