Web-based Information and Applications VPAT

Standard	Complies (Yes/No/NA)	Describe/Explain
1.1 - Use valid, standard web programming code.
1.2 - Use appropriate markup to convey document structure.
1.3 - Provide meaningful page titles.
1.4 - Use headings to introduce sections and sub-sections, and use them in the correct order.
1.5 - Use lists to identify series of related items, including navigation menus.
2.1 - Use text to display text, unless formatting that cannot be achieved with CSS is required.
2.2 - Use relative sizes for fonts.
2.3 - Identify the language of text.
2.4 - Use images instead of "ASCII art."
3.1 - Do not convey information with color alone.
3.2 - Use contrasting foreground and background colors.
4.1 - Provide appropriate "alternate text" for all images.
4.2 - Provide full descriptions for graphs, diagrams, and other meaningful images.
5.1 - Provide alternate text for each area in client-side image maps.
5.2 - Use client-side image maps instead of server-side image maps unless areas cannot be defined with available shapes.
6.1 - Do not convey information with sound alone.
6.2 - Do not automatically play audio.
6.3 - Provide text transcripts for audio containing speech when it is provided to the public and/or required to be viewed by employees.
7.1 - Provide synchronized captions for all multimedia containing essential auditory information when it is provided to the public and/or required to be viewed by employees.
7.2 - Provide audio descriptions for all multimedia that contains essential visual information when it is provided to the public and/or required to be viewed by employees.
8.1 - Provide a means of pausing any moving, blinking, scrolling, or auto-updating information.
8.2 - Do not include content that flashes faster than 3 times per second.
9.1 - Ensure that links are understandable out of context.
9.2 - Provide a means of skipping past repetitive navigation links.
9.3 - Avoid using small links.
9.4 - Ensure that same-page links move keyboard focus as well as screen focus.
10.1 - Provide labels or titles for all form fields.
10.2 - Provide legends for groups of form fields.
10.3 - Ensure that form fields are in a logical tab order.
10.4 - Avoid placing non-focusable text between form fields.
10.5 - Ensure that text in form fields can be enlarged.
11.1 - Identify a header cell for each column and row in simple data tables.
11.2 - Identify relationships in complex data tables using id and headers attributes.
11.3 - Provide summary attributes for data tables.
12.1 - Provide concise, unique, and understandable titles for frames.
12.2 - Avoid using hidden, empty, or non-essential frames.
13.1 - Ensure that scripted functions are usable with assistive technologies.
13.2 - Ensure that significant interactions can be performed with both keyboard and mouse.
13.3 - Avoid changing focus unexpectedly.
13.4 - Avoid changing content unexpectedly
14.1 - Use accessible embedded objects whenever possible.
14.2 - If an inaccessible embedded object must be used, provide an accessible alternative that includes the same content and functionality.
15.1 - Provide natively accessible downloadable documents whenever possible.
15.2 - If a downloadable document cannot be made natively accessible, provide an accessible alternative that includes the same content and functionality.
16.1 - Notify users of time limits and provide a means to extend time if possible.
16.2 - Do not automatically refresh the current page.
17.1 - When using tables for layout, ensure that reading order is logical.
17.2 - When using style sheets for layout, ensure that reading order is logical.
17.3 - Avoid horizontal scrolling.
18.1 - Use separate accessible versions only as a last resort.

Note: The standards listed above are based on Section 508 Standards for web-based intranet and internet information and applications (§ 1194.22) and the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines (WCAG) 1.0, Priorities 1 and 2.