Back to Web Accessibility Best Practices NASA Insignia

Web Accessibility Checklist

Question Y N N/A
1. For all images, is alternative text provided?
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?      
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 provided of all graphics that convey important information?
To do so: use "longdesc."
     
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 -- 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, 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?
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.
     
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?      
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. 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?      
23. If you provide a "text only" alternative page, does it contain substantially the same information as the original page?      
24. If you provide a "text only" alternative page, is it updated as often as the original page?      

Back to Web Accessibility Best Practices

If you have any difficulty viewing this page with adaptive technology, click here to let us know.

Author
Charles Redmond
NASA Headquarters
NASA Headuarters building picture Curator
Charles Redmond
This document last updated January, 2001.

NASA Privacy Statement, Disclaimer,
and Accessibility Certification