Reviewed November 11, 2026

Accessibility Overlays: The FTC Fine, the Lawsuits, and What They Actually Do

An accessibility overlay is a widget you install on your store that promises to make it accessible, usually by adding a toolbar with text-size and contrast controls. It does not fix your site. It sits on top of it, and in April 2025 the FTC ordered accessiBe, the largest overlay vendor, to pay $1 million for deceptive claims that its product could make websites compliant with WCAG. UsableNet counted 1,416 lawsuits in 2025 against companies using accessibility widgets, more than 1,000 of them in 2024 alone. And 69 to 72 percent of disabled users who have used overlays rate them as not effective. The overlay does not fix the underlying code, it does not stop a lawsuit, and it can make the site worse for the people it claims to help. Fix the code instead.

What the overlay promises

The pitch is simple and it is aimed at a real fear. A store owner gets a demand letter, or reads about a competitor who did, and a vendor offers a widget: install one line of JavaScript, get a toolbar with text-size controls, contrast toggles, and a screen-reader mode, and the site is accessible. The price is a monthly subscription, the install takes minutes, and the vendor's marketing says the widget brings the site into compliance with WCAG. For a merchant who does not write code, it sounds like the only option that fits the budget and the timeline. That is the whole business model, and it is why overlays are on so many stores.

What the regulator said

In April 2025, the Federal Trade Commission issued a final order against accessiBe, the largest overlay vendor, requiring it to pay $1 million and barring it from making deceptive claims that its product could make any website compliant with WCAG or accessible to people with disabilities. The FTC's complaint was specific: the company had claimed its AI-powered tool could make websites accessible, and it could not. The order did not ban overlays. It banned the claim that an overlay makes a site compliant, because that claim was false. The vendor's own marketing had said the widget fixed accessibility, and the regulator said it did not.

What the lawsuits say

UsableNet counted 1,416 lawsuits in 2025 against companies using accessibility widgets, with more than 1,000 of them filed in 2024 alone. The number is not a coincidence. An overlay is visible on the site, which makes it easy for a plaintiff's firm to find, and it does not fix the underlying failures, which makes it easy for a plaintiff's firm to document. A store with an overlay still has unlabeled form fields, still has images without alt text, still has keyboard traps, and now it has a widget that interferes with the assistive technology the plaintiff uses. The overlay does not stop a lawsuit. It advertises the site to the people filing them, and it adds a new failure on top of the old ones.

What the users say

The people overlays claim to help are the ones who rate them worst. In surveys of disabled users who have used overlays, 69 to 72 percent rate them as not effective, and more than 800 practitioners signed the Overlay Fact Sheet, a public statement that overlays do not fix accessibility and can make it worse. The reason is straightforward. A screen reader user already has a screen reader, with their own speech rate, their own navigation habits, and their own settings. An overlay that injects its own controls, its own focus behavior, and its own markup on top of the page disrupts all of that. The toolbar is not a substitute for a screen reader, and the site underneath it is still broken. The honest fix is the unglamorous one: remediate the code, in the order that matters most, and stop paying a monthly fee for a toolbar that makes the problem harder to see.

Frequently asked questions

Does an accessibility overlay protect my store from a lawsuit?

No, and the evidence points the other way. UsableNet counted 1,416 lawsuits in 2025 against companies using accessibility widgets, more than 1,000 of them in 2024. An overlay is not a defense in a demand letter, and plaintiffs' firms know the difference between a widget and a fix. A store that has remediated its code is in a stronger position than a store that bought a toolbar.

Why do disabled users dislike overlays?

Because overlays interfere with the tools they already use. Screen reader users have their own settings, their own speech rate, their own navigation habits, and an overlay that injects its own controls, its own focus behavior, and its own markup on top of the page disrupts all of it. In surveys, 69 to 72 percent of disabled users who have used overlays rate them as not effective, and many describe them as actively harmful.

What should I do instead of installing an overlay?

Fix the underlying code, in the order that matters most. Keyboard operability first, then form labels, then alt text, then contrast, then focus visibility. Those five fixes cover the failures that show up in nearly every audit, and they are permanent: they survive a theme update and they do not depend on a third-party script loading. A one-time remediation is cheaper than a year of overlay subscription plus a lawsuit.

Are there any overlays that are legitimate?

There are tools that help with remediation, automated scanners, and testing services, and those are legitimate. The problem is the widget that claims to fix a site by sitting on top of it, usually for a monthly fee, with a toolbar that appears to visitors. A tool that finds problems for you to fix is a tool. A tool that claims the problems are fixed because the toolbar is installed is a claim the FTC has now fined a vendor $1 million for making.