Manual audit vs automated accessibility scanners
Automated scanners are fast, cheap and worth running, but they only catch part of the problem. A manual audit is a person using your site the way disabled people do, with a keyboard and a screen reader, to find the barriers a scanner can't see. You want both, for different jobs.
The short answer
- Scanners check the code for things a machine can measure: missing alt text, low contrast, unlabelled fields.
- A manual audit checks whether people can actually use the site: keyboard access, screen reader announcements, whole journeys.
- Use a scanner every time the site changes. Get a manual audit before a launch, a redesign or a tender, or after a complaint.
What the evidence says
The UK Government Digital Service built a web page with 142 deliberate accessibility failures and ran it through popular automated testing tools. The best single tool found only around 40% of the problems, and even all the tools combined missed almost a third. That was a page designed to be broken in obvious ways, so on a real website the share a scanner catches is usually lower.
What scanners are good at
Free tools such as WAVE, Lighthouse and axe reliably flag things that can be checked by reading the code:
- Images with no alt text at all.
- Text colour that fails the minimum contrast ratio.
- Form fields with no label in the code.
- A missing page language or page title.
- Empty links and buttons.
- Headings that skip levels.
Running a scanner regularly, ideally every time the site changes, is a sensible habit. It stops easy mistakes creeping back in.
What scanners can't tell you
A scanner can see that something exists. It can't tell whether it makes sense or works. It won't reliably catch:
- Bad alt text. “image123.jpg” or “photo” passes the scanner but tells a blind customer nothing.
- Keyboard traps. A cookie banner or pop-up you can tab into but never out of.
- Focus order. Whether pressing Tab moves through the page in a logical order, and whether you can see where you are.
- Screen reader announcements. Whether a basket update, an error message or “booking confirmed” is ever read out.
- Whole journeys. Whether someone can actually complete a booking, a purchase or an enquiry from start to finish.
- Meaning. Whether link text like “click here” makes sense out of context, or whether instructions rely on colour alone.
These are the barriers that make disabled customers leave, and the ones complaints are usually about.
The “100 score” trap
A Lighthouse accessibility score of 100 means the automated checks passed. It doesn't mean your site is accessible or that it meets WCAG 2.2 AA. Sites that score in the 90s can still be impossible to check out from using only a keyboard.
What a manual audit adds
In a Clearsight audit I use scanners as a first pass, then test by hand:
- Keyboard-only testing, with the mouse unplugged.
- Screen reader testing with VoiceOver on Mac and NVDA and JAWS on Windows.
- Zoom, reflow and mobile testing.
- Each relevant WCAG 2.2 AA success criterion checked against your key pages and journeys, following the DHS Trusted Tester method.
You get every issue explained in plain English: where it is, who it affects, how serious it is and how to fix it.
Which do you need?
- Just curious: run WAVE or Lighthouse yourself, and try the Tab Test.
- Before a launch, redesign or tender: get a manual audit.
- After a complaint: get a manual audit, and take legal advice.
- Ongoing: scanner checks on every update, with a manual retest after big changes.
See how much a website accessibility audit costs for prices.
Common questions
Is an automated scan enough to be legally safe?
No. The Equality Act asks whether disabled people can use your service, and most of the barriers that stop them can only be found by hand.
What about AI-powered scanners?
They can make useful suggestions, but they still can't confirm that a journey works with a real screen reader. Treat their output as a starting point to check, not a result.
Are overlay widgets a kind of automated fix?
Yes, and they share the same limits. Read do accessibility overlay widgets protect you from the Equality Act?
Not sure what a scan is missing?
Send me your site and I'll show you what a person finds that the tools didn't, starting with the free 5-issue quick check.
Email Clearsight AccessThis guide is general information, not legal advice. Back to all Web Accessibility Guides.