Search within:

Accessibility Evaluations

Accessibility Evaluations

Evaluating a website or web application for accessibility is not difficult with automated tools. Just keep in mind that automated evaluations only find about 30% of accessibility issues. But if you are choosing between IT purchases, automated evaluations can give you an idea of which tool might do a better job including everyone in that solution.

Find out more about the IT purchasing process.

Chrome Lighthouse Score

The nice thing about this tool is that it gives you a score for each page you run the automated checker on. You can assign each page 100, then you can average that out to scores for each page.

If you'd like to run your own audit, here are the steps:

  1. Use Chrome to navigate to the page you want to check.
  2. Go to the View menu.
  3. Choose Developer then Developer Tools.
  4. Go to the Audits tab choose AccessibilityOptional: deselect the other audits to speed up the process.
  5. Scroll down and choose Run Audits.

It will take a few moments for the checker to process, then you will see a score.

There are many other automated tools you can use and the more tools you use, the better idea you will have about the accessibility of the site. Please keep in mind however, that any automated tool, while helpful, will only indicate about 30% of the possible accessibility problems with the web page it is evaluating. Even the errors it finds still need to be understood in context because they may or may not actually be errors.

Manual Evaluations

This section is an introduction to some of the manual checks required for accessible web pages. Some manual checks can be performed on an individual page, while some require looking at usage across pages on a site.

  1. Do a visual inspection of your pages. Check the contrast with a Color Contrast tool (beware of false positives- you may need to manually check items that are marked as a violation).
  2. If you have media and images, check to make sure that your images have alternative descriptions and your videos have captions.
  3. Order and presentation of content should make logical sense. Headings should be used to designate content, not simply change the appearance of text.
  4. Access your website with a keyboard. Set aside the mouse, and start tabbing through your page. A good example site to tab through is the Web Experience Toolkit. Note you will need to use your keyboard arrow keys on the menus on that toolkit. Some things to be aware of:
    • Can you see where the focus is as you tab through the web page?
    • Are there places that lose focus or do there appear to be multiple steps between items on the page?
    • As you tab through the page, does the order follow how things are visually placed on the page?
    • With menus that have sub menus, can you open those menus by hitting space or return?
    • Is there a skip link at the top of the page to skip over the navigation into the main content area?
    • Are there areas on the website that can't be accessed via the keyboard?
    • For further details, visit the WebAIM resource on keyboard accessibility.
  5. Look across the pages on the site, and check:
    • Is the order and appearance of elements on the pages consistent?
    • Do you consistently use headings the same way?
    • Do you have "skip to main content" links? (These may only be visible when they receive keyboard focus by tabbing to the link.)

When you're ready to make the next step to checking for all of the accessibility guidelines, WebAIM has a good checklist. Be sure to set the simplified checklist to the correct conformance level (currently WCAG 2.1 AA).