Guarding Against the Instant Compliance Pitch
A widget promising full ADA compliance in 48 hours is selling the liability it claims to remove. What overlays cannot fix, what the filing data shows, and what to buy instead.
The pitch arrives by email, usually the week after a competitor announces a settlement: install one line of JavaScript, become ADA compliant in 48 hours, stop worrying. It is a good pitch because the fear is real. It is a bad purchase because the product cannot do the thing the pitch promises, and the gap between the two is where the liability sits.
Accessibility practitioners have said this bluntly for years: an overlay can adjust presentation for some users, and it cannot repair the underlying barriers that lawsuits and audits actually test. This post separates what these tools genuinely do from what they claim, and sets out what a store should spend the same money on instead.
What an overlay can and cannot reach
An overlay script can offer user-triggered adjustments: larger text, higher contrast themes, a reading mask. Some users like those controls. What it cannot do is rewrite your templates. It cannot give a nameless icon button a name in the accessibility tree, untrap a keyboard user inside a chat widget, associate a form error with its field, or add captions to your product video. Those barriers live in your HTML and your third-party components, underneath anything a script paints on top.
WCAG conformance is a property of the page as delivered and operated, tested with assistive technology against the real code. A toolbar that sits beside the page does not change the page's conformance, which is why auditors and plaintiffs' experts test with the overlay ignored or removed.
What the filing data shows
If widgets prevented lawsuits, sued sites would not have them installed. UsableNet's analysis of the 2025 docket found that a substantial share of filings, roughly one in five in the first half of the year by its midyear reporting, targeted websites running an accessibility widget. Some complaints now cite the widget's own interference, including cases where the overlay broke screen reader navigation that previously worked.
There is also a regulatory edge: the FTC has already acted against a prominent overlay vendor over deceptive compliance claims, ordering a $1 million payment in 2025. A store repeating the vendor's promise on its own accessibility statement inherits the accuracy problem.
What to buy with the same budget
The overlay subscription money, redirected, buys the things that actually change conformance: a template-level audit scoped to your top flows, remediation of the header, product, cart, and checkout components, and a monitoring cadence that catches regressions when themes and apps update. None of that arrives in 48 hours. All of it is still true in 49 days, which is more than the pitch can say.
Related reading: Accessible Store Locators and Pickup Selection: Maps Are Not the Only Way In, Testing Accessible Names on Header Icons: Search, Account, and Cart, ADA Risk in Age Gates and Date of Birth Fields.
Frequently asked questions
Can an accessibility overlay make a site WCAG conformant?
No. Conformance is tested against the page's own code and behaviour with assistive technology. Overlays add a parallel toolbar; they do not repair missing names, labels, focus handling, or captions in the underlying templates, so auditors do not credit them as remediation.
Are overlays harmful, or just useless?
They range from neutral to actively harmful. Some users value the display controls. But overlays have been documented interfering with screen readers and keyboard navigation, and complaints in recent filings have cited the widget itself as a barrier. The compliance claim is the harmful part.
Did regulators really act against an overlay vendor?
Yes. The Federal Trade Commission announced in 2025 that a leading overlay company would pay $1 million over allegations its AI widget claims were deceptive, including claims that it could make websites compliant. Vendor marketing is not a compliance defence.
What should our accessibility statement say instead?
Say what you have actually done: the standard you target, the date and scope of your last evaluation, the known limitations, and a working contact route for barriers. A modest accurate statement protects you better than a borrowed promise of instant compliance.