Section 508

Section 508 of the Rehabilitation Act of 1973 requires that Federal agencies' electronic and information technology be accessible to people with disabilities. Many Web designers have adopted these guidelines in an effort to produce Web sites that are accessible to the greatest number of potential users.

The portion of Section 508 that is most relevant to Web accessibility is Web-based Intranet and Internet Information and Applications. It consists of 16 paragraphs, which comprise the requirements for making a page compliant with Section 508 standards:

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 the aforementioned standards.
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.

The following are the ways in which CCCOnline strives to meet these accessibility requirements:

1. Utilize “alt” tag attributes for images, using relevant text.
2. n/a
3. Text that utilizes color for emphasis should incorporate proper structural markup so that the emphasis is still present without using <font> tags. Color should be achieved using style sheets.
4. Use proper structural markup so that pages are still readable without the associated style sheet.
5. n/a
6. n/a
7. Use <th> for data tables.
8. Complex tables require very complex and specific markup. Please inquire about this if needed.
9. n/a
10. Do not use <blink>, or animations that serve no purpose. Limit animation cycles to three.
11. Provide text-versions when needed.
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. Provide descriptions and links for applets and plug-ins.
14. n/a
15. Tabbing between WebCT frames, or hiding the Course Menu.
16. n/a

Other practices that contribute to meeting multiple requirements are:

• Use headings (h1 – h6) to structure pages, making the hierarchy of information clear, much like an outline.
• Use structural elements (strong, em, cite, code, abbr, etc.) instead of presentation elements (b, I, u, font, etc.) Use blockquote for long quotes and not for indenting. Create styles in the style sheet to achieve presentation.