UTEP Web Page Accessibility Checklist

Original 09/11/2007
Revised 01/28/2008
Question 35 added 05/28/2009

Programmer/Developer/Webmaster Name:_________________________________                     Date: ___/___/_____

Reviewer Name:______________________                                                                                

Application Name / Version: _____________________________________________________________________

Web Page Area / Date / URL: ___________________________________________________________________

Instructions:  This checklist should be used during web page development as a guide and as an assist for creating compliant web pages. After development, this checklist should be completed for each application, web site, and/or web page prior to code release / use. This checklist is subject to change at any time without notification.

The only acceptable method for ensuring TAC (Texas Administrative Code) & US 508 compliance (accessibility) is a combination of manual checks and the use of  automated accessibility checkers. Neither manual checking or automated checking alone provides satisfactory assurance of accessibility. Several automated tools are available to assist in checking TAC & US 508 compliance. A listing of those tools (Color/Contrast analyzer, W3C HTML/XHTML checker, , 508 checker) is provided at the following link:  http://utminers.utep.edu/dmbatten/usefullinks.html. Testing with accessibility technologies, such as JAWS, ensures that those with disabilities can access the information on the web page.

It is STRONGLY suggested that you use all the tools listed above prior to completing the checklist below.

The TAC document can be found at the following link: Texas Administrative Code
A synopsis of the TAC which pertains to web pages, as of 9/11/2008, can be found at:  http://utminers.utep.edu/dmbatten/usefullinks.html

Note: After completion his document must be retained by the creating authority due to the potential of audit from the State of  Texas, IRDR. A copy of this document along with a copy of the explanation document should be sent to the regulating authority, Information Technology for Applications and Department of Web Content for Web Pages, web forms and web sites.

The programmer, developer and/or webmaster is responsible for complying with the TAC and any subsequent requirements. This document is a guide for compliant creation of accessible web pages.

*For items answered "Not Applicable", provide a brief description in a separate document explaining why the item is not applicable to this accessibility check point. Explanation documents should always be kept with the completed checklist.





1. For all images, is alternative text provided? (use of the HTML ALT tag)

Note. This includes images used as spacers, bullets in lists, and links


2. For all applets, are alternative text and content provided?


3. For all image map links, is alternative text provided ("title" tags, etc)?


4. If server-side image maps were used, are text links provided for each hotspot in the image map?


5. For all graphical buttons, is alternative text provided?


6. Is there an absence of ASCII art, and, instead, are images and alternative text used? e.g., use "smile" or an image with alt text instead of: :-)


7. If OBJECT was used to incorporate an image, applet, or script into a page, is the information also conveyed in an alternative means in cases where the OBJECT cannot be perceived, such as with "title" or within the body of the OBJECT element?


8. Are long descriptions (over 80 characters) provided of all graphics that convey important and necessary  information?  Hint: To do so: use the "longdesc." tag.


9. For stand-alone audio files, are textual transcripts of all words spoken or sung as well as all significant sounds provided?


10. For audio associated with video, are captions -- textual transcripts of dialog and sounds --Provided?  Are captions synchronized with the video?


11. Where sounds are played automatically, are visual notification and transcripts provided?


12. For short animations such as animated "gifs" images, are alternative text and a long description provided, if needed?


13. For movies and video, are auditory descriptions provided and synchronized with the original audio?


14. If color is used to convey information, is the information also clear from the markup and/or text? (No information should be conveyed only with color, as some people are color blind and cannot make that distinction)

Hint: One way of testing this is to ask yourself whether the information is available if one is viewing it on a black and white screen, or to print out the page on a black and white printer.


15. Are foreground and background color combinations used that provide sufficient contrast when viewed by someone with color blindness or when viewed on a black and white screen or printed on a black and white printer?


16. For auto-refreshing or timed response pages, is a second copy of the page provided where refresh only happens after a link has been selected (until user agents provide this ability themselves)?


17. Is the Web page free from any blinking or updating of the screen that causes flicker?


18. If you are using frames, are they appropriately labeled so that their usage and navigation is apparent to those who are using screen readers? If not, is a fallback page provided for pages that contain frames?


19. For scripts that present critical information or functions, is an alternative, equivalent presentation or mechanism provided?


20. For pages that use style sheets, are the contents of each page ordered and structured so that they read appropriately without the style sheet?


21. If frames are used, are titles provided so that users can keep track of frames by name?


22. Do you provide a "text only" alternative page to the original page if  any of the answers on this list are "No"?


23. If you provide a "text only" alternative page, does it contain the same information as the original page?


24. If you provide a "text only" alternative page, is it updated in parallel with the original page?

25. Is navigation on the page set up for left to right and top to bottom movement?

26. Are controls tagged within the code so that users of screen readers know which fields/controls they are accessing?

27. Have you passed your web page through a screen reader in order to check for comprehensibility and accuracy?

28. Do graphics within the web page convey important meaning to the purpose of the page? (If they are just for decoration, you might need to rethink your page design).

29. Are you using a University approved CSS in conjunction with your document?

30. Are font styles, colors, sizes declared by "font family" and "relative" sizes within the document?

31. Does all web page code conform to published and accepted standards? (HTML, XHTML, CSS...etc)? Note: the use of an authoring tool does not automatically assure that the code generated is in compliance with published and accepted standards.

32. If a 'form' is used and it has a 'time out' value, does it allow the user to ask for more time to complete the form or task?

33. If you provide a page with "translated" text, is it updated in parallel with the original language  page?

34. Have you checked your HTML, XHTML, CSS, and color usage with the automated tools listed at: http://utminers.utep.edu/dmbatten/usefullinks.html ?

35. Do all 'href' tags have 'title' tags associated with them?

Answering "No" to any of the above questions does not automatically imply that your site or page is not compliant. Each site should be reviewed, using both manual and automatic techniques to ensure compliance.

**This is a 'living document" whose only valid version is online. Printed copies may be out of date. This document is subject to immediate and unannounced updates and changes as dictated by the UT System and the UTEP Department of Web Content. It is the user's responsibility to stay informed of the current version and to utilize the contents herein.
Copyright (c) 2008-Forward, The University of Texas at El Paso
Department of Web Content
email: webcontent@utep.edu