Main Content

Basic Guidelines for Designing Accessible Web Pages

The World Wide Web Consortium (W3C) has created a set of guidelines to help web authors create web pages that make the Internet accessible to all. Allegany College of Maryland encourages web authors to design pages that meet the minimum standards set forth in the W3C Web Accessibility Initiatives. W3C's Web Content Accessibility Guidelines can be found at .

  1. Provide alternate text for all images and image maps in your document. The syntax for including alternate text is: alt=""
  2. The same alt syntax can be used in client-side image maps to provide alternate text for each link area in the image. Be sure that the text provides an adequate description of the link's target for a user who may be relying on a screen reader or other assistive technology to read the page.
  3. Identify row and column headers in tables. This can be accomplished by use of the , and tags, which separate table headers from table data. For example:

    Job Chart
    Name Monday Tuesday
    Trip dinner dishes take out trash
    Sally dust living room dinner dishes

    The code for this will look something like this:

    The HTML 4.0 table tags allow data to be associated with a specific header and for multiple columns to be grouped together. If you are creating complex tables in HTML, it is advisable to consult an HTML 4.0 reference book and the W3C guidelines for advice on how to create accessible data tables. Note that the W3C recommends that the use of tables purely for screen formatting be kept to a minimum.
  4. If you use Cascading Style Sheets in your page, be sure that the page organization will still be coherent when it is viewed by a browser or screen reader that does not support CSS.
  5. Be sure that the text and background colors provide sufficient contrast. Consider that color-blind readers may have difficulty distinguishing text and background colors.
  6. Provide titles for each document frame in a frame set.
  7. Provide text descriptions for all multimedia content, scripts, ascii art, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
  8. Do not cause the screen to flicker.
  9. If all else fails, present the user with the option to view a text-only page.