Accessibility ≠ Overlay: an automated 100/100 does not mean WCAG conformance

📅 October 2026   ⏱ 9 min

A perfect score can be a useful signal, but it describes the checks run by that tool and how they are weighted. In Lighthouse, the accessibility score is a weighted average of its automated audits; manual audits do not affect that score.

Lighthouse itself states the limitation

Chrome documentation is clear: passing every automated audit and scoring 100 in accessibility does not guarantee that the audited page is accessible. Manual testing remains important. A 100/100 score therefore does not by itself mean WCAG conformance.

WCAG is not a score

WCAG defines conformance criteria, not an overall mark from 0 to 100. W3C states that no tool alone can determine whether a site meets accessibility standards; knowledgeable human evaluation is required.

What a 100 can hide

A page can pass automated checks and still have barriers requiring manual review: focus order, keyboard interaction, meaningful text alternatives, complex component behaviour or clear instructions. Coverage also depends on which pages, states and content were evaluated.

Tools remain extremely valuable

This does not reduce the value of Lighthouse, axe or other tools. They are excellent for finding issues quickly and repeatedly during development. axe-core says it automatically finds a portion of WCAG issues and returns “incomplete” cases when manual review is needed. The mistake is turning a score into a certification the tool was not designed to provide.

What does this have to do with overlays?

The same caution applies to claims of “automatic compliance”. Detecting, modifying or scoring what can be identified programmatically does not by itself demonstrate full website conformance. More automation can improve coverage, but it does not remove context, interaction or human judgement.

What about Blind Reader?

Blind Reader belongs on the user-assistance side. It can help a person access or work with content, but it does not turn a score into WCAG conformance, certify a website or replace evaluation. 100/100 means 100/100 for the checks that make up that score; it does not automatically mean “this website conforms to WCAG”.

Fuentes / Sources

🧑‍🦯 Blind Reader
Intent narrator ready.

Accessibility guide

This is a functional summary, not a literal reading.

Go to primary goal Jumps to the main action area (form, list or contact).

You are on a listing page. The main goal seems to be: to explore options.

Top actions: Browse results, Filter or sort.

There are 10 key sections you can jump to.

Confidence: 68%

Before continuing:

  • Handle cookies/consent Reason: Detecté un aviso relacionado con cookies/consentimiento. — Recommended route: Contenido principal

Recommended actions

  • Browse results Reason: Parece haber un listado de elementos. — Recommended route: Listado
  • Filter or sort Reason: Detecté términos de filtros/ordenación. — Recommended route: Listado

Go by goals

Choose what you want to do. I will explain it, then ask before jumping.

Confirmation mode

Choose how often I should ask before jumping.



Learning scope (only for “first time”)

Site: remember this goal across the whole site. Page: remember per URL.


  • Go to Home
  • Go to About
  • Go to BlindReader
  • Go to Withdrawal Button
  • Go to Services
  • Go to Blog
  • Go to Contact
  • Go to English
  • Go to Español
  • Go to Català
  • Go to Polski
  • Go to Română
  • Go to Italiano
  • Go to Français
  • Go to Svenska
  • Go to Deutsch
  • Go to Nederlands
  • Go to Português
  • Go to article content
  • Go to comments
  • Go to end of article
  • Back to News / Blog
  • Previous post
  • Next post
  • Handle cookies/consent Important: this may block navigation.
  • Browse results
  • Filter or sort

Guided navigation

The guide announces one section at a time.

How it works: Start guide announces the first key section and scrolls to it. Next moves to the following section. To move focus to the section, use Go to current section. Stop exits.

Status: Guide inactive

Go to current section This link updates as the guide advances.

This article has approximately 374 words.

Moves focus to the start of the content, skipping menus and secondary elements.

About Blind Reader

Blind Reader is an accessibility assistant that analyzes each page and narrates its purpose, key sections and recommended actions — designed for screen reader users.

Compatible page builders: Works with any WordPress theme or builder: Divi, Elementor, Gutenberg, WPBakery, Avada and others. It reads the real content of the page, not the builder markup.

Does it interfere with your content? No. Blind Reader adds an accessible panel above the page but does not modify, hide or alter any existing content or styles on your site.

How does it work? It analyzes the page structure (headings, links, forms, landmarks) and generates a functional summary. The guide and goals help navigate without having to scan the whole page.

Keyboard shortcut: Press Alt + G to jump directly to the first goal.