Overlays vs. a real audit — why widgets are legally risky
In short
Overlay widgets promise accessibility via JavaScript but do not establish legal conformance — this is the position of the European Commission and expert bodies. In the US, websites using overlays have increasingly been sued. What is defensible instead is an audit with documented findings, real code fixes and human review.
What an overlay is
An accessibility overlay (also “widget” or “toolbar”) is a piece of JavaScript embedded into a website. At runtime it lays a layer over the page in the browser that is meant to adjust contrast, font sizes or read-aloud functions — sold as “accessibility at the click of a button” on an annual subscription.
Why overlays do not establish conformance
The basic idea is attractive, but the substance does not hold. No automated script can detect or correctly fix all WCAG A/AA criteria — much depends on content and context (does the alt text fit, is the reading order right, is text over an image legible). The European Commission and expert bodies have made clear that overlays do not establish legal conformance. On top of that, an overlay can even conflict with the user's real assistive technology (screen reader, browser settings) and reinforce barriers instead of removing them.
The legal risk
An overlay does not make the underlying barriers documented and demonstrably disappear — at best it superficially covers them. In the US, websites relying on overlays have increasingly been sued for lack of accessibility; there, the widget has in part itself become the target. Numerous accessibility experts have publicly spoken out against overlays. Anyone who relies on an overlay holds no defensible chain of evidence in a dispute.
What works instead
Accessibility becomes defensible not through a runtime layer but through real corrections in the source code — documented and auditable. The difference at a glance:
| Feature | Overlay / widget | Real audit |
|---|---|---|
| Legal conformance | Does not establish conformance | Documented proof to WCAG 2.2 AA & EN 301 549 |
| How it works | Script “repairs” at runtime in the browser | Real findings and code fixes for your team |
| Auditability | Black box, no chain of evidence | Per finding: page, DOM element, criterion, screenshot, confidence |
| Human review | None | Ambiguous cases go to a review queue |
A real audit finds the barriers, proves them and hands your development team concrete fixes — not a script you rent over the top of the problem. What such an audit costs and what drives the price is in “What does an accessibility audit cost?”. Whether your offering is covered at all is clarified in “BFSG: Who is affected?”.
Frequently asked questions
- Are accessibility overlays legal?
- An overlay is not banned per se, but it does not establish legal conformance. The European Commission and expert bodies have made clear that overlays do not meet the requirements — so they do not protect against the obligation or against complaints.
- Do overlays make my website accessible?
- No. A script cannot detect or fix all WCAG criteria and can even conflict with real assistive technology. The actual barriers in the source code remain.
- What is the alternative to an overlay?
- A real audit: documented findings with page, DOM element, violated criterion and screenshot, concrete code fixes for your team, human review of the ambiguous cases and a defensible conformance statement.
Request a free scan
Tell us your domain — we run a free initial scan and show you the most important barriers.