There has been an increased sensitivity to the fact that many Web documents are written using HTML codes that may actually inhibit access.

   A common misconception is that Web accessibility means that a Web document must use minimal design and cater to those with disabilities.  Some have also interpreted accessibility to mean that graphics and multimedia should be avoided.  Neither is the intent. 

   The goal of Web accessibility initiatives is to raise awareness that Web document need to be designed so they are usable for all users, not just those with disabilities.

   Designing documents with accessibility in mind allows the content to reach as many readers as possible, including those with telnet-based browsers, slow connections (including most people outside of North America and Western Europe), and with graphics disabled. Low-end browsers that don't understand constructs such as tables and frames may also restrict access. 

   Here are some additional design considerations which can make a Web document more accessible:

• Use the <ALT> tag to describe the function of all images, photographs and animations.

• Use headings, lists, table summaries, and a clear and consistent page structure to make pages easy to scan.

• Since many people cannot use a mouse, use client-side mapping to provide alternative text for imagemap hotspots.

• Descriptive text for links can improve access for those with vision impairment.  Each link should make sense when read alone.

• Provide captions or transcripts of any audio content. Add text or audio descriptions of any video content.

• Provide alternate content for scripting, applets or plug-ins so important information is not lost when it is unsupported or turned off at the client side.

For More Information:

• W3C Web Accessibility Initiative, WAI QuickTips Reference Card
• WebABLE!
• Trace Research and Development Center

Next:
Future Considerations

Back:
Design Considerations