What accessibility overlay widgets get wrong — and why they can increase your liability

The pitch is irresistible. One line of JavaScript, a small accessibility icon in the corner of your site, and you're compliant — no audit, no remediation, no developer time. For a few hundred dollars a year, a problem that sounded expensive becomes someone else's.

If that sounds too good to be true, the regulators agree with you.

The FTC fined one of the biggest providers $1 million

In January 2025, the US Federal Trade Commission filed a complaint against accessiBe over its accessWidget product. The company had claimed the tool "can make any website compliant with the Web Content Accessibility Guidelines (WCAG)."

The FTC alleged those claims were false, misleading, or unsubstantiated — that the widget simply did not make all customer websites WCAG-conformant. The complaint also alleged the company paid for third-party reviews formatted to look like independent opinions, without disclosing the connection.

The FTC approved the final order in April 2025: a $1 million payment, and a bar on representing that its automated products can make any website WCAG-compliant, or keep it that way, without evidence to back it up.

That's not a competitor's marketing claim. That's a regulator's finding about the core promise of the product category.

Sites with overlays are still getting sued

The stronger argument isn't regulatory — it's what happens in practice.

In US web accessibility litigation, overlay widgets show up constantly, and not on the defence's side:

• 1,023 US lawsuits in 2024 — about 25% of the total — explicitly cited an overlay widget as a barrier, not a fix.
• 456 Lawsuits in 2025 (22.6%) targeting websites that were running an overlay or widget.
• $1M FTC settlement with accessiBe over claims its AI widget could make any site WCAG-compliant.

A note on those numbers, because it matters: that's United States ADA litigation, which is simply where the large public dataset lives. Ontario organizations are covered by the AODA instead, which works differently — a compliance-reporting regime rather than a private-litigation culture. What carries across jurisdictions isn't the lawsuit risk. It's the technical finding underneath it: the overlay didn't fix the site.

Why they don't work

An overlay is JavaScript that runs after your page loads and tries to patch accessibility problems on the fly. That's a hard problem, and it fails in predictable ways:

• It can't infer meaning. An overlay can detect an image with no alt text. It cannot know that the image is your pricing table, or your logo, or a decorative flourish that should be skipped entirely. Guessed alt text can be worse than none.
• It doesn't fix the code. The underlying markup — the thing screen readers, switch devices, and braille displays actually consume — is unchanged.
• It can fight the user's own tools. People who rely on assistive technology have already configured it precisely. An overlay injecting its own keyboard handling and focus management on top can actively interfere.
• It arrives late. It runs after the page does, so there's a window where none of it applies.

To be fair: the better products do offer genuine preference controls — text sizing, contrast toggles, motion reduction. Those are real conveniences for some visitors. They just aren't conformance, and the people they help most usually have those settings in their OS or browser already.

The uncomfortable part

An overlay is visible. It announces to anyone looking — including someone deciding whether to file a complaint — that you knew accessibility was an obligation and chose the cheapest possible response.

Worse, it can create false confidence internally. A team that believes the widget handled it stops asking. Meanwhile the actual barriers — keyboard traps, invisible focus, unlabelled fields — are all still there.

What actually works

Nothing exotic. Fix the code.

Semantic markup, real labels, visible focus, keyboard paths that work, contrast that passes. Tested by a person on a keyboard and with a screen reader, because that's the only way to know. It's more work than pasting a script tag, and it's the only approach that produces a site that's genuinely usable — and a compliance claim you can defend.

If you're filing an AODA compliance report this December and an overlay is the reason you were planning to tick the box, that's worth a second look before you sign. See Accessibility Audits & AODA Compliance for what a real assessment involves.