Section 508 and WCAG Sidebar

See legend, notes and disclaimer at bottom of page

1. A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). 1194.22(a)
2. Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). WCAG 1.1 (p1)
3. Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. 1194.22(b)
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. WCAG 1.4 (p1)
5. Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. 1194.22(c)
6. Ensure that all information conveyed with color is also available without color, for example from context or markup. WCAG 2.1 (p1)
7. Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text]. WCAG 2.2 (p2)
8. Documents shall be organized so they are readable without requiring an associated style sheet.1194.22(d)
9. 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. WCAG 6.1 (p1)
10. Redundant text links shall be provided for each active region of a server-side image map. 1194.22(e)
11. Image map: Provide redundant text links for each active region of a server-side image map. WCAG 1.2 (p1)
12. 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. 1194.22(f)
13. Image map: Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. WCAG 9.1 (p1)
14. Row and column headers shall be identified for data tables.1194.22(g)
15. For data tables, identify row and column headers. WCAG 5.1 (p1)
16. 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. 1194.22(h)
17. Tables: For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. WCAG 5.2 (p1)
18. Frames shall be titled with text that facilitates frame identification and navigation. 1194.22(i)
19. Frames: Title each frame to facilitate frame identification and navigation. WCAG 12.1 (p1)
20. Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. 1194.22(j)
21. Until user agents allow users to control flickering, avoid causing the screen to flicker. WCAG 7.1 (p1)
22. A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of these standards, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. 1194.22(k)
23. 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. WCAG 11.4 (p1)
24. 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. 1194.22(l)
25. Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.] WCAG 8.1(p1)
26. 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).1194.22(m)
27. 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. 1194.22(n)
28. Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. WCAG 10.4 (p3)
29. A method shall be provided that permits users to skip repetitive navigation links. 1194.22(o)
30. When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. 1194.22(p)
31. Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). WCAG 4.1 (p1)
32. Ensure that equivalents for dynamic content are updated when the dynamic content changes. WCAG 6.2 (p1)
33. Use the clearest and simplest language appropriate for a site's content. WCAG 14.1 (p1)
34. Scripts: 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. WCAG 6.3 (p1)
35. 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. WCAG 1.3 (p1)
36. When an appropriate markup language exists, use markup rather than images to convey information. WCAG 3.1 (p2)
37. Create documents that validate to published formal grammars. WCAG 3.2 (p2)
38. Use style sheets to control layout and presentation. WCAG 3.3 (p2)
39. Use relative rather than absolute units in markup language attribute values and style sheet property values. WCAG 3.4 (p2)
40. Use header elements to convey document structure and use them according to specification. WCAG 3.5 (p2)
41. Mark up lists and list items properly. WCAG 3.6 (p2)
42. Mark up quotations. Do not use quotation markup [i.e. blockquote]for formatting effects such as indentation. WCAG 3.7 (p2)
43. Ensure that dynamic content is accessible or provide an alternative presentation or page. WCAG 6.5 (p2)
44. Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off). WCAG 7.2 (p2)
45. Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. WCAG 7.4 (p2)
46. Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. WCAG 7.5 (p2)
47. Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. WCAG 10.1 (p2)
48. Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. WCAG 11.1 (p2)
49. Avoid deprecated features of W3C technologies. WCAG 11.2 (p2)
50. Divide large blocks of information into more manageable groups where natural and appropriate. WCAG 12.3 (p2)
51. Clearly identify the target of each link. WCAG 13.1 (p2)
52. Provide metadata to add semantic information to pages and sites. WCAG 13.2 (p2)
53. Provide information about the general layout of a site (e.g., a site map or table of contents). WCAG 13.3 (p2)
54. Use navigation mechanisms in a consistent manner. WCAG 13.4 (p2)
55. Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). WCAG 5.3 (p2)
56. If a table is used for layout, do not use any structural markup for the purpose of visual formatting. (i.e. the th tag) WCAG 5.4 (p2)
57. Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. WCAG 12.2 (p2)
58. 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. WCAG 10.2 (p2)
59. Associate labels explicitly with their controls. WCAG 12.4 (p2)
60. For scripts and applets, ensure that event handlers are input device-independent. WCAG 6.4 (p2)
61. Until user agents allow users to freeze moving content, avoid movement in pages. WCAG 7.3 (p2)
62. Ensure that any element that has its own interface can be operated in a device-independent manner. WCAG 9.2 (p2)
63. For scripts, specify logical event handlers rather than device-dependent event handlers. WCAG 9.3 (p2)
64. Specify the expansion of each abbreviation or acronym in a document where it first occurs. WCAG 4.2 (p3)
65. Identify the primary natural language of a document. WCAG 4.3 (p3)
66. Create a logical tab order through links, form controls, and objects. WCAG 9.4 (p3)
67. Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. WCAG 9.5 (p3)
68. Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. WCAG 10.5 (p3)
69. Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) WCAG 11.3 (p3)
70. Provide navigation bars to highlight and give access to the navigation mechanism. WCAG 13.5 (p3)
71. Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. WCAG 13.6 (p3)
72. If search functions are provided, enable different types of searches for different skill levels and preferences. WCAG 13.7 (p3)
73. Place distinguishing information at the beginning of headings, paragraphs, lists, etc. WCAG 13.8 (p3)
74. Provide information about document collections (i.e., documents comprising multiple pages.). WCAG 13.9 (p3)
75. Provide a means to skip over multi-line ASCII art. WCAG 13.10 (p3)
76. Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. WCAG 14.2 (p3)
77. Create a style of presentation that is consistent across pages. WCAG 14.3 (p3)
78. Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map. WCAG 1.5 (p3)
79. Provide summaries for tables. WCAG 5.5 (p3)
80. Provide abbreviations for header labels. WCAG 5.6 (p3)
81. Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns. WCAG 10.3 (p3)

(Reload this page)

Legend, Notes and Disclaimers: