The Overlay Reckoning: One Year After the FTC's $1M accessiBe Fine

A reckoning that was a long time coming

For years, a single seductive promise propped up an entire industry: paste one line of JavaScript onto your site, and an "accessibility widget" will make it compliant overnight. No audit, no code changes, no developers. It was too good to be true — and in April 2025, a federal regulator said so in writing.

The Federal Trade Commission finalized a $1 million order against accessiBe for deceptively marketing its overlay as a tool that made websites WCAG-compliant. The vote was 5–0. A year later, it is worth being blunt about what that means: the central marketing claim of the overlay industry has been ruled deceptive by the United States' consumer-protection authority, and the data backs the regulator up.

The statistic that buried the myth

If overlays worked, the sites that installed them would be sued less. The opposite is true. EcomBack found that 22.64% of websites sued for accessibility in the first half of 2025 already had an overlay installed at the time of the lawsuit.

Read that again. Nearly a quarter of sued sites had paid for the "solution" and were sued anyway. Installing an overlay is not correlated with protection — if anything, the detectable widget signature makes a site easier to identify and, in many cases, introduces new barriers that hand a plaintiff fresh ammunition.

Why overlays cannot do what they claim

This is not a vendor-quality problem that a better widget will fix. It is structural. Web accessibility is mostly about the underlying HTML — semantic structure, programmatic labels, focus order, meaningful alternatives. A script that runs after the page loads cannot reliably:

• Know what an image actually depicts (auto-generated alt text is frequently wrong or useless).
• Restructure non-semantic markup into something a screen reader can navigate.
• Repair a keyboard trap baked into a custom component.
• Coexist cleanly with the assistive technology a disabled user already runs — overlays often fight the user's own screen reader.

That last point is the one the marketing never mentions. Many people with disabilities have spent years tuning their own assistive technology. An overlay that hijacks the experience can make a site less usable for the very people it claims to help — which is why the National Federation of the Blind and a broad coalition of disability advocates have publicly rejected overlays as a compliance strategy.

The data keeps getting worse, not better

You might expect that after a decade of lawsuits and a billion-dollar accessibility-tech industry, the web would be getting more accessible. It is not. The 2026 WebAIM Million report found detectable WCAG failures on 95.9% of the top one million home pages — up from 94.8% the year before, reversing years of slow improvement. Average errors per page rose more than 10%.

Overlays were sold as the scalable answer to exactly this problem. The aggregate data says they have not moved the needle on real accessibility at all — they have mostly moved money. (We dig into the broader numbers in our 2026 WebAIM Million analysis, and the relationship between overlays and lawsuits in our overlay study.)

What honest accessibility looks like

Accessibility is engineering, not a plugin. The work is well understood and entirely doable:

• Audit the real code against WCAG 2.1 AA — automated scanning plus manual testing with a keyboard and a screen reader.
• Fix the underlying barriers — start with the "Big Six" that dominate every data set, then work the full requirements.
• Build accessibility into your process so new features ship usable instead of being patched after a complaint.
• Publish an honest accessibility statement describing your conformance and how to report problems.

None of this is glamorous, and none of it fits on a single line of JavaScript. But it is the only approach that actually helps disabled users and holds up when a demand letter arrives. For the full case against quick-fix widgets, see why overlays do not work.

The opinion, plainly stated

The FTC's order should be read as an ending. The overlay's core promise — instant compliance with no real work — has been formally labeled deceptive, and the lawsuit data shows it never protected anyone in the first place. If you are still paying for a widget in the belief that it makes you compliant, the most valuable thing you can do this quarter is cancel that belief, run an honest audit, and fix the real thing. Your disabled customers deserve it, and it is the only path that actually reduces your risk.