508 Compliance Checklist

I saw many folks were busy in figuring out proper 508 Compliance. People have understanding what it is, but they are not certain with test cases to verify it. I would like to say there is no hard & fast rule defined to validate 508, but yeah it needs few scenarios to be cover (as per the objective of site / application).

To validate 508 against a site / application we have prepared a basic checklist. Again its not necessary that all checkpoints listed below applicable for all sites; and also its not necessary that these are the only points need to verify for 508. Its a basic checklist which provide us confidence at we are not a failure in 508 compliance. The list varies depends on product.

Kindly find the points below. Hope this will helpful.

Are all functions and user input fields accessible through the keyboard?

Applications shall not disrupt or disable activated features of other products or operating system that are identified as accessibility features.

Is the user made aware of changes to window content when page content changes as a result of active scripting rather than screen refreshing?

Are all application control elements represented by accessible text?

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.

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.

If animation in the form of .gif, .avi, .mpg or other format is used to communicate information, is this information available in an accessible format such as .txt, .htm, .doc, etc.?

When color is used to communicate information, is this information available in different modes?

If the program permits the user to select interface colors does the range of colors available include selections for users with low vision?

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.

Do all forms utilize the Label attribute, are form elements organized logically and consistently?

Do all images have ALT descriptive tags?

If a table is used for page format purposes, can it be read linearly (left to right and top to bottom) by a screen reader?

Applications shall not override user selected contrast and color selections and other individual display attributes.

Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

If a timed response is required, is the user alerted and given sufficient time to indicate more time is required?

Does the document file name not contain spaces and/or special characters?

Is the document file name concise, generally limited to 20-30 characters, and does it make the contents of the file clear?

Does the document utilize recommended fonts (i.e., Times New Roman, Verdana, Arial, Tahoma, Helvetica, or Calibri)?

Has a separate accessible version of the document been provided when there is no other way to make the content accessible?

If there are tables, are blank cells avoided?

Is all of the text easy to read in comparison to the background of the document (i.e., has a color-contrast ratio of 4.5:1)?

Has the document been reviewed in Print Preview for a final visual check?

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.

Do the active worksheets have clear and concise names that allow users (and assistive technology) to identify the table’s source and content?

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.

Do all nontext elements that convey information, including images, have descriptive captions (alternative text does not currently work in Excel)?

Do all charts have titles, legends, and axis labels?

Are row and column headers identified for data tables?

Are documents organized so they are readable without requiring an associated style sheet?

Is there a text equivalent (e.g., via “alt”, “longdesc”, or in element content) for every non-text element?

Is a method provided that permits users to skip repetitive navigation links?

Make sure that screen reading tools can read all the text available and every image with alt-text?

Do product defined keyboard actions, affect accessibility keyboard shortcuts?

Ensure that text can be resized for the users with poor vision.