Section 508 of the US Rehabilitation Act. Check List

Section 508 is a part of the Rehabilitation Act of 1973 amended in 1998 through the Workforce Investment Act. It requires that electronic and information technology developed, procured, maintained or used by the federal government to be accessible to people with disabilities. The Electronic and Information Technology Accessibility Standards promulgated by the U.S. Access Board provide the accessibility requirements for mainstream technology. These federal requirements are codified in California Government Code 11135.

Section 508 Web Accessibility Basic Checklist (greater detail below this)

• Link needs to be descriptive (not click here)
• Links need to be meaningful, short and relevant to the specific topic.
• The letters (PDF) or (Video) need to be in the link text.
• Use the list tool to make lists
• Explain all graphics if they are informational in nature.
• All video must include a transcript or have close captioning
• Ensure color contrast in images and graphics
• Ensure color is not the sole means of communication indicating selection or indicating and error message.
• Ensure that all java applets, flash files, video files, audio files, plug-ins, etc. have an equivalent alternative or text description.
• Ensure that all PDFs are accessible before posting/ Replace existing PDFs with accessible ones or remove from sites.
• Ex: PDFs can not be scans
• PDFs are for maps and publications. Not fact sheets or lists. Make a web page for those.
• All pages must include a title
• Power point files are not accessible.

Section 508 Web Accessibility Advanced Checklist (mostly used when doing your own coding)

Subpart B of Section 508 outlines the following standards for “Web-based intranet and Internet information and applications:” (The WCAG 1.0 checkpoint that was that spurred the standard is included in parentheses.)

1. A text equivalent for every non-text element shall be provided (e.g., via “alt,” “longdesc,” or in element content. (WCAG 1.0 checkpoint 1.1)
2. Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. (WCAG 1.0 checkpoint 1.4)
3. Web pages shall be designed so that all information conveyed with color is also available without color, for example, from context or markup. (WCAG 1.0 checkpoint 2.1)
4. Documents shall be organized so that they are readable without requiring an associated style sheet. (WCAG 1.0 checkpoint 6.1)
5. Redundant text links shall be provided for each active region of a server-side image map (WCAG 1.0 checkpoint 1.2)
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. (WCAG 1.0 checkpoint 9.1)
7. Row and column headers shall be identified for data tables. (WCAG 1.0 checkpoint 5.1)
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. (WCAG 1.0 checkpoint 5.2)
9. Frames shall be titled with text that facilitates frame identification and navigation. (WCAG 1.0 checkpoint 12.1)
10. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. (WCAG 1.0 checkpoint 7.1)
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 any other way. The content of the text-only page shall be updated whenever the primary page changes. (WCAG 1.0 checkpoint 11.4)
12. When pages utilize scripting languages to display content, or o create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. (no WCAG 1.0 checkpoint)
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 above statutes]. (no WCAG 1.0 checkpoint)
14. When electronic forms are designed to be completed online, 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. (no WCAG 1.0 checkpoint)
15. A method shall be provided that permits users to skip repetitive navigation links. (no WCAG 1.0 checkpoint)
16. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. (no WCAG 1.0 checkpoint)

Further Reading

• Creating Accessible Images (offsite link)
• YouTube auto-timing and auto captions for video transcripts (offsite link)
• In depth information on creating Accessible PDF documents (PDF)
• Software that helps you see how things are displayed on different screens (offsite link)
• Guidelines for Accessible Distance Education (offsite link)
• Cynthia says is a web accessibility checker. Just past the address in to see a report (offsite link)
• How to prepare a Word Doc as an accessible PDF (PDF)

Greater detail

Below is an embedded spreadsheet that is updated every five minutes as changes in the document happen. It outlines in greater detail the points mentioned above. Please review the items below and email the web administrator if anything below seems unclear or would like a review of what you have done so far.