HTML Accessibility

There are a number of accessibility initiatives on the web. The U.S. government has issued a set of guidelines known as Section 508. A part of Section 508 pertains to web design. Although government agencies are required to follow the Section 508 guidelines, many accessibility proponents consider them inadequate.

Another commonly used accessibility resource on the web is the Web Content Accessibility Guidelines 1.0. This initiative is part of the World Wide Web Consortium. These guidelines can be quite helpful for planning and converting web sites.

An automated accessibility checker named Bobby is available online. It is configurable to some degree and can quickly check a web page for conformance to various guidelines such as are found in Section 508.

One thing that is important to remember is that accessibility is also an issue for people without severe handicaps. Mild color-blindness, reduced vision, and slow internet access are very common problems. The number one accessibility issue is often considered to be excessively long download times. These are all issues which should be considered when designing a web site.

Web Resources

Section 508 guidelines

  1. A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
  2. Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
  3. Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
  4. Documents shall be organized so they are readable without requiring an associated style sheet.
  5. Redundant text links shall be provided for each active region of a server-side image map.
  6. Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
  7. Row and column headers shall be identified for data tables.
  8. Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
  9. Frames shall be titled with text that facilitates frame identification and navigation.
  10. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
  11. A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
  12. When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.
  13. 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).
  14. When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
  15. A method shall be provided that permits users to skip repetitive navigation links.
  16. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.


Previous: HTML Image Maps

Next: HTML Software


© 2003, David G. Klick Last modified