accesspatched

Research

Accessibility overlays: the $1,000,000 lie your competitors keep buying

Published 23 July 2026

Do accessibility overlays work? The honest short answer is no, and it is not a close call. Paste in one line of JavaScript, the vendor says, and your site becomes compliant overnight. No developers, no audit, no fuss. If that were true we would sell it too and take the afternoon off. It is not true, and the reason is structural rather than a matter of finding a better-built widget. Below is what the regulator did about the claim, what the accessibility profession found when it tested overlays, and the mechanical reason the whole category cannot deliver what it promises.

What the FTC did about the "instant compliance" claim

Start with the clearest data point on the table. In January 2025 the US Federal Trade Commission ordered the overlay vendor accessiBe to pay $1,000,000 over deceptive claims that its AI product could make websites WCAG-compliant (FTC). Read that slowly. A consumer-protection regulator examined the "your site is now compliant" promise and treated it as false advertising, with a seven-figure price tag attached.

To be precise, because we are always precise about enforcement: this was a US action about advertising claims, not a fine under any accessibility statute, and it is separate from the European picture. As we cover in the EAA enforcement piece, no monetary EAA fines have been issued anywhere yet. But the direction of travel is not subtle. When the government does step in on overlays, it is the overlay vendor writing the cheque, not the businesses who skipped them.

What the accessibility profession found when it tested them

The FTC is not a lone voice. The Overlay Fact Sheet, authored by accessibility engineer Karl Groves and signed by roughly 800 accessibility professionals, states plainly that overlays cannot achieve WCAG conformance, and its signatories pledge never to recommend overlay products that deceptively claim automated compliance (Overlay Fact Sheet). That is close to a professional consensus, and professions do not usually agree on much.

The evidence behind that stance is concrete, not just principled. Groves' expert-witness analysis of 50 sites using accessiBe found they were no more or less accessible than sites without it (Overlay Fact Sheet). Read that again: on a sample of fifty real sites, the widget made no measurable difference to actual accessibility. You are paying an annual subscription for a script that, in that analysis, moved the needle by nothing. On the European side, the European Disability Forum and the International Association of Accessibility Professionals issued a joint statement that overlays do not satisfy European legislation (EDF and IAAP). So the two bodies you would most want on your side, the disability community and the certifying profession, both say the same thing.

Why an overlay cannot fix the underlying problem

Here is the mechanical reason, the part the sales page skips. An overlay is JavaScript that runs in the visitor's browser after your page has already loaded. It does not change your source code. The empty button is still an empty button in your repository. The overlay merely tries to paper over it at runtime, on every single page load, by guessing what the button should have said.

Guessing is the flaw, and it is baked in. The six most common failures, missing alt text, empty buttons and empty links, unlabelled form fields, low-contrast text, and a missing document-language declaration, all live in the markup. That is also exactly where a genuine fix lives. A script that overrides your page from the outside is fighting your own code on every visit, and when its guess is wrong it does not fail quietly. It can announce the wrong thing to a screen reader, trap keyboard focus, or fight the user's own assistive technology, making the experience worse for the very people it claims to help. Some screen reader users have learned to disable overlays on sight for exactly this reason.

Even a flawless overlay would fall short

Grant the vendors their best possible case. Imagine an overlay that perfectly handled everything a machine can detect, with no wrong guesses at all. It would still only reach the roughly one-third of issues that are machine-detectable in the first place. It cannot make a checkout completable by a screen reader user. It cannot fix a reading order that jumps around nonsensically. It cannot judge whether a piece of alt text actually describes the product or just repeats the file name. And "can the customer complete the purchase" is the precise thing European regulators test. A widget, by construction, cannot answer that question, because the question is about the whole journey, not one element inspected in isolation.

What actually works instead

The unglamorous answer is the correct one: fix the code. Label the buttons, describe the images, set the contrast, associate the form fields, declare the language, and then have a human confirm the purchase journey works end to end. It is more work than pasting a script, which is precisely why the script industry exists. But it is the only version that survives a real user and a real regulator meeting your checkout, and unlike a subscription it is a fix you own permanently once it ships. If you want that done properly, our service audits the site, ships the corrections as reviewable code, and hands you a conformance statement rather than a widget.

Common questions

Is accessiBe a scam?

We would not use that word, and we are not lawyers. What we can point to is documented: the FTC ordered accessiBe to pay $1,000,000 over deceptive claims that its AI product could make sites WCAG-compliant, and an expert analysis of 50 sites using it found no accessibility improvement. Draw your own conclusion about whether the product does what its marketing says.

Will an overlay protect me from a lawsuit or an EAA complaint?

There is no evidence it does, and good reason to think it hurts. Regulators and courts test whether a real user can complete the task, and an overlay does not change that outcome. Relying on a widget can also expose you to the vendor's own advertising problems, as the FTC action shows.

I already installed one. What now?

Leave it or remove it, but do not treat it as done. The real work is in your markup. The fastest way to see what the overlay is not fixing is to scan the site with it still installed and look at what remains broken underneath.

That is exactly the kind of work we do: an audit to WCAG-EM, manual screen-reader testing of the real journey, and the fixes delivered as pull requests against your actual codebase, ending with an EN 301 549 conformance statement. If you already run an overlay, we will happily scan the site with it installed. The findings tend to make the point for us.

See where your own shop stands. Our free scan runs the same automated checks a regulator's tester starts with, then a human goes through your site with a screen reader and emails you the findings, in plain language. If your shop passes, we say so.

Get a free scan

Sources

Back to all research