Overlay Widgets Won't Make You Compliant

You've seen the pitch. Paste in one line of code, a little accessibility icon appears in the corner of your site, and supposedly you're compliant overnight. No audit, no rebuild, just a monthly fee. It sounds too good to be true because it is. Accessibility overlays are one of the few topics where we'll be blunt rather than balanced, because the evidence is one sided.

What overlays actually are

An overlay is a script that loads on top of your existing site and tries to patch accessibility problems automatically, guessing at alt text, adjusting contrast on the fly, and offering a menu of accessibility profiles. The key word is guessing. It's software trying to infer meaning your code never gave it, in real time, in the browser.

Why they don't deliver compliance

• Automation only reaches so far. Automated tools reliably catch somewhere around a quarter to a third of the accessibility problems on a page, and their rules touch only a minority of the success criteria. Whether an alt text is meaningful, whether a form's error handling makes sense, whether the reading order is logical, those need a person to judge. An overlay can't supply that.
• They patch symptoms, not causes. The broken markup is still broken underneath. The overlay just drapes a layer over it. Turn the overlay off and every problem is still there.
• Selling instant compliance is itself risky. If you file or imply a compliance claim resting on an overlay, and the site still fails for real users, you've documented a claim you can't back up.

Why they can make things worse

This is the part that surprises people. Many overlays actively interfere with the assistive technology users already have and trust. They can fight with a person's own screen reader, hijack keyboard behaviour, or announce controls that don't work as promised. The result is that some blind and low vision users report overlays making sites harder to use, not easier. There is a public statement called the Overlay Fact Sheet, signed by hundreds of accessibility professionals and disabled users, asking businesses not to use these products. When the people a product claims to help are its loudest critics, that tells you something.

There's a legal wrinkle too. In the US, having an overlay installed has not reliably prevented accessibility lawsuits. In some cases sites running overlays have been sued anyway. The overlay didn't buy the protection it promised.

The same trick, one lane over

Once you know the shape of this, you start seeing it in the other half of compliance work. On the privacy side the equivalent is the consent widget: it gets installed, it shows a banner, it records which button was clicked, and it never actually stops a single tracking tag from firing. Same promise, same bolt on, same gap between the badge in the corner and what is happening underneath. A widget can be the interface for a fix. It cannot be the fix.

What actually works instead

There's no shortcut, but the real path isn't mysterious. Audit the site against WCAGWeb Content Accessibility Guidelines, the technical standard the AODA points at, fix the underlying code, and build accessibly going forward. It's more work than pasting a script, and it costs more up front. It's also the only approach that actually makes your site usable and genuinely reduces your risk, because it changes what's really there instead of hiding it.

If you're already paying for an overlay, we're not here to shame you. The marketing is genuinely convincing. But we'd rather show you what an actual audit finds underneath it, so you can decide where that monthly fee is really going. We're not lawyers and this isn't legal advice about your own position. It's what we find on real sites and what the standard actually asks for.