What Is an Accessibility Overlay — And Why It's Not Enough

You've probably seen the ads: "Make your website ADA compliant in 48 hours." "One line of code. Full WCAG compliance." These claims come from companies selling what's called an accessibility overlay — a JavaScript widget that sits on top of your existing website and claims to automatically fix accessibility issues.

It sounds too good to be true. It is.

What is an accessibility overlay?

An accessibility overlay is a third-party JavaScript plugin that adds a toolbar or widget to your website. Common features include buttons to increase text size, change contrast, pause animations, or switch to a "screen reader mode." Well-known overlay vendors include accessiBe, UserWay, AudioEye, and EqualWeb.

They're marketed as a fast, cheap alternative to actual accessibility remediation. Prices range from $49/month to a few hundred dollars per year. The pitch is compelling: add one script tag and your accessibility problems disappear.

Why overlays don't work

The core problem is architectural. Overlays work by intercepting and modifying what's already in your HTML — but they can't fix what isn't there. If an image has no alt text in the underlying code, the overlay has to guess what the image is about. If a form field has no label, the overlay has to infer one. These guesses are frequently wrong.

More critically, overlays interfere with assistive technologies. Screen reader users — the very people overlays claim to help — report that overlay widgets frequently break their existing tools. The overlay tries to intercept keyboard events that NVDA or JAWS already handles, creating conflicts that make the site harder to use, not easier.

Overlays don't provide legal protection

This is the part that matters most if you're concerned about ADA lawsuits. Having an overlay on your site does not protect you from legal action — and courts have ruled accordingly.

Companies using overlays have been successfully sued multiple times. Domino's Pizza, which used an overlay, lost their ADA web accessibility case all the way to the Supreme Court. Gil v. Winn-Dixie established that overlay widgets do not constitute adequate remediation under the ADA.

Plaintiffs' attorneys are now specifically targeting sites that use overlays, arguing that the overlay itself is evidence the company knew about the problem but chose a cheap workaround instead of a real fix.

What actually works

Real accessibility requires fixing the underlying HTML, CSS, and JavaScript — not layering a widget on top of it. The process looks like this:

1. Audit your site — identify every WCAG violation with a combination of automated scanning and manual testing
2. Prioritize fixes — start with critical violations that completely block access, then work through high and medium impact issues
3. Fix the source code — add alt text, proper labels, keyboard navigation, heading structure, and contrast-compliant colors directly in the HTML/CSS
4. Test with real assistive technology — use NVDA, JAWS, or VoiceOver to verify the fixes work as intended
5. Document everything — keep records of your audit findings and remediation work
6. Maintain it — accessibility regressions happen as sites are updated; build testing into your development process

How much does real remediation cost?

For most small to mid-size websites, professional accessibility remediation costs between $500 and $5,000 — a one-time investment rather than an ongoing monthly fee. That's typically cheaper than a year of overlay subscription fees, and it actually works.

Compare that to the cost of an ADA lawsuit settlement ($5,000–$75,000) and the choice is clear.

Start with a free audit

Before spending anything, find out exactly what's broken on your site. WebPossum's free WCAG 2.2 scanner gives you a complete report in seconds — every violation, every affected element, and how to fix it.

If you need help with the actual fixes, contact Raphael at hello@webpossum.com. We do proper remediation — fixing the source code, not adding a widget on top of it.