• Home
• Section 508 Requirements
• Testing Tools
• Tutorials
• Web Templates
• FAQs
• Resources

Manual Evaluation Checklist

Pages can pass W3C validation but still be inaccessible to users. This manual procedure is designed to compliment automated evaluation tools for website accessibility, emphasizing areas that can only be evaluated realistically by human judgment. This cheklist is based on Tom Jewett's Manual Accessibility Evaluation, this checklist has been edited to follow California State University, Los Angeles (CSULA) requirements.

The necessary tools for this manual check must be downloaded at the accessibility Testing Tools page (Firefox browser, Firefox Web Developer Toolbar, Accessibility Extension and lowvis.css).

Printable Version of Manual Evaluation Checklist

This page contains a file that requires Adobe Acrobat to view. If you need an Adobe viewer, you can Download Adobe Reader for free.

For instructions see steps in bold.

• VISUAL CHECK

  • By visually looking at the web page:
    • Do columns, page elements, or text lines overlap each other when enlarged? Text should "wrap" within column.
      Browser: View » Text Size » Increase
      No Yes — if yes, it needs repair.
      Note: To reset settings, go to View » Text Size » Normal
    • Are page elements positioned in a logical, organized, easy-to-find layout?
      Yes No — if no, it needs repair.
    • Does page contain moving elements such as blinking text or marquees?
      No Yes — if yes, it needs repair. 
    • Does the page require active content such as video, audio, applets, to load?
      No Yes — if yes, it will need specialized evaluation. Go to http://www.calstatela.edu/accessibility/508.php for additional information.
    • Do all images have an equivalent alternative text? Only decorative images should be left blank (alt="")
      Web Developers Toolbar: Images » Display Alt Attributes
      Yes No — if no, it needs repair.
      Note: Repeat the steps to reset settings back to normal.
    • Are headings, paragraphs, and lists obvious and sensible when the styles are turned off?
      Web Developers Toolbar: CSS » Disable Styles » All Styles
      Yes No — if no, it needs repair.
      Note: Repeat the steps to reset settings back to normal.
    • Do all the text and background colors return to browser default color style?
      Web Developers Toolbar: CSS » Disable Styles » All Styles
      Yes No — if no, it needs repair.
      Note: Repeat the steps to reset settings back to normal.
    • Is there sufficient contrast between alt text and background colors when images are turned off?
      Web Developers Toolbar: Images » Disable Images » All Images
      Yes No — if no, it needs repair.
      Note: Repeat the steps to reset settings back to normal.
    • Does the reading order of headings and page elements make sense when linearized?
      Disable CSS and images.
      Web Developers Toolbar: Miscellaneous » Linearize Page
      Yes No — if no, it needs repair.
      Note: Repeat the steps to reset settings back to normal.
    • Is the page still accessible when javascript is turned off?
      Web Developer Toolbar: Disable » Disable JavaScript » All JavaScript
      Yes No — if no, it needs repair.
      Note: Repeat the steps to reset settings back to normal.
  • By tabbing through all the links and form elements:
    • Is there a logical progression between links and elements?
      Yes No — if no, it needs repair.
    • Does the tab order between form elements make sense?
      Yes No — if no, it needs repair. 
    • Is there a way to skip links and directly go to content?
      Yes No — if no, it needs repair.
  • Run Colour Contrast Analyzer:
    Simulation » Select Window (List)
    Under "Select Window" locate the browser title.
    Under "Simulation" choose one of the simulations listed.
    Click on the Preview button.
    • Is text legible in each simulation?
      
      • Protanopia
        Yes No — if no, it needs repair.
      • Deuteranopia
        Yes No — if no, it needs repair.
      • Tritanopia
        Yes No — if no, it needs repair.
      • Grayscale
        Yes No — if no, it needs repair.
      • Invert
        Yes No — if no, it needs repair.
    • Is there sufficient visual contrast ratio of at least 5:1 between text and background colors on each test? A green check mark will confirm this.
      Run Colour Contrast Analyzer:
      Select foreground and background color using the color picker.
      Select "Show contrast result for colour blindness".
      See results on Result-Luminosity Panel.
      
      • Normal
        Yes No — if no, it needs repair.
      • Protanopia
        Yes No — if no, it needs repair.
      • Deuteranopia
        Yes No — if no, it needs repair.
      • Tritanopia
        Yes No — if no, it needs repair.

• TECHNICAL

  • Browser: View » Page Source
    • Does each form input have an associated <label> element or other appropriate grouping element?
      Yes No — if no, it needs repair.
    • Does each data table column (and row, if applicable) have a head element with the scope attribute?
      Yes No — if no, it needs repair.
    • Is a summary attribute provided for data tables?
      Yes No — if no, it needs repair.
    • Are there deprecated "illegal" codes in used such as <font><b><i>. For a complete list go to Illegal Coding page.
      No Yes — if yes, it needs repair.
    • Does the page use frames?
      Page Source: Edit » Find (Ctrl + F).
      Search by typing "frameset".
      No Yes — if yes, each frame should be named.
    • Does the page use image maps?
      Search for "map".
      No Yes — if yes, provide text equivalent.
    • Does the page have <noscript> within all JavaScript elements?
      Search for "script" and look for a "noscript" after it.
      Yes No — if no, it needs repair.
  • Automated Validation
    Note: Cannot be run locally.
    • Does the HTML code pass the automated validation?
      Web Developers Toolbar: Tools » Validate HTML
      Yes No — if no, it needs repair. 
    • Does the CSS code pass the automated validation?
      Web Developers Toolbar: Tools » Validate CSS
      Yes No — if no, it needs repair.
  • Headings
    Web Developers Toolbar: Information » View Document Outline
    • Are headings organized according to the content presented?
      Yes No — if no, it needs repair.
    • Are there any missing heading?
      No Yes — if yes, it needs repair.
  • Link Details
    Web Developers Toolbar: Information » Display Link Details
    
    • Do all links look distinguishable from normal text?
      Yes No — if no, it needs repair.
    • Do any links contain "href='javascript...'"?
      No Yes — if yes, it needs repair.
      
    Note: Repeat the steps to reset settings back to normal.
  • View Speed Report: Is there a warning sign?
    Web Developers Toolbar: Tools » View Speed Report

    Go to the Analysis and Recommendations section.
    

    • TOTAL_HTML
      No Yes — if yes, it needs repair.
    • TOTAL_OBJECT
      No Yes — if yes, it needs repair.
    • TOTAL_IMAGES
      No Yes — if yes, it needs repair.
    • TOTAL_CSS
      No Yes — if yes, it needs repair.
    • TOTAL_SIZE
      No Yes — if yes, it needs repair.
    • TOTAL_SCRIPT
      No Yes — if yes, it needs repair.
    • HTML_SIZE
      No Yes — if yes, it needs repair.
    • SCRIPT_SIZE
      No Yes — if yes, it needs repair.
    • CSS_SIZE
      No Yes — if yes, it needs repair.
    • MULTIM_SIZE
      No Yes — if yes, it needs repair.

• USER TESTING

  • Low vision user test: This style sheet an example of one user's individual settings. We are testing to see if the user can personalize the page to their needs. Apply lowvis.css and look for the following problems:
    Web Developers Toolbar: CSS » Add User Style Sheet
    
    • Does all text size increased dramatically?
      Yes No — if no, it needs repair.
    • Does the background and text colors change to a brown hue?
      Yes No — if no, it needs repair.
    • Do paragraphs have a surrounding border?
      Yes No — if no, it needs repair.
    Note: Repeat the steps to reset settings back to normal.
  • Voice reader user test: Run JAWS or Fangs.
    For tutorials on JAWS go to http://atto.buffalo.edu/registered/Tutorials/jaws/index.php
    • Does it sound or appear like the text reader is dictating content in a logical manner?
      Yes No — if no, it needs repair.

Back to Top

• CSULA
• Campus Directory
• Campus Safety
• Contact CSULA
• GET
• Library
• News
• Search

5151 State University Drive . Los Angeles . CA 90032 . (323) 343-3000
© 2008 Trustees of the California State University

Last Update: 08/7/2008
Contact the Page Author