Why Testing Matters
Making a website accessible isn't a one-time task — it requires regular testing to find barriers, fix them, and make sure new content doesn't introduce new problems. The DOJ's Title II web rule requires conformance with WCAG 2.1 Level AA, and testing is how you know whether you meet that standard.
Effective testing combines three approaches: automated scanning tools, manual keyboard and visual checks, and screen reader testing. No single method catches everything — you need all three.
Automated Testing Tools
Automated tools scan your web pages and flag common accessibility issues. They're fast and good for catching low-hanging fruit, but they only find about 30–40% of issues.
What automated tools miss: Whether alt text is actually meaningful, whether a keyboard user can complete a task, whether content makes sense when read aloud, whether focus order is logical, and whether custom components work with assistive technology.
Official Standard
WCAG 2.1 — Conformance Testing
WCAG defines conformance as meeting all Level A and Level AA success criteria for entire web pages. Automated tools evaluate machine-testable criteria — approximately 30–40% of all success criteria.
Criteria like "text alternatives serve the equivalent purpose" (SC 1.1.1) or "content is understandable" (Principle 3) require human judgment and cannot be fully evaluated by automated tools alone.
Manual Testing
Manual testing catches the majority of issues that automated tools miss. Here's a step-by-step checklist:
Official Standard
WCAG 2.1 SC 2.1.1 — Keyboard (Level A)
"All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes."
SC 1.4.4 — Resize Text (Level AA)
"Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality."
SC 1.4.3 — Contrast (Minimum) (Level AA)
"The visual presentation of text and images of text has a contrast ratio of at least 4.5:1."
Screen Reader Testing
Screen readers convert on-screen content to speech or Braille output. Testing with a screen reader reveals issues that no other method can catch — like confusing reading order, missing button names, or unlabeled icons.
What to listen for: Can you tell what every button and link does? Are images described? Do form fields announce their labels? When the page changes (like after submitting a form), does the screen reader announce the change?
Most Common Issues Found
Research from WebAIM's annual survey of the top 1 million websites consistently finds the same issues year after year:
How Often to Test
Accessibility testing should be part of your regular workflow, not a once-a-year event:
- Before every launch: Run automated scans and manual keyboard testing on any new page, feature, or redesign before it goes live.
- After every major update: CMS updates, theme changes, new plugins, or content migrations can introduce new barriers.
- Quarterly audits: A more thorough review — including screen reader testing — on a regular schedule catches issues introduced by day-to-day content updates.
- Continuous monitoring: Automated scanning tools can be set to run weekly or monthly and alert you to regressions.
- Annual comprehensive audit: A full evaluation by an accessibility specialist provides the most complete picture and helps prioritize the year's remediation work.
Important Note
This guide provides general information about web accessibility testing. Comprehensive testing may require specialized expertise. For legal advice about your obligations or your rights, connect with an experienced ADA attorney.
Think you experienced an ADA violation?
Answer a few simple questions and we’ll show you exactly what applies to your situation — in 60 seconds.
Attorney-connected violation reporting — launching soon.