Do accessibility overlay widgets protect you from lawsuits?

If you have been sold an accessibility widget as a one-line fix for ADA risk, here is the short version: the record does not support the promise. A federal regulator fined the best-known overlay maker a million dollars over its claims, and businesses running overlays kept getting sued right through 2025. This is what the data actually shows, and what to do instead. None of this is legal advice.

What an overlay is, and what it promises

An accessibility overlay is a snippet of JavaScript you paste into your site. It loads a widget, usually a small accessibility icon, that lets visitors adjust contrast, font size, and similar settings, and it runs automated scripts that try to patch accessibility issues as the page loads. The pitch is that this one line makes your site accessible and keeps you out of court.

The appeal is obvious. Real accessibility work means auditing your site and fixing code, and a widget promises to skip all of that for a monthly fee. The problem is that the promise has not held up, in the data or with regulators.

The FTC fined one of the largest overlay makers $1 million

The Federal Trade Commission found that accessiBe, one of the largest overlay vendors, had advertised its tool as making websites accessible and compliant when it did not, and in 2025 it finalized an order requiring the company to pay $1 million. When a federal consumer-protection agency puts a number on the gap between an accessibility overlay's marketing and its results, that is not a detail to wave away.

Overlay users kept getting sued

The litigation data is just as direct. One industry tracker found that in 2023 roughly 700 businesses with an accessibility widget installed were sued anyway, about 15 percent of all digital accessibility cases that year, and overlay users kept landing in court through 2025. If overlays reliably closed legal exposure, that number would be near zero. It is not.

The pattern is visible in individual cases. In one, an online retailer bought a UserWay subscription, was sued anyway by a blind user who could not use the site, and then turned around and sued the overlay vendor, alleging its accessibility claims were false. A magistrate judge has recommended that key parts of that case proceed. A tool that leaves you exposed enough to be sued, and then to sue your vendor, is not the shield it was sold as.

Why overlays do not close the risk

The reason is structural, and once you see it the data stops being surprising. An overlay sits on top of your website and adjusts what a visitor sees at the moment the page loads. It does not change the underlying code. The barriers that a screen reader or a keyboard user actually hits, an unlabeled form field, an image with no text alternative, a control that keyboard focus cannot reach, largely live in that code. A layer that never touches the code cannot be relied on to remove the problems that live in it.

The accessibility community has documented this in detail. Hundreds of accessibility professionals and disabled users have signed on to a public fact sheet cataloging where overlays fall short in practice. When the people who actually use assistive technology say a tool does not work for them, that is the evidence that matters most.

What actually reduces the risk

The work that lowers your exposure is the work an overlay skips. Find the real issues with an audit against WCAG 2.1 AA, fix them in the code worst-first, confirm the fixes, and keep the site from drifting back out of shape. We walk through that in detail in our guide to what actually reduces website-lawsuit risk.

The first step is seeing the accessibility issues on your pages, which is exactly what a scan gives you. Run a scan and you get a specific, prioritized list of the accessibility issues on your real pages, so you can fix the code instead of hiding it behind a widget. It will not do the remediation for you, and it does not pretend to. What it does is give you a specific, prioritized list of the accessibility issues on your pages, which an overlay never surfaces.

FAQ

Are accessibility overlays illegal?

No. Overlays are legal products. The issue is effectiveness, not legality: the FTC's 2025 action against accessiBe concerned misleading claims about what an overlay delivers, and the litigation data shows overlay users still get sued. You can run one, but do not treat it as legal protection.

If I already use an overlay, what should I do?

Keep or remove it as you like, but do not rely on it for compliance. Get an actual audit of your site against WCAG 2.1 AA, remediate the real issues in your code, and treat the widget as, at most, a minor convenience feature rather than a fix.

Does an overlay help or hurt in a lawsuit?

The documented cases show overlay users being sued at scale, and in at least one case the overlay itself became the subject of a fraud claim. It is not a defense you can count on. Real remediation is.