Do accessibility overlays protect you from a lawsuit?
No — and in 2026 they are more often part of the complaint than a defence against it. Here is the evidence, with sources, so you can check it yourself.
What an overlay is
An accessibility overlay is a single line of JavaScript you paste into your site. It loads a toolbar offering options like larger text, higher contrast and a "screen reader mode", and it attempts to patch accessibility problems in the visitor's browser as the page loads. It is sold on a monthly subscription, typically $490 to $1,200 a year for a small site, on the promise of fast or automatic compliance.
The appeal is obvious. Real remediation means changing your markup. An overlay means changing nothing.
What the record shows
The FTC fined the largest vendor $1 million for its compliance claims
In January 2025 the US Federal Trade Commission announced a settlement with accessiBe, finalised in April 2025, requiring the company to pay $1,000,000. The FTC's complaint alleged the company misrepresented that its AI-powered plug-in could make any website compliant with WCAG, and that in practice the plug-in failed to make basic components accessible — navigation menus, form fields and image descriptions among them. The complaint also alleged the company presented third-party articles and reviews as independent when it had undisclosed material connections to the reviewers.
The final order bars accessiBe from claiming its automated products can make any website WCAG-compliant, or keep it compliant over time, unless it has evidence to support the claim.
Source: Federal Trade Commission, accessiBe Inc., matter 2223156; FTC press release, April 2025. This action concerns one named vendor and should not be read as a finding about any other company.
Sites with a widget installed are being sued in large numbers
UsableNet, which tracks US digital accessibility litigation, recorded 983 lawsuits in 2025 filed against websites that already had an accessibility widget present — 24.9% of the 3,948 it counted, up from 722 (22.65%) the year before. Separate analysis of 2025 filings found that 38.5% of the businesses sued already had some accessibility tool installed.
Read that carefully, because it is the whole argument in one number: roughly a quarter of the businesses being sued had already paid for the thing that was supposed to prevent this.
The accessibility profession is close to unanimous
The Overlay Fact Sheet is a joint statement signed by more than 800 accessibility practitioners, researchers and disabled advocates, including contributors to the WCAG, ARIA and HTML specifications themselves. Its position is that overlays are not an effective means of ensuring accessibility. The National Federation of the Blind has passed a formal resolution describing overlay marketing claims as misleading and unproven, and warning that the products can make navigation harder for blind users.
That last point matters and is easy to miss. Many blind users already run a screen reader they have used for years and configured to their preference. An overlay that inserts its own "screen reader mode" can fight with that software rather than help it. Several overlay vendors now ship instructions for how to turn their own product off.
Why it cannot work, mechanically
Set the litigation aside for a moment. There is a straightforward technical reason to expect this outcome.
- It cannot know what your images show. Generating alt text automatically means guessing. "Person holding object" is not a description of your product, and on an e-commerce site the alt text is the product information.
- It cannot know what your buttons do. An unlabelled icon button can be named "button" or guessed from a class name. Neither tells a user whether it adds to the cart or empties it.
- It runs after the page loads, in the browser. Assistive technology may have already begun reading. The markup your server sent — which is what a tester or an expert witness examines — is unchanged.
- It cannot fix a keyboard trap it did not create. If your date picker cannot be escaped with a keyboard, no amount of contrast toggling helps.
- It cannot make a judgement. Whether a form's error message is comprehensible, or whether the reading order makes sense, are human questions.
Automation genuinely does help — it is how this site's own free scanner works, and it reliably finds around half of WCAG failures. The distinction is between detecting problems automatically, which works well, and fixing them automatically without knowing what the content means, which does not.
If you already have one installed
Do not panic, and do not necessarily rip it out this afternoon. Some of its features — a contrast toggle, text resizing — are harmless and occasionally useful to somebody. The mistake is treating it as the remediation rather than as a cosmetic layer on top of one.
- Find out what is actually broken underneath. Run the free scan. It reads the HTML your server sends, which is what the overlay does not change, and it will tell you if a widget is present.
- Fix the markup. The list is usually shorter and more boring than people fear: alt text, form labels, button names, heading structure, contrast.
- Write down what you found and what you did. A dated remediation record is the thing that demonstrates good-faith effort. A subscription receipt is not.
- Then decide about the widget. Once the underlying site works, it is a genuine preference question rather than a compliance one.
What we are, for the avoidance of doubt
We sell a fixed-price audit and remediation package, so we are not a neutral party here and you should weigh this page accordingly. That is exactly why every claim above is attributed to a source you can check without taking our word for anything: the FTC's published order, UsableNet's litigation counts, a public document with 800 named signatories.
We also do not claim the thing overlays are criticised for claiming. Nothing we sell guarantees compliance or immunity from a lawsuit, because nothing anyone sells can. What a real audit gets you is an accurate list, the fixes, and documentation that you acted.