Does a 100 Lighthouse Accessibility Score mean my site is WCAG compliant?

No. It means your site passes every automated check Lighthouse runs, which covers a meaningful but partial subset of WCAG 2.1's success criteria. Manual testing — keyboard navigation, screen reader use, focus order — can still surface failures on a page that scores 100.

How many WCAG success criteria can automated tools like Lighthouse actually test?

Estimates vary, but most accessibility professionals put the share of WCAG 2.1 success criteria that automated tools can reliably verify somewhere around a third to half. The rest need a human — a real keyboard, a real screen reader, or a real reading of the content.

Is Lighthouse a bad tool for accessibility testing?

No — it's a legitimate, well-built first layer. It catches real issues quickly and for free, and it's excellent for catching regressions in CI. The mistake isn't using Lighthouse; it's treating its score as the finish line.

What's the difference between Lighthouse's score and WCAG's conformance levels?

Lighthouse produces one 0-100 number per audit. WCAG doesn't produce a score at all — each success criterion is either met or not met, and a page conforms to a level (A, AA, or AAA) or it doesn't. They're structurally different measurement systems, not two versions of the same scale.

Can I use Lighthouse to prove WCAG 2.1 AA compliance for legal purposes?

Not on its own. Lighthouse's checks map to a subset of WCAG success criteria, but legal and regulatory contexts — like the European Accessibility Act — typically expect evidence of both automated and manual testing, since a passing Lighthouse score doesn't demonstrate keyboard or screen reader usability.

Why did my Lighthouse Accessibility score change even though I didn't touch accessibility code?

Accessibility results are usually more stable than Performance, but third-party scripts that inject DOM content late — ads, chat widgets, banners — can change what Lighthouse actually sees on the page at analysis time, shifting the score without any change on your end.

What should I check manually that Lighthouse won't catch?

At minimum: whether you can complete every interactive flow using only a keyboard, whether focus moves in a sensible order, whether removing your mouse ever traps you inside a component, and whether a screen reader announces dynamic changes the way a sighted user would expect.

Does GetGDPRScan replace Google Lighthouse?

No, and it isn't trying to. GetGDPRScan runs its own set of 27 WCAG-mapped checks with severity-weighted scoring, and on paid reports also runs a live Lighthouse accessibility audit alongside its own findings — using Lighthouse as one input, not a replacement for it.

How often should I re-check my site's accessibility?

Ideally every time you ship a change that touches markup, styling, or third-party scripts — a passing score today doesn't guarantee anything about a page six months and four plugin updates later. That drift is exactly what continuous monitoring is meant to catch.

Accessibility Module

Lighthouse vs WCAG: Does a Perfect Accessibility Score Mean You're Compliant?

Q: What engine does Lighthouse use for its accessibility audits?

Most of Lighthouse's accessibility checks run on axe-core, the open-source testing engine maintained by Deque Systems — the same engine that powers several browser extensions and CI accessibility tools.

Google's free tool is genuinely useful — it just wasn't built to answer the compliance question by itself.

Quick answer

Google Lighthouse's Accessibility Score is a fast, free, automated audit built largely on the axe-core testing engine. It reliably catches things a script can verify without human judgment — missing alt attributes, low color contrast, invalid ARIA, unlabeled form fields — but it cannot test keyboard navigation, focus order, or whether a screen reader user can actually use the page. A 100 score means you passed every automated check, not that you meet WCAG 2.1 AA.

By GetGDPRScan Editorial · Last updated 2026-07-31

Open Chrome DevTools, run a Lighthouse audit, see a 95 or 100 in the Accessibility category, and it's tempting to close the tab and call the job done. Lighthouse is fast, it's free, it ships inside every Chrome install, and a clean score feels like a verdict.

That trust is only half-earned. Lighthouse is a solid tool for exactly what it was built to do — it's just that "what it was built to do" covers less of WCAG than most people assume. This guide walks through what the Lighthouse Accessibility Score actually checks, what it can't check by design, and what that gap means if you're trying to claim real WCAG compliance rather than just a good score.

What Is Google Lighthouse?

Lighthouse is a free, open-source auditing tool from Google. You can run it straight from the Lighthouse panel in Chrome DevTools, as a command-line tool, or as a Node package inside a CI pipeline — there's no account, license, or setup beyond loading a page in Chrome and clicking "Analyze page load."

A Lighthouse report scores a single page across four categories: Performance, Accessibility, Best Practices, and SEO. Each category is graded independently on a 0-100 scale, so a page can score 100 on Accessibility while scoring 40 on Performance, or the reverse — one score says nothing about the others.

Accessibility is one slice of that report, not the whole point of it. Lighthouse is a general page-quality auditor that happens to include an accessibility category — worth keeping in mind, because it shapes how deep that category can realistically go.

What Does the Lighthouse Accessibility Score Actually Check?

Most of Lighthouse's accessibility audits run on axe-core, the open-source accessibility testing engine maintained by Deque Systems — the same engine behind several browser extensions and CI accessibility tools. Because every audit runs without a human in the loop, each one has to be something a script can verify purely by inspecting the rendered page.

That still covers real, common problems. A typical Lighthouse Accessibility run checks things like:

•Image alt text — flags <img> elements with no alt attribute at all
•Form labels — flags inputs with no associated <label>, aria-label, or aria-labelledby
•Color contrast — computes the contrast ratio between text and its background and checks it against WCAG thresholds
•Semantic HTML — flags structural issues like non-sequential heading levels or lists built from the wrong elements
•ARIA usage — checks that ARIA attributes have valid values and aren't applied where they conflict with native HTML semantics
•Language attribute — checks that <html lang="..."> is present and set to a real language code
•Button and link names — flags buttons and links with no accessible text, like an icon-only link with no aria-label

What Lighthouse Does NOT Check

Automated tools test the page, not the person using it — and a large part of WCAG only reveals itself when an actual human interacts with the page the way someone with a disability would.

Most accessibility professionals estimate that only a third to half of WCAG 2.1's roughly 50 success criteria can be reliably verified by an automated tool at all, Lighthouse included. The rest, including everything below, needs a person:

•Whether alt text is meaningful — Lighthouse confirms alt="..." exists, not whether it says "IMG_4021.jpg" or "Warehouse team, June 2026"
•Keyboard navigation — whether every interactive element can be reached and operated using only Tab, Shift+Tab, and Enter, with no keyboard trap
•Logical focus order — whether tabbing through a page, especially through modals, custom dropdowns, or single-page-app routing, follows a sensible order
•Screen reader usability — whether the page actually makes sense read aloud, including dynamic updates like form errors or loading states
•Understandable content — WCAG's requirements around plain language and predictable navigation, which need a human reader to judge
•Caption accuracy — Lighthouse can flag a video with no <track> element, but not whether existing captions are actually correct
•Anything that only shows up during interaction — time limits, motion and flashing content, and other criteria that don't exist at page load

Lighthouse vs WCAG: The Real Differences

Lighthouse and WCAG aren't really comparable on the same axis — one is a tool, the other is a standard — but it helps to see the differences side by side:

Lighthouse and WCAG, side by side

Aspect	Google Lighthouse	WCAG
Scope	One page, one snapshot, across 4 categories (Performance, Accessibility, Best Practices, SEO)	All content and every user flow on a site, evaluated against defined success criteria
Automatic checks	Around 30 accessibility audits, all fully automated	A minority of success criteria have automatable equivalents
Manual checks	None — Lighthouse can't tab through a page or use a screen reader	Roughly half of WCAG 2.1's success criteria need human testing to verify
Score	A single 0-100 number, weighted by estimated impact	No numeric score — each success criterion is simply met or not met
WCAG compliance	Not a conformance test; approximates a subset of WCAG 2.1 criteria	The actual standard compliance is measured against, with three levels: A, AA, AAA
Best use case	Fast regression checks, CI pipelines, catching obvious issues early	Formal accessibility claims — EAA, ADA, EN 301 549, and similar regulatory contexts

Why the Scores Can Be Different

It's entirely possible for a site to score Lighthouse Accessibility: 100 and still fail a WCAG 2.1 AA audit — not as an edge case, but as the normal outcome for a page whose only accessibility work has been "pass the Lighthouse audit." A few concrete ways that happens:

•Every image has alt text, but it's decorative filler ("image", "photo1") instead of a real description — Lighthouse only checks that the attribute exists, satisfying the letter of WCAG 1.1.1 without meeting its intent
•A custom modal or dropdown opens correctly on click, but once it's open, keyboard focus gets trapped inside it — or never moves into it at all — because Lighthouse never actually tabs through the interface to find out
•Text passes the automated contrast check at page load, but a hover state, a dark-mode toggle, or dynamically inserted content later drops the contrast below threshold — Lighthouse only evaluates the DOM as it exists at load time
•A form shows a validation error visually in red text, but the error isn't announced through an ARIA live region — a sighted user sees it instantly, a screen reader user may never know it happened
•Heading levels are structurally valid (h1, h2, h3 in order) but the headings themselves don't describe the sections they introduce — passing the structural check while failing the intent behind it

Should You Trust Lighthouse?

Yes — with the right expectations. Lighthouse is a well-built, free, fast tool that catches real, common problems, and it's genuinely good at what it's for: an early warning system, not a final verdict.

Where it earns its keep is continuous, low-friction checking — running it in a CI pipeline so a pull request that removes an alt attribute or drops contrast below 4.5:1 gets flagged before it ships, rather than discovered later by a user or an auditor. That's a real, valuable job, and Lighthouse does it well.

Where it falls short is treating a high score as a finish line. A 100 tells you that you passed every check a script can run without a person behind the keyboard — it doesn't tell you whether a person can actually use the page. Full WCAG conformance work usually needs both: automated tools like Lighthouse for continuous coverage, and manual testing for everything a script structurally cannot judge.

How GetGDPRScan Complements Lighthouse

GetGDPRScan's accessibility module isn't a replacement for Lighthouse — it runs alongside it, aimed specifically at closing more of the WCAG gap than a general-purpose page auditor covers in its one accessibility category:

•27 individual checks mapped directly to WCAG 2.1 success criteria — covering images, headings, links, forms, tables, media, color contrast, ARIA roles, iframe titles, and more — rather than accessibility being one category inside a broader page-quality report
•Severity-weighted scoring, so a missing skip-link doesn't carry the same weight as a form with no labels at all
•Findings written in plain language with a specific fix attached, so a flagged issue reads as a potential WCAG problem and how to fix it, not just a rule ID
•On paid reports, GetGDPRScan runs a live Google Lighthouse accessibility audit against the same page alongside its own 27 checks — cross-verifying results instead of asking you to trust one engine's opinion
•An optional monitoring plan that re-checks a site on a schedule, since a page that passed cleanly can regress after the next plugin update, theme change, or third-party script

Conclusion

None of this — GetGDPRScan included — amounts to a legal certificate of WCAG compliance. No automated tool, ours or Google's, can issue one; that still requires the manual testing and human judgment this article has walked through. What a broader, WCAG-mapped scan helps identify is a wider net of potential issues, caught before a real user, a complaint, or an auditor finds them first.

If Lighthouse is the only accessibility check your site has had, that's a reasonable starting point — not a finish line. Run a free WCAG scan to see how many of the 27 checks your site passes today, and where the gaps are.

Key takeaways

•Lighthouse's Accessibility Score only tests what a script can verify without human judgment — a meaningful subset of WCAG, not all of it.
•A 100 Lighthouse score is a strong technical signal, not proof of WCAG 2.1 AA conformance.
•Keyboard navigation, focus order, screen reader usability, and meaningful alt text almost always need manual testing.
•Lighthouse and WCAG measure different things: one produces a 0-100 score, the other is a pass/fail standard with conformance levels.
•Automated tools like Lighthouse and GetGDPRScan are complementary layers of a larger accessibility process, not substitutes for manual review.

FAQ

European Accessibility Act & WCAG: Who Must Comply and By When

Who's legally required to meet WCAG, and by when.

What Automated Compliance Scanners Can (and Can't) Detect

The broader case for what any automated scan — Lighthouse included — can and can't tell you.

How Website Compliance Scanning Actually Works

How GetGDPRScan's accessibility module reads a rendered page.

Accessibility Checker

Run a free WCAG 2.1 scan and see your site's 27-check breakdown.

Sources