Why accessibility overlays don't work

An accessibility overlay is a script you paste onto your site that promises to make it accessible automatically — a floating button, a menu of contrast and font toggles, a claim of instant compliance. If that sounds too good to be true, it is. We don't sell overlays, we don't install them, and a site relying on one will not pass our assessment. Here's why.

They don't fix the underlying code

Accessibility problems live in a site's HTML: a form field with no label, a button that isn't reachable by keyboard, an image with no text alternative, a heading structure that makes no sense to a screen reader. An overlay sits on top of that code and tries to patch it at runtime with JavaScript. It cannot reliably understand what a control is for, whether alt text is meaningful, or whether a custom widget behaves correctly — because those require human judgment about intent, not a script guessing at the surface.

The people they claim to serve say they don't work

This isn't just our opinion. The Overlay Fact Sheet — signed by hundreds of accessibility advocates, developers, and disability organizations, including the American Foundation for the Blind, the National Federation of the Blind, and the W3C's Web Accessibility Initiative — states plainly that no existing overlay can make a website fully accessible. When the organizations representing the exact users these tools claim to help unanimously say they don't work, that's not a debate. It's a consensus.

They can make things worse

Screen-reader users frequently report that overlays interfere with the assistive technology they already use — overriding their settings, hijacking keyboard commands, or creating new barriers on top of the old ones. Many disabled users have learned to detect an overlay and immediately turn it off, if they can. A tool that people disable on sight is not accessibility.

And they don't hold up legally

Overlays are marketed as a shield against legal risk. In practice they've become a target. Regulators have taken action against overlay vendors for the compliance claims they make, and sites running overlays have been named in accessibility lawsuits in large numbers. Paying a monthly fee for a widget that doesn't fix your site and doesn't protect you is the worst of both worlds.

The honest path is unglamorous: find the real barriers, fix them in the code, and keep a record. That's slower than pasting in a script — which is exactly why it works.

What to do instead

Start by finding out what's actually wrong. An evidence-backed assessment identifies the real barriers on your site and maps each to the standard it fails — the roadmap for fixing them properly. From there you can remediate the underlying code yourself, with your developers, or with a remediation firm. No widget required, and nothing to undo later.