Skip to content
SiteRecord

What Accessibility Scans Can and Cannot Tell You

Automated accessibility scans are the fastest way to find common problems on a website. They are also commonly over-read: a clean scan is treated as proof of accessibility, and a scan report is treated as proof of a compliance program. Neither is accurate. Understanding what scans can and cannot tell you is what makes them genuinely useful.

What automated scans detect well

Scanning tools evaluate a page's code against machine-checkable rules, most of them derived from the Web Content Accessibility Guidelines (WCAG). Where the answer is a matter of markup, scanners are fast, consistent, and thorough across large page counts. They reliably catch things like:

  • Images missing an alt attribute.
  • Form fields with no programmatically associated label.
  • Text contrast below WCAG thresholds.
  • Missing page language or title.
  • Absent landmarks such as main, nav, or header regions.
  • Duplicate IDs and broken ARIA references.
  • Keyboard traps that are detectable in code.

For a website of any real size, this coverage is the practical way to keep track of mechanical issues at scale. A scan turns "we should check the site" into a list of specific, located findings.

What requires human evaluation

Most WCAG success criteria cannot be fully checked by a machine. The W3C's own guidance on evaluating accessibility is explicit that tools cannot determine all conformance, and human judgment is required. The limits are structural, not temporary:

  • Quality, not presence. A scanner sees that an image has alt text. It cannot tell whether "image123.png" describes anything. It sees a label exists; it cannot judge whether the label makes sense.
  • Interaction. Whether a menu can be operated with a keyboard, whether focus moves in a sensible order, whether a modal traps or releases focus correctly: these have to be tried, not read.
  • Meaning. Whether an error message explains the problem, whether instructions are understandable, whether the reading order matches the visual order.
  • Real-world use. Whether a person using a screen reader, magnification, or voice control can actually complete the task the page exists for.

Automated tools cover a minority of what determines whether a site is usable by people with disabilities. Manual testing, especially keyboard checks and assistive technology walkthroughs, is not a supplement to scanning. It is the other half of the evaluation.

What a clean scan actually means

A scan that reports no issues means only this: on the pages checked, at the time it ran, the tool found no violations of the rules it applies. It does not mean the site is accessible, conformant, or safe from complaints, because the scan did not evaluate most of the criteria that matter and only saw the pages it was given.

The reverse also holds. A flagged result is a suspected barrier, not a confirmed one. Scans produce false positives, and a person should review findings before they become work items or claims.

Scan reports are useful inputs, not verdicts

A scan report documents real facts: that a check ran, which pages it covered, what it found, and when. As part of an accessibility record, that is valuable. It shows detection, and detection is where the work starts.

What a scan report cannot show is everything that happened next. It does not record who saw the findings, who was assigned to fix them, what changed, or whether anyone verified the result. Those facts live in the remediation and verification record around the scan, which is why a folder of scan reports is not the same thing as an accessibility program. How to Document Accessibility Improvements covers the rest of that record.

Getting real value from scans

Scans pay off when they sit inside a loop rather than standing alone:

  • Scan the pages and journeys that matter, on a schedule that matches how fast the site changes.
  • Review findings and assign them to people, instead of letting reports accumulate.
  • Fix the confirmed issues and record what changed.
  • Verify fixes with the method that fits: a rescan for mechanical issues, keyboard or assistive technology checks for interaction problems.
  • Use scan-to-scan comparisons to spot regressions and recurring patterns.

The Accessibility Remediation Checklist lays out that loop step by step, and How to Verify an Accessibility Fix covers what confirmation actually involves.