508 and WCAG - cross reference
| Section 508 Standard §1194.22 Web-based intranet and internet information and applications. |
WCAG 1.0 Checklist my comments or examples |
|---|---|
| (a) A text equivalent for every non text element shall be provided (e.g., via "alt", "longdesc", or in element content.) <img alt="description" /> <img longdesc="url.htm" /> <input type="image" alt="" /> |
P1(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. |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | P1(1.4) For any time based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) 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. | P1(2.1) Ensure 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. | P1(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. P2(3.3) Use style sheets to control layout and presentation. |
| (e) Redundant text links shall be provided for each active region of a server side image map. | P1(1.2) Provide redundant text links 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. | P1(9.1) Provide client side image maps 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. | P1(5.1) For data tables, identify row and column 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. | P1(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. |
| (i) Frames shall be titled with text that facilitates frame identification and navigation. | P1(12.1) Title each frame to facilitate 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. | P1(7.1) Until user agents allow users to control flickering, avoid causing the screen to 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. | P1(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. P1(1.3) Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. |
| (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. | P1(6.3) Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. P1(8.1) Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies. |
| (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). | Get free Acrobat PDF Reader Get free Adobe Flash Player |
| (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. | P2(10.2) Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned. P2(12.4) Associate labels explicitly with their controls. <label for="must_match"></label> <input id="must_match" /> |
| (o) A method shall be provided that permits users to skip repetitive navigation links. | P3(13.6) Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. |
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | |
| <span lang="es"></span> <html lang="en"> |
P1(4.1) Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). P3(4.3) Identify the primary natural language of a document. |
| Simple Measure of Gobbledygook (SMOG) Calculator |
P1(14.1) Use the clearest and simplest language appropriate for a site's content. |
| Section 508 Standard §1194.21 Software applications and operating systems. |
WCAG 1.0 Checklist |
| (a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. | P2(6.4) For scripts and applets, ensure that event handlers are input device-independent. P2(8.1) Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies. P2(9.2) Ensure that any element that has its own interface can be operated in a device-independent manner. P2(9.3) For scripts, specify logical event handlers rather than device-dependent event handlers. |
| (b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer. | |
| (c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that assistive technology can track focus and focus changes. | |
| (d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to assistive technology. When an image represents a program element, the information conveyed by the image must also be available in text. | |
| (e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. | |
| (f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes. | |
| (g) Applications shall not override user selected contrast and color selections and other individual display attributes. | |
| (h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. | |
| (i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | P1(2.1) Ensure that all information conveyed with color is also available without color, for example from context or markup. |
| (j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided. | |
| (k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. | |
| (l) When electronic forms are used, 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. |
