Overlay widget lawsuits: what actually happened

Overlay widgets were sold on a simple promise: install a script, get an accessible site, avoid a lawsuit. Over 800 lawsuits later, against businesses that had overlays installed, that promise hasn't held up. Here's what happened, and what a defensible response actually looks like.

What overlays promise

The pitch is speed and simplicity: add one line of JavaScript, and an overlay widget adjusts your site in the visitor's browser — font size and contrast controls, some automated ARIA attribute fixes, sometimes a compliance badge for the footer. For a business with no accessibility work done at all, that's an appealing shortcut, and it does provide some real, visible accommodations to visitors who use the toggles.

The FTC action against accessiBe

In April 2025, the FTC fined overlay vendor accessiBe $1 million for deceptive claims that its overlay provided automated compliance. The FTC order also covered misleading advertising practices tied to those claims. It was a signal that regulators were no longer taking “automated full compliance” marketing at face value.

Why plaintiffs sue anyway

An overlay changes what a visitor's browser renders at runtime. It does not change your underlying HTML, CSS, or application code. Many plaintiffs' firms now run automated pre-suit scans that read source code directly — the same kind of scan that sees through a runtime overlay to the issues underneath. If the underlying code still has missing alt text, unlabelled form fields, or keyboard traps, an overlay sitting on top of the page doesn't change what that scan finds.

That's the core reason more than 800 businesses using overlay widgets have been sued despite having an overlay installed: the overlay addressed what a human visitor sees, not what the code actually contains.

The EU Commission position

For businesses operating in the EU, the European Commission's position adds a further layer: overlay widgets alone do not achieve EAA compliance. That's a clear signal that an overlay cannot be the whole of a compliance strategy under Directive (EU) 2019/882.

What defensible actually looks like

None of this means overlays are useless as a small accommodation for visitors. It means they can't be the entirety of your response. A more defensible position combines three things: fix the underlying code issues so the site is actually more accessible, not just cosmetically adjusted; publish an accessibility statement that says what standard you're assessed against and what your conformance status is; and keep a dated record of continuous effort — scans, fixes, and reviews over time — rather than a one-off badge.

That's the same combination regulators and courts have been pointing toward: code-level fixes plus documented, ongoing effort.

This article is general information about EU accessibility law, not legal advice.