Skip to main content

Do accessibility overlays work?

Short answer: not for the thing they are sold for. They can add a preferences panel. They cannot make an inaccessible website accessible, and the record on that is now unusually clear for a question people still argue about.

$1M

FTC settlement with accessiBe in 2025 over its compliance marketing

456

US lawsuits in H1 2025 against sites that already had an overlay

22.6%

Share of all such lawsuits that period which hit overlay-equipped sites

What is promised, and what is true

“One line of code makes your site compliant”

An overlay cannot know what your images show, cannot restructure your headings, cannot write your form labels and cannot fix your checkout. Those live in your pages, and the overlay never touches them.

“AI handles the accessibility work for you”

Automated tooling reliably detects about a third of WCAG failures and can safely repair a smaller fraction still. Anything claiming to close the whole gap automatically is claiming something no scanner can do, including ours.

“It protects you from lawsuits”

Sites carrying overlays are sued at scale. accessiBe appeared in 258 US web accessibility cases in 2024, UserWay in 187. Having the widget did not prevent the case and in several instances was cited as evidence the owner knew there was a problem.

“Disabled users prefer it”

Hundreds of accessibility practitioners and screen reader users have signed public statements asking site owners not to use them. The people the product claims to serve are the people objecting loudest.

Why the technology cannot deliver it

An overlay is JavaScript that runs after your page has loaded, in the visitor's browser. Everything it can see is the finished HTML. It cannot see the photograph, so it cannot describe it. It cannot know that the bold paragraph was meant as a section heading. It cannot know which of three unlabelled fields is the email address.

It also arrives into a browser where a screen reader is already running. Assistive software has its own keyboard model, its own announcement queue and its own settings that the visitor has spent years tuning. An overlay that overrides those is not adding help; it is competing with the help already there.

This is not a matter of one vendor doing it badly. It is what the position in the stack allows.

If you already have one installed

  1. 1

    Scan your site with the overlay still running

    You will see the failures it is not fixing. That report is the honest picture of where you stand, and it is what an investigator would find.

  2. 2

    Do not remove it in a panic

    If it is providing a preferences panel some visitors now rely on, take it out deliberately rather than overnight. It is not helping your compliance, but abrupt removal helps nobody either.

  3. 3

    Fix the failures in the pages

    Contrast in your theme palette, alt text in your media library, labels in your forms. Most sites clear the bulk of it in a day or two of focused work.

  4. 4

    Then test by hand

    Keyboard only, then with a screen reader. This is the part no product can do for you, and it is the part that decides whether someone can actually buy from you.

See what your overlay is not fixing

The scanner detects the common overlays by name and lists the failures still present underneath them.

Scan my page free

Common questions

Do accessibility overlays make a website ADA compliant?
No. Overlays run in the visitor's browser after your pages have already loaded, so the pages themselves are unchanged. In the first half of 2025, 456 US accessibility lawsuits were filed against websites that already had an overlay installed, which is 22.6% of all such cases that period.
Has any overlay company been penalised for its claims?
Yes. In 2025 the US Federal Trade Commission reached a $1 million settlement with accessiBe, finding it had misled businesses by marketing its widget as a guaranteed compliance solution.
Why do blind users dislike overlays?
Screen reader users already have software tuned to how they work. An overlay that tries to take over announcements, keyboard shortcuts or focus fights with that software rather than helping it. Many blind users specifically ask sites to remove them.
Is there any legitimate use for an accessibility widget?
A widget that only offers optional preferences, such as larger text or a high contrast theme, and makes no compliance claim, is harmless. The problem is not the button. It is selling that button as a substitute for fixing the site.
What should I do instead?
Find out what is actually broken, fix the pages themselves, and test with a keyboard and a screen reader. It is slower than pasting a script and it is the only approach that survives contact with a real user or a real lawyer.