Accessibility Checklist

Checklist for webpages

Does the web address not contain聽spaces and/or special characters?
Is the web address聽short, descriptive and contain lowercase letters?
Are heading styles organized in a hierarchal and logical fashion, with聽consecutive headings聽(i.e., no missing heading levels)?

Is the聽list style聽being used as opposed to manually typed characters (e.g. Hyphens, numbers, or graphics)?
Is content聽?
Do all URLs contain聽descriptive hyperlinks聽(i.e., avoid generic phrases like "Click here" and, instead, use phrases that let users know about the content of the linked page prior to selecting it)?
Is the聽聽between foreground text and background color sufficient?

Do all聽, grouped images, and聽聽that convey information have meaningful聽alternative-text descriptions?
Do complex images (i.e., charts and graphs) have聽聽near the image (perhaps as a caption or long description)?
Is the document free of聽聽(i.e., avoid text content contained in images that disappear when images are not available)?
If color is used to emphasize important text, is there is an聽聽used as well?
Have you provided alternatives for or avoided use of聽聽(e.g., shape, size, color, visual location, orientation, sound, etc.)?

Do all data tables have聽proper titles, captions, column headers and/or row headers?
For tables containing data, is there an聽聽used to explain the meaning of the table if it is not otherwise evident from context?

Has the site been checked for accessibility by the聽Accessibility Network?
Has a separate聽聽been provided when there is no other way to make the content accessible?
Did you use the聽聽on any electronic documents, has that been run and does it pass?
础谤别听links provided聽to any special readers or plug-ins that are required to interpret page content?

Does the application provide聽聽instructions for use of all keyboard functions as part of the user documentation?
Does the software provide聽聽for all mouse actions, including buttons, scroll windows, text entry fields, and pop-up windows?
Does the software have a聽聽among fields, text boxes, and focal points?
Can you use聽聽through a list followed by pressing the ENTER key or space bar to select the desired item?
础谤别听聽provided for all pull-down menus?

If timed responses are present, does the software allow the user to聽modify the length of required timed responses?
Does the software application聽聽that the user has defined for accessibility?
Does every window, object, and control have a聽听辫辞蝉颈迟颈辞苍别诲听?
Does the software application use聽聽rather than owner-drawn or custom controls?

Is the聽聽throughout the application?
础谤别听聽in the menu, tool, and format bars?
Does the software ensure that聽color-coding is never used as the only means聽of conveying information or indicating an action?
Does the application support聽听蝉测蝉迟别尘-飞颈诲别?
Is all visible and nonvisible text聽?

If there are audio alerts, are聽聽also provided?
Can the user聽?
If information is provided in an audio format, is it also capable of being displayed by the user in a聽?
Is the software application聽聽used behind text or important graphics?
Can a user override聽聽for printing and text displays?
Can a user adjust or disable聽?

Are all manuals and documentation provided in an聽accessible electronic format聽including text descriptions of any charts, graphs, pictures, or graphics of any nature?
滨蝉听聽that will enable them to become familiar with the software and learn how to use it in conjunction with assistive technology provided as an accommodation?

Does the software support existing聽聽(e.g., sticky keys, slow keys, repeat keys, Voice Over)?
Have you聽聽(including, at a minimum, a screen reader, and, if possible, alternate input devices, screen enlargement software, and voice recognition software and devices)? Describe the accessibility successes and problems you encountered during these testing exercises, as well as your plans for addressing any problems.
Have you聽evaluated similar software alternatives聽that might have better accessibility features?