Why an Overlay Widget Doesn't Protect You (and What Does)

Q: What does an overlay widget actually do?

An overlay widget is a piece of JavaScript that, client-side — only in your visitor's browser — lays a layer over your site. It tries to reinterpret and adjust the HTML at load time (often via a Shadow DOM), but it doesn't change the underlying source code on your server. That keeps it a cosmetic intervention, not a real repair.

Q: So what *does* work against inaccessibility?

You fix accessibility at the source: 1. Test your site against WCAG 2.1 AA and see exactly what's wrong. 2. Repair the real code — often theme-wide, so one fix immediately covers many pages. 3. Keep testing, because your site changes and new errors keep creeping in. That's more than a button, but it's the only thing that holds up in an audit — and it also gets you real, usable improvements instead of a layer on top. Whether or not you fall under the European Accessibility Act, or simply don't want to lose customers: tackling it at the source is ultimately less work and the only thing that's durable.

June 4, 2026

Short answer. An overlay widget lays a layer of JavaScript over your site and promises to make it "100% accessible" with one line of code. In reality it doesn't repair your underlying code, can add new barriers, and doesn't protect you against claims — the American regulator FTC fined a major overlay provider $1 million in 2025 for misleading compliance claims. What does work: fixing the errors at the source, in your own code.

An overlay widget is a piece of JavaScript that, client-side — only in your visitor's browser — lays a layer over your site. It tries to reinterpret and adjust the HTML at load time (often via a Shadow DOM), but it doesn't change the underlying source code on your server. That keeps it a cosmetic intervention, not a real repair.

Does an overlay repair the real errors?

No. Because the code itself doesn't change, the real errors remain. An inaccessible checkout form stays inaccessible; the widget at most pastes something over it. And as soon as you adjust your theme or an app, the "repair" can break again.

Can an overlay add new barriers?

Yes, regularly. Overlays automatically intervene in your page and sometimes introduce new problems in the process — think of focus jumping around, duplicate announcements for screen readers, or buttons that suddenly stop working. Many experts by experience and screen reader users therefore prefer to switch overlays off: the tool meant to help them gets in their way.

Does an overlay slow your site down?

Yes. An overlay loads extra JavaScript on every page view that searches and adjusts the DOM. That costs load time and hits your Core Web Vitals — in particular INP (Interaction to Next Paint), which Google weighs in your ranking. Ironic: the tool meant to improve your accessibility actually makes your site slower — including for the users with disabilities who benefit most from a fast page. So you pay for it twice: in user experience and in SEO.

Does an overlay protect you against fines and claims?

This is the most important question, and the answer is no. An overlay doesn't make you demonstrably compliant and doesn't shield you from enforcement or claims. In fact: the American regulator FTC fined a well-known overlay provider $1 million in 2025 for misleading compliance claims — the promise itself turned out to be the problem. And for good reason: there are now thousands of accessibility lawsuits, hundreds of them against sites that were precisely using an overlay. The widget didn't protect them.

Overlay versus a real code fix

Aspect	Overlay widget	Fix in your own code
Repairs the source code	no, client-side only	yes, structurally
Protects against claims	no	yes — the only thing that holds up in an audit
Speed & SEO	slows down, harms Core Web Vitals	faster, better SEO
Durable when the theme changes	often breaks	stays in place

So what does work against inaccessibility?

You fix accessibility at the source:

Test your site against WCAG 2.1 AA and see exactly what's wrong.
Repair the real code — often theme-wide, so one fix immediately covers many pages.
Keep testing, because your site changes and new errors keep creeping in.

That's more than a button, but it's the only thing that holds up in an audit — and it also gets you real, usable improvements instead of a layer on top. Whether or not you fall under the European Accessibility Act, or simply don't want to lose customers: tackling it at the source is ultimately less work and the only thing that's durable.

Start with measuring

Want to know what's going on under the hood of your site? Scan one page for free. You won't get a made-up "100% fixed", but a clear picture: what a machine definitely detects, what requires human review, and how to fix it — in under 60 seconds, no account.