Website Accessibility Testing Tools: What They Miss and Why It Matters

The Problem with Relying on Automated Accessibility Testing

If you have ever run your website through a free accessibility checker, you probably got one of two results: a long list of errors that felt overwhelming, or a clean report that made you think everything was fine. Both can be misleading.

Automated accessibility testing tools are useful. They catch real issues, they work fast, and they give you a starting point. But here is what most business owners do not realize: even the best website accessibility testing tools only detect about 30 to 40 percent of WCAG accessibility issues. The rest require a human being to evaluate.

That gap matters. It is the difference between a site that passes a scan and a site that actually works for people with disabilities. And from a legal standpoint, a clean automated report does not protect you from an ADA compliance claim.

What Automated Tools Are Good At

Before we talk about the gaps, let us give credit where it is due. Automated accessibility testing tools excel at catching the things a computer can measure objectively:

• Missing alt text on images. The tool checks whether an alt attribute exists. Simple yes or no.
• Color contrast failures. It can calculate the contrast ratio between text and background colors and flag anything below WCAG minimums.
• Missing form labels. If a form field has no associated label element, the tool catches it instantly.
• Broken heading hierarchy. Jumping from H1 to H4 without H2 and H3 in between is easy for a scanner to detect.
• Missing page language attribute. The tool checks whether your HTML has a lang attribute set.
• Duplicate IDs. Two elements with the same ID will confuse assistive technology, and a scanner spots this immediately.

These are real issues worth fixing. If a tool finds them, fix them. But do not mistake this list for a complete picture of your site's accessibility.

What Automated Tools Miss

This is where most businesses get a false sense of security. A website accessibility checker cannot evaluate context, meaning, or user experience. Here are the categories of issues that require human judgment:

Alt text quality

A tool can tell you whether alt text exists. It cannot tell you whether it is useful. An image tagged "photo" or "DSC_0042.jpg" technically passes the automated check, but it tells a screen reader user nothing. Good alt text describes what the image communicates, not just that an image is there.

Keyboard navigation flow

Automated tools can check whether interactive elements are focusable. They cannot tell you whether the tab order makes sense, whether focus indicators are visible, or whether a keyboard user can actually complete a task like filling out a form and submitting it. That takes a person tabbing through the site and paying attention to the experience.

Screen reader experience

A scanner cannot listen to how your page sounds when read aloud. It cannot tell you that your navigation announces 47 links before reaching the main content, or that a dynamic form error appears visually but is never announced to assistive technology. Screen reader testing requires actually using a screen reader.

Dynamic content and interactive elements

Dropdown menus, modal dialogs, accordions, sliders, and tabbed interfaces all require specific ARIA attributes and keyboard behaviors to be accessible. Automated tools can check for the presence of some ARIA roles, but they cannot verify that a modal traps focus correctly, that an accordion announces its expanded or collapsed state, or that a slider can be operated with arrow keys.

Meaningful link text

"Click here" and "Read more" pass every automated scan. But for someone using a screen reader who pulls up a list of all links on a page, a dozen "click here" links are useless. Descriptive link text ("download our maintenance checklist" instead of "click here") is an accessibility requirement that only a human can evaluate.

Content readability and cognitive accessibility

WCAG includes guidelines about clear language, consistent navigation, and helpful error messages. No tool can measure whether your content is actually understandable to your audience. That is a human judgment call.

The Most Common Free Tools (and What to Expect)

If you want to run a quick check on your site, these are the tools we recommend starting with. Just remember their limitations.

WAVE (Web Accessibility Evaluation Tool)

Free browser-based tool from WebAIM. Shows errors, alerts, and structural elements as visual overlays on your page. Good for a quick visual audit of one page at a time. Does not test keyboard navigation or screen reader behavior.

Google Lighthouse

Built into Chrome DevTools. Runs an accessibility audit alongside performance, SEO, and best practices checks. Uses the axe-core engine under the hood. Gives you a score out of 100, but a perfect score does not mean your site is fully accessible.

axe DevTools

Browser extension from Deque Systems. One of the most accurate automated scanners available. The free version catches a solid range of issues. The paid version adds guided manual testing workflows, which is where real value shows up.

Browser keyboard test (no tool required)

Unplug your mouse. Try navigating your entire website using only the Tab, Shift+Tab, Enter, and Arrow keys. This is the single most revealing test you can do, and it costs nothing. If you get stuck, lose track of where you are on the page, or cannot complete a task, your keyboard users are having the same experience.

Why "We Ran a Scan" Is Not Enough

We see this regularly: a business owner runs their site through WAVE or Lighthouse, gets a decent score, and assumes they are covered. Then an ADA demand letter shows up citing issues the scanner never flagged.

Automated scans are a starting point, not a finish line. A complete accessibility evaluation includes:

1. Automated scanning to catch the low-hanging fruit (contrast, alt text, labels, heading structure)
2. Keyboard testing to verify navigation, focus management, and interactive element behavior
3. Screen reader testing to hear how your content is actually experienced by assistive technology users
4. Manual code review to check ARIA implementation, semantic HTML, and form validation
5. Content review to evaluate link text, error messages, and overall readability

Steps 2 through 5 require expertise and time, which is why most businesses work with a professional for this part.

Frequently Asked Questions

Can I make my website accessible using only free tools?

Free tools can help you find and fix many common issues. But they will not catch everything. For a thorough evaluation, especially if you are concerned about legal exposure, professional manual testing is worth the investment.

How often should I test my website for accessibility?

At a minimum, after any major update, redesign, or content change. New pages, new plugins, and new features can all introduce accessibility issues. If you are on a maintenance plan, accessibility checks should be part of the regular cycle.

Do accessibility overlays and widgets work?

Short answer: not well enough. Overlay tools (the ones that add a floating icon to your site promising "one-click accessibility") have been widely criticized by accessibility experts and disability advocates. They do not fix underlying code issues, they often interfere with actual assistive technology, and they have not prevented lawsuits. The only reliable approach is building accessibility into your site properly.

What should I do if my site fails an automated scan?

Do not panic. An automated scan showing errors is normal, even for well-built sites. Prioritize the critical issues first: missing alt text, contrast failures, missing form labels, and keyboard traps. Then work through the rest methodically. It does not have to happen all at once.

Not sure where your site stands? We include accessibility evaluation as part of our website audits. Start with a free 30-minute website consultation and we will walk through your site's current state together.

Schedule your free consultation →