Skip to main content

Website Accessibility Score: What a Good Score Means

You ran a scan and got a number. Is 78 good? Is 100 the goal? This post explains what a website accessibility score measures, how scanners arrive at it, and how to use it without mistaking it for proof of compliance.

What an Accessibility Score Actually Measures

An accessibility score is a single number, usually 0 to 100, that summarises the results of an automated scan. The scanner loads a page, runs a set of rules against it, and turns the failures into a number. That is all it is. It is a measure of how many automatically detectable problems the page has, weighted somehow. It is not a measure of how usable the page is for a person with a disability, and it is not a legal verdict.

That distinction matters because automated tools see only part of the picture. Deque, the company behind axe-core, found that automated tests flagged 57% of all issues, counted by volume, across 13,000+ audited pages (Deque automated coverage report (opens in new tab)). The rest need a human: whether alt text is meaningful, whether the reading order makes sense, whether a custom widget works with a screen reader. A high score tells you the machine-checkable part is in good shape. It cannot tell you about the part machines cannot check.

How Scanners Calculate the Number

There is no standard formula. Every vendor chooses its own, so a 92 from one tool and a 92 from another are not the same thing. Three common approaches:

  • Pass-rate scores. Lighthouse, built into Chrome, runs a subset of axe-core rules and weights each by impact. Pages are scored on the weighted share of audits that pass, and a rule that applies to nothing on the page is simply left out. A page with few testable elements can score high almost by default.
  • Deduction scores. Start at 100 and subtract points per issue, with bigger penalties for severe ones. Simple to understand, and it rewards fixing the worst problems first.
  • Grade or tier systems. Letter grades or bands such as "Good" and "Needs work". Easy to read, but they hide how close you are to the next band.

CompliaScan uses the deduction approach. Each page starts at 100, and every issue found takes points off by severity: 10 for critical, 5 for serious, 3 for moderate and 1 for minor, with a floor of 0. For a multi-page scan the site score is the average of the page scores, so adding more pages does not drag the number down on its own. The full description, including the 100+ accessibility checks behind it (axe-core plus 9 custom checks), is on our methodology page.

Want to know where your site stands?

Run a free scan →

What Counts as a Good Score

As a rough guide using our own bands: 90 and above is good, 70 to 89 needs improvement, 50 to 69 is poor and anything below 50 is critical. A score of 100 means the scanner found nothing to flag on the pages it tested. It does not mean the page is accessible to everyone.

A few things change how you should read your own number:

  • One critical issue costs as much as ten minor ones. A 90 with a single critical failure, such as a checkout button with no accessible name, is worse in practice than a 90 made of ten cosmetic minor issues. Read the issue list, not just the headline.
  • Repeated issues add up fast. A missing form label in a site-wide template can appear on every page. Fixing the template moves the score more than any other single change.
  • Pages differ. A marketing page and a checkout flow are different risks. An average can hide one badly broken page, so look at the lowest-scoring pages too.
  • Different tools disagree. They run different rules and weight them differently. Compare scores only within one tool, over time.

Why a Perfect Score Is Not Compliance

It is tempting to treat 100 as a finish line, especially when a client or manager asks for a number. Resist it. WCAG has many requirements that automated rules cannot evaluate, and no scanner score amounts to a conformance claim. In the same way, there is no official ADA certificate, a point covered in our post on why no ADA badge or certificate exists. A score is evidence of effort and trend, not proof of anything.

If you need a document that states conformance, that is a different artefact: see our explainer on the VPAT, which should rest on manual testing as well as scans. And if you are weighing legal exposure, this post is not legal advice; talk to a lawyer. For background on the numbers, Seyfarth Shaw counted 3,117 federal-court website accessibility lawsuits in 2025 (ADA Title III (opens in new tab)), which is why a documented, improving record is worth having.

How to Use a Score Well

Used properly, a score is a good management tool. Here is a practical routine:

  • Baseline once. Scan your key pages: home, top landing pages, sign-up, checkout, contact. Record the score and the issue list.
  • Fix by severity. Work critical and serious issues first. They move the number most and usually affect real users most.
  • Fix templates before pages. Navigation, footer, forms and buttons repeat everywhere. Our list of the most common WCAG failures shows where to look first.
  • Rescan after every release. Scores drift down quietly when new content and code ship. A weekly or per-deploy scan catches regressions early. See the guide to accessibility monitoring..
  • Add manual checks. Tab through the page with a keyboard and try a screen reader on your main flows. Our guides on keyboard accessibility and how screen readers work are a start.

You can get a baseline score for free with the WCAG checker, and the pricing page covers ongoing monitoring and history. Pair the number with the WCAG checklist for the criteria a scan cannot judge.

Common Questions

Is my score the same as my Lighthouse accessibility score? No. Lighthouse uses its own subset of rules and its own weighting, so the numbers will differ even on the same page. Use one tool consistently to track change.

Why did my score drop when I changed nothing? Third-party scripts, new content, A/B tests and cookie banners can all change the page between scans. Tools also add rules over time.

Should I put my score on my website? A dated, honest score can show good faith. Be careful with wording: say what was scanned and when, and do not present it as a certification or a compliance claim.

Check your compliance status, free

Run a free WCAG 2.2 scan and see exactly which requirements your site meets and which it misses. No signup required, results in under 30 seconds.

Free scan · No signup required · Results in ~30 seconds

Keep reading

All articles →

Related Resources