Skip to main content

Human Ability and Accessibility Center
Newsroom
Accessibility Services
Industries
Case studies
Product accessibility information
Developer guidelines
Software
Web
Java
Lotus Notes
Hardware
Hardware self contained, closed products
Documentation
Laws, standards and regulations
Open Computing
Accessibility education
Partnerships
Events
Resources
Accessibility at IBM
Downloads

Web Accessibility

Use this checklist for:

  • Web sites
  • Web applications

    • Understanding Accessibility

    If you are new to accessibility, review "Understanding Accessibility" before completing the checklist.

    IBM Web Accessibility Checklist

    Last updated September 27, 2002. Techniques pages, accessed via the link in each checkpoint, may contain more recent updates. Be sure to review the techniques pages for the latest accessibility guidance. For convenience in completing the Web accessibility checklist, save this page and edit the HTML file.


    IBM Web accessibility checklist - version 3.1
    Checkpoint Yes No
    Planned
    N/A    		 Comments
    1 Images and animations. Use the alt="text" attribute to provide text equivalents for images. Use alt="" for images that do not convey important information or convey redundant information.    
    2 Image Maps. Use client-side image maps and alternative text for image map hot spots. If a server-side map is needed, provide equivalent text links.    
    3 Graphs and Charts. Summarize the content of each graph and chart, or use the longdesc attribute to link to the description or data.    
    4 Multimedia. Provide captions or transcripts of important audio content. Provide transcripts or audio descriptions of important video content.    
    5 Scripts. Ensure the functionality of scripts is keyboard accessible. If the content affected by scripting is not accessible, provide an alternative.    
    6 Applets, Plug-ins, and non-HTML content. When an applet, plug-in or other application is required to be present, provide a link to one that is directly accessible, or provide alternate content for those which are not directly accessible.    
    7 Forms. Make forms accessible to assistive technology.    
    8 Skip to main content. Provide methods for skipping over navigation links to get to main content of page.    
    9 Frames. Provide a title for each FRAME element and frame page. Provide an accessible source for each frame.    
    10 Table Headers. Use the TH element to mark up table heading cells. Use the headers attribute on cells of complex data tables.    
    11 Cascading Style Sheets. Web pages should be readable without requiring style sheets.    
    12 Color & Contrast. Ensure that all information conveyed with color is also conveyed in the absence of color.    
    13 Blinking, Moving or Flickering Content. Avoid causing content to blink, flicker, or move.    
    14 Timed Responses. When a timed response is required, alert the user, and give sufficient time to indicate more time is required.    
    15 Text-only Page. If accessibility cannot be accomplished in any other way, provide a text-only page with equivalent information or functionality. Update the content of the text-only page whenever the primary page changes.    
    16 Verify Accessibility. Test the accessibility using available tools.    

    ©2001, 2002 IBM Corporation

    References