Here is a list of Section 508 accessibility guidelines, with notes on how IWS meets them in the websites we design and build. We also indicate where our standard practice doesn't (yet) completely meet a guideline, and whether we can add that functionality if a client desires it.
Anyone who does website work for you should be prepared to discuss these accessibility features and how they implement them. You can use this checklist to further investigate any blanket claims that a vendor might make to be '508 compliant.'
A. A text equivalent for every non-text element shall be provided (e.g., via alt, longdesc, or in element content). YES: IWS provides alt description, text description, or adjacent text to all non-text elements such as images.
B. Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. NO: Currently IWS does not provide synchronized captions for audio or video.
C. Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. YES: IWS never uses color as the sole method for identifying screen elements or controls; all information conveyed with color is available without color, for example from context or markup. IWS also addresses the use of color to indicate an action by underlining links in addition to displaying them in a distinctive color.
D. Documents shall be organized so they are readable without requiring an associated style sheet. YES: IWS codes html pages following Semantic xHTML1.0 markup standards and separates presentation, CSS2.1, from page structure.
E. Redundant text links shall be provided for each active region of a server-side image map. YES: IWS does not design websites with image maps.
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. YES: IWS does not design websites with image maps.
G. Row and column headers shall be identified for data tables. YES: IWS builds all data tables with table headers.
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. YES: IWS can add IDs to table cells as needed.
I. Frames shall be titled with text that facilitates frame identification and navigation. YES: IWS does not design websites with frames.
J. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. YES: IWS does not use screen flicker.
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. YES: IWS develops web pages to be accessible to screen readers and text browsers. Also text-only page equivalents can be provided as needed.
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. YES: IWS builds content displayed by scripting languages to be accessible by assistive technologies. Flash interactives are considered on a case-by-case basis; IWS can provide text-only versions for Flash interactives. EXCEPTION: Currently IWS cannot deliver an authoring interface for CommonSpot, the University's standard content-management system, that is accessible to assistive technologies. This is a limitation in the CommonSpot product, and must be addressed by the company that produces it, PaperThin.
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). YES: 1) IWS includes plug-in links on the page for Flash and Quicktime. 2) IWS includes a plug-in link for each page that contains PDFs. 3) IWS can provide media players as standalone if requested by client, as standalone players are “usually more accessible.” This is not a standard but strongly suggested.
EXCEPTIONS: 1) PDF files must be made accessible to screen readers by adding embedded tags or accessible HTML versions. Currently IWS does not embed tags into PDFs. IWS can make HTML versions of PDFs at additional cost. 2) For PowerPoint files, “it is recommended that an accessible HTML version be provided instead of or in addition to the PowerPoint version. ” IWS can make accessible HTML versions of Power Point files at additional cost.
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. YES: IWS passes Section 508 requirements for forms when they are hand-coded forms as labels, fieldsets, and IDs are properly labeled. EXCEPTION: Forms generated by CommonSpot, the University's content-management system, fail as CommonSpot does not label form elements properly.
O. A method shall be provided that permits users to skip repetitive navigation links. YES: IWS includes text links in page headers (which are accessible to screen readers and CSS-disabled browsers) that allow 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. YES: IWS does not design websites with timed responses. However, Flash interactives will require alerts for timed responses or no timed responses.
Additionally, IWS: