Skip to the content

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 the Manual Accessibility Evaluation by Tom Jewett. This checklist has been edited to follow California State University, Los Angeles (CSULA) requirements.

The necessary tools for this manual check (Firefox browser, Firefox Web Developer Toolbar, Accessibility Extension, and lowvis.css) can be downloaded from theTesting Tools page. Instructions for performing some of the manual checks have been provided in bold text.

  • TECHNICAL

    • Browser: View » Page Source
      • Does each form input have an associated <label> element or other appropriate grouping element?
        — if no, it needs repair.
      • Does each data table column (and row, if applicable) have a head element with the scope attribute?
        — if no, it needs repair.
      • Is a summary attribute provided for data tables?
        — if no, it needs repair.
      • Are there deprecated "illegal" codes in use such as <font><b><i>. For a complete list go to Illegal Coding page.
        — if yes, it needs repair.
      • Does the page use frames?
        Page Source: Edit » Find (Ctrl + F).
        Search by typing "frameset".

        — if yes, each frame must be named using the name attribute (name="").
      • Does the page use image maps?
        Search for "map".
        — if yes, provide text equivalents for hotspots.
    • Automated Validation
      Note: Cannot be run locally, page must be online.
      • Does the HTML code pass the automated validation?
        Web Developers Toolbar: Tools » Validate HTML
        — if no, it needs repair. 
      • Does the CSS code pass the automated validation?
        Web Developers Toolbar: Tools » Validate CSS
        — if no, it needs repair.
    • Headings
      Web Developers Toolbar: Information » View Document Outline
      • Are headings organized according to the content presented?
        — if no, it needs repair.
      • Are there any missing heading?
        — if yes, it needs repair.
    • Link Details
      Web Developers Toolbar: Information » Display Link Details
      • Do all links look distinguishable from normal text?
        — if no, it needs repair.
      • Do any links contain "href='javascript...'"?
        — if yes, it needs repair. See Tutorials on JavaScript.
      Note: Repeat the steps to reset settings back to normal.
  • 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?
        — if no, it needs repair.
      • Does the background and text colors change to a brown hue?
        — if no, it needs repair.
      • Do paragraphs have a surrounding border?
        — 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?
        — if no, it needs repair.

  • Back to Top

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

    Last Update: 05/28/2009
    Contact the Page Author