University of Colorado at Boulder Web Communications  
University of Colorado CU Home Search A to Z Index Map University of Colorado at Boulder

Web Communications >> Resources >> Creating Accessible Web Pages

Creating Accessible Web Pages

Section 508 Accessibility Standards for Web Sites

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

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

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

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

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

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

(f) 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) Row and column headers shall be identified for data tables.

(h) 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 shall be titled with text that facilitates frame identification and navigation.

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

(k) 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) 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) 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) 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) A method shall be provided that permits users to skip repetitive navigation links.

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

Note to §1194.22: 1. 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:

Note: The following table was adapted from WebABLE The table is an enhanced replication of the table currently located on the Access Board's Section 508 web page. This table includes hyperlinks to the individual 508 requirement, the associated W3C Web Content Accessibility Guideline, and the W3C accessibility coding technique.

Section 1194.22 Paragraph WCAG 1.0 Checkpoint WAI Coding Technique
(a) 1.1 Text equivalents
(b) 1.4 Multimedia equivalents
(c) 2.1 Content not color dependent
(d) 6.1 Content readable without CSS
(e) 1.2 Text links for server-side image maps
(f) 9.1 Use client-side image maps
(g) 5.1 Identify columns and rows in data tables
(h) 5.2 Identify columns and rows in multilevel tables
(i) 12.1 Identify frames with titles
(j) 7.1 Avoid screen flicker
(k) 11.4 Create alternative pages
(l) 6.3,6.4, and 6.5 Functional text for scripts
(m) 11.1 and 11.3 Provide links to accessible plug-ins and applets
(n) 9.4, 9.5, 12.3, and 12.4 Make forms assessable
(o) 6.2 Skip repetitive navigation links
(p)   Provide alerts for timed responses


2. Paragraphs (l), (m), (n), (o), and (p) of this section are different from WCAG 1.0. Web pages that conform to WCAG 1.0, level A (i.e., all priority 1 checkpoints) must also meet paragraphs (l), (m), (n), (o), and (p) of this section to comply with this section. WCAG 1.0 is available at

The complete text of the Electronic and Information Technology Accessibility Standards is available from the Access Board at

University Communications