Home > Guidelines

In 1998, Congress amended the Rehabilitation Act to require Federal agencies to make their electronic and information technology accessible to people with disabilities. Inaccessible technology interferes with an individual's ability to obtain and use information quickly and easily.

Section 508 was enacted to

  • eliminate barriers in information technology
  • make available new opportunities for people with disabilities
  • encourage development of technologies that will help achieve these goals

The following section lists the tips according to the Section 508 Technical Standards

§ 1194.22 Web-based intranet and internet information and applications.

Note: The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5, 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium.

Source: Section508.gov

(a) A text equivalent for every non-text element shall be provided

A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).

(b) Provide equivalent alternatives for multimedia

Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

(c) Don't rely on color

Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

(d) Check page without a style sheet

Documents shall be organized so they are readable without requiring an associated style sheet.

(e) Provide a text link for every clickable region of an image map

Redundant text links shall be provided for each active region of a server-side image map.

(f) Try to use client-side image maps when possible

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.

(g) Rows and Columns

Row and column headers shall be identified for data tables.

(h) Use table headers for complex tables

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.

(i) Frames

Frames shall be titled with text that facilitates frame identification and navigation.

(j) Avoid flicker

Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

(k) Use a text-only version as a last resort

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.

(l) Scripting languages

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.

(m) Applets, plug-ins, etc

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)

(n) Forms

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.

(o) Skip navigation links

A method shall be provided that permits users to skip repetitive navigation links

(p) Timed responses

When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.