You typed your web address into a free ADA compliance checker and got a verdict back in seconds. Maybe it was a big red “Not compliant” with a score out of 100. Maybe it was a friendly green check and a badge you were invited to put in your footer. Both felt official.
It is worth knowing what actually happened in those seconds, because the result is much narrower than the word “compliance” suggests. Free scans are useful. They are also easy to misread, and a few are built mainly to sell you something.
What a free ADA compliance checker does with your URL
The site loads one page, usually your home page, in an automated browser. It runs a set of rules over the code: images without alt attributes, form fields without labels, low contrast text, missing page language, empty links and buttons, and so on. It counts the failures, weights them by its own formula, and turns that into a score or a pass/fail label.
That is all. Nobody tried your menu with a keyboard. Nobody listened to the page with a screen reader. The scan did not fill in your contact form, open your booking widget, log in, or reach your checkout. It usually looked at one page out of however many your site has.
None of this makes the scan worthless. The rules it runs catch real, common problems. But it is a test of a slice of the code on a slice of the site, and the label on the result should be read that way.
Why “ADA compliance” in a tool’s name means less than it sounds
The ADA itself does not contain a technical checklist for websites. For businesses open to the public under Title III, there is no DOJ regulation setting a web standard, and no government body that tests or certifies websites. In practice, audits, demand letters and settlements tend to use WCAG’s AA level, in its 2.1 or 2.2 edition, as the yardstick, which is why most checkers test against parts of WCAG and call the result “ADA”.
So when a free tool says “ADA compliant” or “not ADA compliant”, what it really means is “these automated WCAG rules passed or failed on this page”. The tool has no way to judge most of WCAG, and it has no authority to tell you where you stand under the law. For that question, the honest sources are ada.gov and, if you have received a letter, a lawyer. This is general information, not legal advice.
What a score can and cannot tell you
A score is good at one thing: showing change on the same page over time with the same tool. If your home page goes from many failures to few after a round of fixes, that is real progress on the issues the tool can see.
It is poor at almost everything else:
- Comparing tools. Every checker uses different rules and weighting, so a score from one means nothing in another’s terms.
- Judging the whole site. Your home page may be tidy while the product template or the contact form has serious barriers.
- Judging usability. A keyboard trap, a menu that only opens on hover, error messages that are never announced, or alt text that says “image” all slip past most automated rules or score as passes.
- Telling you what to fix first. Scores weight by rule, not by which task a visitor is trying to complete.
A top score is a good sign that the basics in the code are in order. It does not show that a blind, low-vision or keyboard-only visitor can get through your pages.
Badges, seals and “compliant” claims
Some checkers and widget vendors offer a badge or seal to display once you pass their scan or install their product. Be careful with these. A badge cannot reflect testing that never happened, and the site will change after the badge goes up: a new plugin, a new popup, a new page built by someone in a hurry. The badge stays green regardless.
There is a practical risk too. A seal that tells visitors your site is accessible invites exactly the people who will notice when it is not. Saying plainly what you have tested and fixed, and how to report a problem, is far more credible than a graphic in the footer.
When the free checker is part of a sales pitch
Some free scanners are run by companies that sell accessibility overlays: toolbars or scripts that claim to fix a site automatically. The scan result is real as far as it goes, but the report then steers you toward installing the product as the fix. Overlays have drawn long-running criticism from disabled users and accessibility specialists, websites running them have still been sued, and the Federal Trade Commission brought a case in 2025 against an overlay company over how it advertised its product. Our explainer on what accessibility overlays can and cannot do covers that properly.
A simple test: does the report explain each issue and how a developer would fix it in your site? Or does every recommendation lead to the same install button? The first is a tool. The second is an ad with a scanner attached.
Are online accessibility checkers accurate?
Mostly yes, within their limits. When a well-known scanner says an image has no alt attribute, it almost always does. The accuracy problem is coverage, not correctness. Many WCAG criteria need a person to judge them, and an automated rule cannot tell whether a description is meaningful or a focus order makes sense.
Checkers also make some mistakes. They may flag a correctly hidden element, misread contrast on text over an image, or miss problems that only appear after a script runs or a button is pressed. Treat every result as something to confirm.
Using a free scan sensibly
- Use a tool that shows its work. WAVE from WebAIM, for example, marks each issue on the page itself so you can see what it is talking about. Our guide to using WAVE walks through its results.
- Scan more than the home page. Run it on one page of each type: a standard page, a blog post, the contact page, a product or service page, your booking or checkout pages.
- Fix the clear errors first. Missing labels, missing alt attributes, empty buttons and contrast failures are usually quick.
- Note what the tool could not check and do a short manual pass: Tab through the page, zoom to 200 percent, try the form. Our post on checking whether your website is ADA compliant gives a half-hour self check for exactly this.
- Re-scan after updates to catch problems that new plugins or content bring back.
- Ignore badges and scores as end goals. Aim to remove barriers on the pages people actually use.
When the free scans have taken you as far as they can, the group guide on testing website accessibility properly shows the full method, and our website accessibility hub collects the rest of the topic.
Frequently asked questions
Does the government offer an official ADA website checker?
No. The Department of Justice does not run a checker or certify websites, and there is no government seal of approval. Tools that use “ADA” in their name test against parts of WCAG, the technical guidelines most often used as the benchmark. Any legal question about your obligations is one for a lawyer.
Can a free ADA compliance checker scan my whole site?
Most free tools scan one page at a time, and some limit how many pages you can check. Even full-site crawlers only run automated rules, so they still miss problems that need a person, such as keyboard traps, confusing focus order and poor alt text. Scan one page of each template at minimum.
My site scored highly. Am I safe from a demand letter?
A high score shows that certain automated checks passed, nothing more. Letters often describe barriers found by actually using a site, such as forms that cannot be completed with a keyboard or screen reader. No score or tool can protect you from a claim. A lawyer should handle any letter you receive.
Should I display an accessibility badge on my site?
We would not. A badge implies a promise that nobody can honestly make and it does not change when the site changes. A short, honest accessibility statement saying what standard you work toward, what you have tested, and how visitors can report a problem is more useful and more credible.
If you would like a person to look at what the automated tools miss, our free website accessibility check is a short first look, and our manual accessibility testing goes through your key pages with a keyboard and screen readers.
Next in this series: Mobile Accessibility Testing: Checks to Run on a Phone
