Accessibility widgets — overlays — all work on the same principle: a JavaScript script injected on the browser side, which modifies the DOM on the surface (contrast, font size, text-to-speech). They're sold as instant compliance. In reality, they don't fix the root of the problem — and they add legal risk instead of removing it. A tour of the 4 most common.
AccessiBe
The best known, and the most emblematic. Sanctioned by the US FTC in April 2025 for deceptive advertising ($1M), precisely for selling a "compliance in one click" it didn't produce. The ruling is now cited in European litigation as a reference.
UserWay
A very similar model. Several class actions target it in the United States. An independent audit (Disability Rights Advocates, 2023) concluded that sites equipped with UserWay were no more WCAG-compliant than sites without: the widget doesn't move the needle.
AudioEye
A hybrid approach (automatic script + human review). Marginally better than a pure overlay in practice, but still not compliant in the sense of an RGAA audit, and also targeted by lawsuits. Adding humans doesn't redeem the overlay model.
EqualWeb
One of the most commercially aggressive in Europe, distributed notably via PrestaShop Addons. Same mechanisms, same limits, same risks as the others.
⚠ The risk the widget adds
By installing an overlay, you automatically display a "compliant site" statement in your footer. This statement is false — and legally binding. It exposes you to two cumulative risks: the classic RGAA sanction, AND the sanction for misleading commercial practice (the exact ground of the FTC vs AccessiBe case).
What to do instead
- 01Audit to learn your true level, with no illusion
- 02Fix the non-conformities at the source, in the code and the content
- 03Publish an honest statement (partial, with a plan) rather than a false "compliant"
- 04Set up monitoring to prevent regressions
Frequently asked questions
Does an overlay really help no one?
Some functions (enlarge text, change contrast) already exist natively in browsers and operating systems. Worse: the overlay can conflict with the user's own settings and screen reader, and degrade their experience instead of improving it.
Why are they so popular then?
Because they promise a solution in 5 minutes where real compliance takes work. It's a tempting commercial shortcut — and it's exactly what regulators have started to sanction.
I've already paid for an overlay subscription, what do I do?
At minimum, remove the false compliance statement it displays, run a real audit, and reinvest the budget in substantive fixes. The money spent on the overlay doesn't redeem the risk it creates.
Compare an overlay with a real RGAA audit.
→ See the comparisons