usability testing

Skip to navigation

(Adapted from the UALR summary of priority checkpoints)

Checkpoint 1.1
For the following items, provide text descriptions: images, graphical representations of text (including symbols), image map regions, animations, applets and programmatic objects, ascii art, frames, scripts, list bullet images, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. To accomplish this, use the alt & title attributes for each element.

Checkpoint 1.2
In case of image maps, provide relative text links on the page as well.

Checkpoint 1.3
If you use video, provide a description of the visual part of the page as either a sound or text file.

Checkpoint 1.4
Synchronize sound and captioning to video files.

Checkpoint 2.1
When you use color to indicate items like headings, use the correct HTML element to indicate a heading.

Checkpoint 3.1
Ensure that pages remain 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.

Checkpoint 4.1
If you change the language of a page use lang = "" attribute for the element. It is best not to change the language in a page but if absolutely necessary, take care to notify users of the change. For example, if the language of a page changes from English to French for a paragraph, use the lang="fr" attribute in the paragraph element.

Checkpoint 5.1
For tables, use header and data cells to define which cell contains data and which cells are the column headers.

Checkpoint 5.2
For complex tables, break your table into its parts using the thead, tbody and tfoot elements.

Checkpoint 6.1
If the stylesheet is turned off, the page should still be readable.

Checkpoint 6.2
If your document uses scripting or Java, make sure to provide results in a way that can be accessed by a screen reader, usually in text format. If you provide the alternative result, make sure to update the alternative page when you change the script so the results are valid.

Checkpoint 7.1
Do not use then BLINK element out of respect for individuals with photosensitive epilepsy. These people can have seizures triggered by flickering or flashing in the 4 to 59 flashes per second (Hertz) range with a peak sensitivity at 20 flashes per second, as well as quick changes from dark to light.

Checkpoint 9.1
If image maps are used for navigation, utilize the "usemap" attribute instead of the "ismap" attribute. "ISMAP" creates a server side image map that cannot correctly pass the location to visit when accessed by a screen reader.

Checkpoint 11.4
If all else fails, provide an alternate accessible page that possesses equivalent information (or functionality) and is updated as often as the original page.

Checkpoint 12.1
Title each frame to allow for frame identification and navigation.

Checkpoint 14.1
Use the clearest and simplest language appropriate for your site.

resources

Skip to navigation

disability.gov
Website linking to information of interest to people with disabilities, their families, employers, service providers, and other community members.
closingthegap.com
Organization that focuses on assistive technology for children and adults with special needs through its bi-monthly newspaper.
aware.hwg.org
Accessible Web Authoring Resources and Education, designed to serve as a central resource for web authors to learn about web accessibility.
w3.org
World Wide Web Consortium (W3C) helps develop specifications, guidelines, software, and tools to lead the Web to its full potential.
uiaccess.com
Resource providing free information on web accessibility in the forms of universal interface design and usable accessibility information.