Skip to content

WAS Notes: Basic Methods for Web Accessibility Testing

I'm studying for the WAS certification. These are some of the notes I've taken recently.

Published:

Accessibility Checklists

The Scope of the Test

This is the priority order for things that need to be evaluated:

  1. Anything that occurs across the entire site
  2. Navigation
  3. Anything used to accept payments or commit to legal contracts
  4. Anything used during primary interaction with the site (core functions)
  5. Common causes of accessibility problems, like images, forms, custom widgets, and multimedia
  6. Things typically used by people with disabilities, like site maps
  7. Things used to contact the organization
  8. High-traffic areas (top 80%)

Testing Pages

Testing Templates

Testing Page Content

An Example Testing Routine

  1. Determine the scope for testing
  2. Run automated tests (can catch about a third of all issues this way)
  3. Perform manual testing for each of these areas of focus
    1. Keyboard Access (tab order, keyboard traps, focus indicators, etc.)
    2. Touch Access (touch target size, touch functionality)
    3. Visual Presentation (color contrast, conveying meaning through color alone)
    4. Alternative Text (going beyond what you can automatically detect, is the alt text actually good?)
    5. Audio and Video (captions, transcripts, and audio descriptions)
    6. Semantics and Document Structure (landmarks, headings, link text, etc.)
    7. Forms (labels and descriptive text, validation and feedback, etc.)
    8. Dynamic Content (does focus update correctly, is content added after the current position in the DOM, etc.)
    9. Custom Widgets (heavy focus on keyboard functionality, since it is created from scratch)
  4. Document findings in an Accessibility Report
  5. Plan for Remediation
  6. Conduct Regression testing

A Good Bug Report Template

Prioritizing Accessibility Bugs