Cyber-Sierra Workshop 2002: Accessible Webs

Accessibility Checkpoints

|  Index |  Tools |  WYSIWYG |  Checkpoints |  MarkUp | 

 

The Center for Academic Computing has created this Web Accessibility Checklist which I have modified for this workshop. In order to use most accessibility checklists effectively, you will need to have some knowledge of HTML. If you are not familiar with HTML, look for these items as properties of various page elements in your WYSIWYG editor.

1. If you use images, use the ALT tag to provide a clear text alternative.
Descriptive ALT text should let the user know what an image is and the purpose of that image.

2. If you use charts or graphs, provide a text alternative.
Summarize the content of each chart or graph, or use the longdesc attribute.

3. If you use motion or animation, make sure that it's necessary.
If it is, be sure to provide an alternate text description that clearly communicates the action and its purpose. Don't use blinking animations.

4. If you use tables, be sure they make sense when read left to right, top to bottom.
This is how a screen reader will read them.

5. If you use lists, use ordered lists so that items are numbered.
Or include the item number within your text.

6. If you use frames, clearly title each frame.
Use the TITLE attribute to facilitate navigation and frame identification.

7. If you use forms, clearly associate form labels with their elements
Place them immediately above or to the left of the element.

8. If you use on-line chat and discussion or e-mail, remember to describe art. Any ASCII art, attachments or audio/visual files should be referenced and described.

9. If you use mathematical or scientific notation as a graphic include ALT text
Accurately "reads" describe the notation.

10. If you use scripts or applets, make sure the pages retain their full meaning
Test the page with scripts turned off and in browsers that don't support scripts. If a page does lose its meaning without a script, provide a way to compensate for it.

Sorry, your browser doesn't support Java(tm).

11. If you use plug-ins or PDF files, include a text alternative.
Sites that provide downloadable plug-ins may not be accessible.

12. If you use audio or video files, provide a description/transcript in text form.
It can be on the same page, or a hyperlink to a separate page can be placed near the clip.

13. If you use multiple languages, provide an audio alternative
Each clip should have an alterntive and use the LANG attribute for screen readers that support it.

14. Verify your page's accessibility
Use tools like IBM Home Page Reader and Bobby. Review the site with images and sounds turned off. When all else fails, provide a link to a text-based alternative page.

Reference Sites:

WebAIM Center

Web Accessibility In Mind Center has extensive articles, checklists and tutorials that will help you modify your site to make it most accessible.
 

WebAIM's Checklist

Available online or as a downloadable PDF file, WebAIM's checklist is an excellent table for identifying potential problem areas during web site creation.
 

IBM Web accessibility checklist

Techniques pages, accessed via the link in each checkpoint, may contain more recent updates.
 

WORKSHOPS: |  E-Mail and Outreach |  Web 101 |  Building Accessible Webs |  Web Security | 

Workshops Location: http://www.cyber-sierra.com/workshops/
2002 copyright © Cyber-Sierra.Com, on-line since 1997