If you run an e-commerce store, you’ve probably been pitched an accessibility overlay: a small JavaScript snippet you add to your site that promises to detect and automatically fix accessibility issues, often with language like “instant ADA compliance” or “WCAG compliant in 48 hours.” It’s an appealing pitch — no developer time, no audit, one line of code. The question worth asking before you install one is simple: does it actually work?
Quick answer: The available evidence says no, not reliably. A 2021 survey of accessibility practitioners found the large majority rate overlays as ineffective, disabled users rate them worse than non-disabled practitioners do, a federal enforcement action in 2025 found one major overlay vendor’s compliance claims were false, and 2025 litigation data shows overlays are not associated with fewer accessibility lawsuits. Overlays can improve some surface-level presentation issues, but they don’t reliably fix the code-level barriers that block people using screen readers, keyboard navigation, or other assistive technology — and installing one is not the same thing as making your site accessible.
This article discusses a federal regulatory enforcement action and general litigation trends. It is educational content, not legal advice. Whether a specific tool or practice creates legal risk for your business is a legal determination — consult qualified counsel for guidance specific to your situation.
What an accessibility overlay actually is
An accessibility overlay (also marketed as a widget or plugin) is third-party JavaScript, usually added with a single <script> tag, that runs in the visitor’s browser and attempts to modify a page’s presentation on the fly — adjusting contrast, resizing text, adding keyboard-navigation menus, or using automated pattern-matching to guess at things like image alt text. It’s a runtime patch layered on top of your existing site, not a change to your site’s underlying HTML, CSS, or JavaScript. That distinction matters for everything that follows: an overlay can change how a page looks to a sighted user adjusting its settings, but it generally cannot rewrite improperly structured code, fix a broken form-label association, or repair a keyboard trap inside a checkout modal — because it doesn’t have access to (and isn’t reprogramming) the code that created those problems in the first place.
What accessibility practitioners and disabled users say
The most substantial independent data on overlay effectiveness comes from WebAIM, the accessibility research group at Utah State University, in its third Survey of Web Accessibility Practitioners, published March 24, 2021, based on 758 valid responses (the third in a series that also ran in 2014 and 2018). The survey asked respondents to rate the effectiveness of accessibility overlays, plugins, and widgets directly. The results: 67% of all respondents rated them “not at all effective” or “not very effective.” Among respondents who identified as having a disability themselves — the people these tools are actually meant to serve — that number rose to 72%, and only 2.4% rated overlays “very effective.”
That pattern — the people overlays are supposed to help rating them worse than practitioners overall — shows up again in the Overlay Fact Sheet, a public statement signed by more than 1,000 accessibility professionals, software engineers (including people from major tech companies), and disabled users. Its core conclusion, in the document’s own words: “full compliance cannot be achieved with an overlay.” The signatories’ underlying argument is straightforward — assistive technology users who need screen readers, alternative input devices, or browser accessibility settings typically already have those tools, built into their operating system or browser. An overlay doesn’t add a capability they’re missing; at best it duplicates what they already have, and at worst it conflicts with it or gets in the way.
A 2025 federal enforcement action
Independent survey data is one thing; a federal enforcement action against a specific vendor’s claims is another kind of evidence entirely. On January 3, 2025, the Federal Trade Commission announced a proposed settlement — finalized April 21, 2025 — requiring accessiBe Inc., one of the best-known overlay vendors, to pay $1 million over deceptive marketing of its “accessWidget” product. According to the FTC’s complaint (as reported by Natural Law Review, the ADA Title III blog published by Seyfarth Shaw, and legal-industry coverage from the Law Office of Lainey Feingold), accessiBe had marketed accessWidget as making a site “compliant with 30% of WCAG’s requirements immediately” and initiating an AI process that would make it “fully compliant with the remaining 70% of WCAG requirements within 48 hours.” The FTC alleged this wasn’t true — that the product routinely failed to make basic components like menus, headings, tables, images, and video recordings accessible, and that some of accessiBe’s supposedly independent third-party endorsements were undisclosed paid placements.
The resulting order permanently bars accessiBe from claiming its automated products can make a website fully WCAG-compliant, or can guarantee ongoing compliance over time, unless it can actually substantiate that claim. It’s the clearest regulatory signal to date that “install this widget for instant compliance” is not a claim regulators consider supportable — at least not for the product examined in that case.
Overlays and lawsuit risk
If the pitch for an overlay isn’t really about accessibility outcomes but about reducing legal exposure, the litigation data doesn’t support that either. UsableNet’s 2025 Midyear Digital Accessibility Lawsuit Report tracked ADA digital accessibility lawsuits filed in the first half of 2025 and found that cases explicitly mentioning an accessibility widget were filed every single month of that period — 85 in January, climbing to 132 in February and March, and totaling roughly 672 across the six months. The report’s own conclusion is direct: these tools “continue to offer no legal protection to the companies that use them.” Overlays typically don’t touch the underlying code plaintiffs’ testers actually encounter with a screen reader or keyboard, so a site can have an overlay installed and still present the same barriers a lawsuit is built around.
What the evidence adds up to
None of this means every automated accessibility tool is worthless — automated scanners are genuinely useful for quickly flagging certain issues, like missing alt text or failing color contrast, across a large site. The distinction is between detection and remediation. An overlay claiming to fix accessibility automatically, without a human reviewing and correcting the underlying code, is the specific claim the evidence above doesn’t support. Real remediation — fixing the actual HTML, form labels, focus order, and keyboard behavior — still requires someone to identify the problem accurately (ideally with both automated scanning and manual testing, since automated tools alone reliably miss things like keyboard traps and focus order) and then correct the code itself.
For a small e-commerce business weighing the decision, the evidence suggests treating an overlay’s compliance claims skeptically, budgeting for actual code-level fixes rather than a monthly widget subscription, and — if legal risk under the ADA is the real underlying concern — reading up on what actually drives that risk rather than assuming a quick install resolves it.
FAQ
Do accessibility overlays make a website ADA compliant? There’s no official legal certification for “ADA compliant” in the first place, and the available evidence — practitioner and disabled-user surveys, a 2025 FTC enforcement action against a major overlay vendor’s compliance claims, and lawsuit data showing overlay-installed sites are still sued regularly — doesn’t support the claim that installing an overlay alone achieves compliance with WCAG or reduces ADA legal risk.
Are all accessibility overlays the same? Products vary in what they attempt to do, but the core limitation is structural: an overlay runs on top of existing code without rewriting it, so it faces the same basic constraint regardless of vendor — it can’t reliably repair problems that live in the underlying markup, such as a missing form label or a keyboard trap in a modal.
Should I remove an overlay if I already have one installed? That depends on your specific site and goals, which is outside the scope of general information like this. What the evidence above supports is not treating an installed overlay as a substitute for a real accessibility review of your site’s actual code.
This article discusses a federal regulatory enforcement action and general accessibility and litigation research. It is educational content, not legal advice. Compliance with the ADA, WCAG, or any other accessibility law or standard is a legal determination; consult qualified counsel for guidance specific to your business.