Accessibility Audit
Excerpt from full accessibility audit of XHTML/CSS Code (testing for 508 and W3C Priority 1 Guidelines is included here).
| Testing status | |
|---|---|
| P | Pass |
| F | Fail |
| U | Untested/Under Development |
| X | Not applicable |
508 Standards
| Standard | Layout 1 (Home Page) | Layout 2 (Section Home) | Layout 3 (Content Page) |
|---|---|---|---|
| (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). | P | P | P |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the | X | X | X |
| (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. | P | P | P |
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. | P | P | P |
| (e) Redundant text links shall be provided for each active region of a server-side image map. | X | X | X |
| (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. | X | X | X |
| (g) Row and column headers shall be identified for data tables. | U (to be tested as part of content audit) | ||
| (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. | U (to be tested as part of content audit) | ||
| (i) Frames shall be titled with text that facilitates frame identification and navigation. | X | X | X |
| (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | P | P | P |
| (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. | X | X | X |
| (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. | X | X | X |
| (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). | X | X | X |
| (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. | P (for site search) | ||
| (o) A method shall be provided that permits users to skip repetitive navigation links. | P (skip navigation link) | ||
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | X | X | X |
WC3 Guidelines
[Please Note: frames, image map, and multimedia standards have been omitted, as they are not used in the pages being evaluated]
[Priority 1]
A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents.
| Wc3 Priority 1 Checkpoint | Layout 1 (Home Page) | Layout 2 (Section Home) | Layout 3 (Content Page) |
|---|---|---|---|
| 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. | P | P | P |
| 2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. | P | P | P |
| 4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). | P (set html lang to en/es as appropriate) | ||
| 6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document. | P | P | P |
| 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. | X | X | X |
| 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. | X | X | X |
| 14.1 Use the clearest and simplest language appropriate for a site's content. | U (to be tested as part of content audit) | ||
| 1.2 /9.1 image maps (N/A) | X | X | X |
| 5.1 For data tables, identify row and column headers. | U (to be tested as part of content audit) | ||
| 5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. | U (to be tested as part of content audit) | ||
| 11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. | X | X | X |