Are accessibility overlays a legal trap? What the FTC, the courts and 800+ experts say

What is an accessibility overlay?

An accessibility overlay is a piece of JavaScript — a widget, plugin or toolbar — that loads on your website and tries to patch accessibility issues at render time, usually adding a floating icon (often a wheelchair symbol) that lets visitors adjust contrast, text size and spacing (Compliapoint, 2026). Some products claim to use AI to detect and repair WCAG violations automatically. The defining characteristic is what they do not do: an overlay modifies how your page appears without changing the source code underneath it.

The category is large and commercial. The most common products are accessiBe, UserWay, AudioEye and EqualWeb, typically sold as recurring subscriptions running from about $490 to $3,990 a year, and the Overlay Fact Sheet lists more than 30 companies selling such tools, many of them white-labeled so a buyer may not know whose code is actually running (a11y Collective, 2026). The pitch is consistent across vendors — paste in one line of code and become compliant — and it is precisely that promise the FTC went after.

How can you tell if a site is already using one?

Two quick checks. Visually, look for a small floating button — often a circle with a wheelchair or person icon — usually in a bottom corner, that opens a menu of contrast, font-size and spacing toggles. Technically, view the page source or the network requests and search for the vendor’s script: filenames like acsb.js for accessiBe, userway.js for UserWay, or an AudioEye domain are exactly the signatures the plaintiff scanners look for. If you find one on your own site, the prudent move is not to rip it out in a panic but to start a genuine source-level audit, because the accessibility gaps the widget was masking are still there — and now you know to fix them properly.

What did the FTC actually find?

It found the promise was false, and it put a number on it. In a 2025 order, the Federal Trade Commission fined accessiBe $1 million for deceptive advertising (Hudson Cook, 2026). The specific claim it sanctioned was striking in its confidence: accessiBe had marketed its accessWidget as making a site compliant with 30% of WCAG immediately and fully compliant with the remaining 70% within 48 hours, with a re-scan every 24 hours to maintain it (Hudson Cook, 2026). The FTC found those claims false, misleading or unsubstantiated, and noted the widget failed to make basic components — menus, headings, tables, images, recordings — accessible.

There was a second deception the order addressed: accessiBe had presented paid endorsements as if they were independent reviews, without disclosing the connection (Brickfield, 2026). The consent order now bars accessiBe from claiming its products can make any website WCAG-compliant or ensure continued compliance over time. This was the first federal enforcement action against an overlay vendor, and it dismantled the marketing narrative the whole industry had relied on (Kha Creation, 2026).

Why can’t an overlay make a site compliant?

Because most of accessibility lives in the source code an overlay never touches, and automation has a hard ceiling. No automated tool — even with current AI — can detect, let alone repair, more than roughly 30 to 40% of WCAG criteria (Accessibility.Works, 2026). WCAG 2.1 has 78 success criteria, and many of them require structural decisions a script cannot make: whether an image is decorative or informational, whether a custom checkout flow is operable by keyboard, whether alt text is meaningful (Kha Creation, 2026).

There is also a whole category of content overlays simply ignore. They do nothing for the accessibility of PDFs, presentations, audio and video files — and the FTC noted that one major vendor’s terms of service did not adequately disclose that those formats would not be made accessible without buying additional services (Brickfield, 2026). A widget that paints over the surface of your home page changes nothing about the inaccessible document a customer actually needs to read.

Why does having an overlay make a lawsuit more likely?

Because to a plaintiff’s attorney, the widget is a flag, not a shield — and the data shows it. In the first half of 2025, about 22.6% of ADA web-accessibility lawsuits targeted sites that already had an overlay installed, with nearly 500 such filings; given that overlays run on only a minority of all websites, that is a massive over-representation (Compliapoint, 2026; Charles Jones, 2026). In 2024, more than 1,000 companies running accessibility widgets were sued (a11y Collective, 2026).

The mechanism is specific. Plaintiff firms run automated scanners that look for code signatures like userway.js or acsb.js, which are trivially easy to detect, and the presence of an overlay signals two useful things: a company with a budget that is aware of accessibility, and a site whose underlying code is probably full of violations the widget is masking (Kha Creation, 2026). Worse, installing the widget documents that you knew accessibility was required and chose a surface fix — which a court reads as choosing the cheapest option you knew did not work, the opposite of a good-faith effort (a11y Collective, 2026).

What have the courts said?

They have rejected the overlay defense repeatedly, and in plain language. In LightHouse v. ADP, the settlement stated that overlay solutions such as those from AudioEye and accessiBe would not suffice to achieve accessibility — a striking line because it named vendors directly (Kha Creation, 2026). In Murphy v. Eyebobs, a blind plaintiff sued a retailer using the accessiBe widget, the court declined to dismiss the case on the strength of the overlay, and the settlement required Eyebobs to remove it and perform genuine manual remediation to WCAG 2.1 AA, hire an accessibility coordinator and run user testing (Kha Creation, 2026).

The vendor promises have fared just as badly. In a 2024 class action, the flower-delivery company Bloomsybox sued UserWay after being hit with an accessibility suit six months after installing the widget it had bought partly on the strength of a marketed million-dollar litigation warranty; when Bloomsybox sought that protection, it was reportedly told its monthly plan did not qualify, was handed a generic guide, and was left to settle on its own after $4,000 in fees (AccessiTree, 2026). The court allowed the deceptive-marketing case against UserWay to proceed.

Do overlays actually help disabled users?

Frequently they make the experience worse, which is the part the marketing never mentions. Overlays often interfere with the assistive technology people already rely on — JAWS, NVDA, VoiceOver — by changing keyboard shortcuts and mishandling the accessibility tree, sometimes ignoring aria-hidden so a screen reader announces things it should skip (DEV Community, 2026). The response from disabled users is telling: many have installed browser extensions specifically to block overlays, one community member bluntly called them malware, and the National Federation of the Blind returned an accessiBe sponsorship and passed a resolution against the product (AccessiTree, 2026; a11y Collective, 2026).

The professional consensus is documented and large. The Overlay Fact Sheet, a public statement signed by more than 800 accessibility professionals — including the chair of the W3C ARIA Authoring Practices Task Force, contributors to the NVDA screen reader, and accessibility leads from companies like Microsoft, Google and Amazon — states that no overlay can make a website fully compliant with any standard and therefore cannot eliminate legal risk (a11y Collective, 2026). There is a privacy dimension too: overlays that detect assistive-technology use without consent are handling sensitive data about disability status, which raises its own compliance questions under regimes like the GDPR (Brickfield, 2026).

What does the EU’s accessibility law say about overlays?

The same verdict, from the other side of the Atlantic. The European Accessibility Act came into force on 28 June 2025, requiring private digital services across the EU to meet EN 301 549, which incorporates WCAG 2.1 AA, with penalties reaching up to €3 million in some member states and, in Ireland’s implementation, the possibility of imprisonment (Brickfield, 2026). An overlay does not satisfy it, and European bodies have said so directly: a joint statement from the European Disability Forum and the International Association of Accessibility Professionals concluded that overlays do not deliver compliance (Accessibility.Works, 2026).

For a business serving both the US and the EU, this closes the last hiding place for the shortcut. A widget that fails the ADA in American courts also fails the EAA in European ones, and the privacy concern is sharper under European law: an overlay that detects a visitor’s assistive technology is processing data about their disability, a special category under the GDPR that demands a lawful basis the widget rarely establishes. Wherever your customers are, the overlay is the same liability in a different jurisdiction — and source-level remediation is the answer in all of them.

What actually works instead?

Source-level remediation — fixing the real HTML so the site is accessible by construction rather than disguised at render time. That means a manual audit against WCAG 2.1 or 2.2 AA, ideally including testing by people who actually use assistive technology, and then correcting the code: using the right element for the job, so a navigation menu is a <nav>, a heading is an <h1> rather than a styled <div>, and a button is a real <button> rather than a clickable div (Charles Jones, 2026). The most cost-effective version is to shift left — build accessibility into design and development so issues never reach production in the first place.

The legal calculus favors this too. Unlike an overlay, source remediation can address 100% of WCAG success criteria, and a dated audit report plus a VPAT give you documented, good-faith evidence — the strongest possible position in a dispute or a procurement review (Compliapoint, 2026). This is the same conclusion our pillar guide on whether web accessibility is the law reaches from the regulatory side: accessibility is built, not bought, because the built version is the only one that is real.

Why we don’t sell overlays

Because we cannot recommend a product the FTC has sanctioned and the courts reject, and we are not in the business of selling one. We resell no overlay and no compliance widget, which is exactly why this assessment costs us nothing to give straight: if a vendor’s central promise is one-click or 48-hour compliance, treat that as the warning sign, not the feature. The honest version of accessibility is slower, lives in your real code, and produces a site that works for a screen-reader user whether or not anyone is checking.

That is the whole point of building accessibility in rather than bolting it on. For the full picture — which laws apply, how lawsuits actually work, and why the durable answer is construction rather than a widget — this guide sits under our pillar on whether web accessibility is the law.