General (W3C Priority 1)	Yes	No	N/A
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.	Yes	No	N/A
508 (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).

2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup.	Yes	No	N/A
508 (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).

Yes

No

N/A

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.	Yes	No	N/A
508 (d) Documents shall be organized so they are readable without requiring an associated style sheet.

6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes.

Yes

No

N/A

7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker.	Yes	No	N/A
508 (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

14.1 Use the clearest and simplest language appropriate for a site's content.

Yes

No

N/A

If you use images and maps.
1.2 Provide redundant text links for each active region of a server-side image map.	Yes	No	N/A
508 (e) Redundant text links shall be provided for each active region of a server-side image map.

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.	Yes	No	N/A
508 (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.

If you use tables.
5.1 For data tables, identify row and column headers.	Yes	No	N/A
508 (g) Row and column headers shall be identified for data tables.

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.	Yes	No	N/A
508 (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.

If you use frames.
12.1 Title each frame to facilitate frame identification and navigation.	Yes	No	N/A
508 (i) Frames shall be titled with text that facilitates frame identification and navigation.

If you use applets and scripts.
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.	Yes	No	N/A

If you use multimedia.
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.	Yes	No	N/A

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.	Yes	No	N/A
508 (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

If all else fails.
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.	Yes	No	N/A
508 (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.

Standard (Section 508)	Yes	No	N/A
508 (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	No	N/A
508 (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	No	N/A
508 (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	No	N/A
508 (o) A method shall be provided that permits users to skip repetitive navigation links.	Yes	No	N/A
508 (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.	Yes	No	N/A

General (W3C Priority 2)	Yes	No	N/A
2.2 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].	Yes	No	N/A
3.1 When an appropriate markup language exists, use markup rather than images to convey information.	Yes	No	N/A
3.2 Create documents that validate to published formal grammars.	Yes	No	N/A
3.3 Use style sheets to control layout and presentation.	Yes	No	N/A
3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values.	Yes	No	N/A
3.5 Use header elements to convey document structure and use them according to specification.	Yes	No	N/A
3.6 Mark up lists and list items properly.	Yes	No	N/A
3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation.	Yes	No	N/A
6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page.	Yes	No	N/A
7.2 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).	Yes	No	N/A
7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.	Yes	No	N/A
7.5 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.	Yes	No	N/A
10.1 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.	Yes	No	N/A
11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.	Yes	No	N/A
11.2 Avoid deprecated features of W3C technologies.	Yes	No	N/A
12.3 Divide large blocks of information into more manageable groups where natural and appropriate.	Yes	No	N/A
13.1 Clearly identify the target of each link.	Yes	No	N/A
13.2 Provide metadata to add semantic information to pages and sites.	Yes	No	N/A
13.3 Provide information about the general layout of a site (e.g., a site map or table of contents).	Yes	No	N/A
13.4 Use navigation mechanisms in a consistent manner.	Yes	No	N/A

If you use tables.
5.3 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).	Yes	No	N/A
5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.	Yes	No	N/A

If you use frames.
12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.	Yes	No	N/A

If you use forms.
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.	Yes	No	N/A
12.4 Associate labels explicitly with their controls.	Yes	No	N/A

If you use applets and scripts.
6.4 For scripts and applets, ensure that event handlers are input device-independent.	Yes	No	N/A
7.3 Until user agents allow users to freeze moving content, avoid movement in pages.	Yes	No	N/A
8.1 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.]	Yes	No	N/A
9.2 Ensure that any element that has its own interface can be operated in a device-independent manner.	Yes	No	N/A
9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.	Yes	No	N/A

General (W3C Priority 3)	Yes	No	N/A
4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs.	Yes	No	N/A
4.3 Identify the primary natural language of a document.	Yes	No	N/A
9.4 Create a logical tab order through links, form controls, and objects.	Yes	No	N/A
9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.	Yes	No	N/A
10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.	Yes	No	N/A
11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)	Yes	No	N/A
13.5 Provide navigation bars to highlight and give access to the navigation mechanism.	Yes	No	N/A
13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.	Yes	No	N/A
13.7 If search functions are provided, enable different types of searches for different skill levels and preferences.	Yes	No	N/A
13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc.	Yes	No	N/A
13.9 Provide information about document collections (i.e., documents comprising multiple pages.).	Yes	No	N/A
13.10 Provide a means to skip over multi-line ASCII art.	Yes	No	N/A
14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.	Yes	No	N/A
14.3 Create a style of presentation that is consistent across pages.	Yes	No	N/A

If you use images and image maps.
1.5 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.	Yes	No	N/A

If you use tables.
5.5 Provide summaries for tables.	Yes	No	N/A
5.6 Provide abbreviations for header labels.	Yes	No	N/A
10.3 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.	Yes	No	N/A

If you use forms.
10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.	Yes	No	N/A