My website passed an accessibility checker. Is it accessible? 7 checks a scan can't do
A clean WAVE, Lighthouse or axe result (0 errors, or a score of 100) is a good start, but it doesn't mean your site works for everyone. Here are 7 quick manual checks that cover what automated scanners can't see.
You ran a free checker and got 0 errors, or a Lighthouse accessibility score of 100. That's worth celebrating, and it means the problems a computer can spot reliably are mostly gone. But a clean scan doesn't mean the site is accessible. The W3C says it plainly in its guide to selecting evaluation tools: tools can't check every accessibility requirement, and people need to judge the results. Here are 7 checks you can do yourself in about 15 minutes.
Why a clean scan isn't the whole answer
Automated checkers test what code can prove: is there an alt attribute, does a form field have a label, is this text's contrast ratio high enough. They can't tell whether the alt text is right, whether the label makes sense, whether a menu can be used without a mouse, or whether an error message helps anyone. A site can pass every automated rule and still lock out a keyboard or screen reader user.
The 7 checks a scan can't do
- Use the whole site with only a keyboard. Tab through the menu, open any dropdown, fill in the contact form and reach the "Book" or "Buy" button. If you get stuck, or can't see where you are, that's a failure no scanner reports reliably. Our keyboard test walks you through it. (WCAG 2.1.1, WCAG 2.1.2, WCAG 2.4.7)
- Read your alt text out loud. A scanner only checks that alt text exists. "IMG_4032.jpg" or "image" passes the scan but tells a blind visitor nothing. See our alt text examples. (WCAG 1.1.1)
- Submit your forms with mistakes. Scanners don't submit forms, so they never see your error messages. Leave a required field empty and check that the message says what's wrong, in text, next to the field. Our form error guide has the details. (WCAG 3.3.1, WCAG 3.3.3)
- Zoom to 200% and look at it on a phone. Text should get bigger without being cut off, and you shouldn't have to scroll sideways to read a paragraph. (WCAG 1.4.4, WCAG 1.4.10)
- Listen to the page with a screen reader for 5 minutes. Check that headings make sense as an outline, buttons say what they do, and nothing important is skipped. Our screen reader test shows how with free tools. (WCAG 1.3.1, WCAG 4.1.2)
- Check what moves, pops up or plays. Sliders, popups, chat widgets and autoplay video often load after the scan finishes, or only appear after a few seconds. Make sure each one can be paused or closed with a keyboard. (WCAG 2.2.2)
- Open your PDFs, menus and booking widget. Many scanners only test the HTML page. A menu posted as a picture or a third-party booking tool can fail even when your page passes. See our guides on PDFs and menus and booking widgets.
The W3C's Easy Checks page is a good free next step, and its page on involving users with disabilities explains why real people catch what tools miss.
Common reasons a "passing" site still fails
- The checker only tested the homepage, not your contact, booking or checkout pages.
- The scan ran before cookie banners, popups or chat widgets appeared.
- Alt text, labels and link text exist but don't make sense ("image", "click here", "button").
- A theme's dropdown menu opens on hover only, so keyboard users can't reach the links inside it.
- Focus outlines were removed in the theme's CSS, so keyboard users can't see where they are.
- An accessibility overlay or widget was added, which can hide problems from some scanners without fixing them. See overlays vs real fixes.
On Wix, Squarespace, Shopify or WordPress
Built-in accessibility checkers on these platforms (such as Wix's Accessibility Wizard) are helpful, but they share the same limits as any automated tool. Themes, apps and plugins change with updates, so a site that passed last month may not pass today. Re-run your checker after big changes and repeat the keyboard and form checks above. Our maintenance plan guide has a simple monthly routine.
What our scan can and can't tell you
Our free snapshot and the $149 Fix-Pack use the same kind of automated engine (axe-core), so they have the same limits described on this page. The Fix-Pack scans up to 10 pages instead of one, and explains each issue it finds in plain English with copy-paste fixes for your platform. It doesn't do the manual checks above for you, and it doesn't replace testing by people with disabilities, so use the 7 checks alongside it. This page is general technical guidance, not legal advice, and following it doesn't certify compliance with the ADA or any law.
Related: free checkers compared, fixing Lighthouse accessibility errors, accessibility checklist, what an audit includes, keyboard test.
Want the fixes written for you?
Start with a free homepage snapshot. The $149 Fix-Pack scans up to 10 pages and gives copy-paste fixes for your platform within 48 hours, with a 14-day refund promise. See a sample report first.
This is general technical guidance, not legal advice, and it does not certify compliance with the ADA or any law.
Related guides
- Therapist and counseling practice website accessibility: intake forms, booking and telehealth
- WCAG 2.2 explained for small-business websites
- Squarespace accessibility fixes: alt text, contrast, forms and more
- Wix accessibility fixes: a practical checklist
This guide is general technical information, not legal advice. Following it does not certify ADA or any legal compliance. Automated checks find only part of accessibility barriers.
Check your own site
Run a free homepage snapshot to see your top 3 issues in about a minute, or order the $149 Fix-Pack for up to 10 pages with copy-paste fixes for your platform.