Do Accessibility Overlays Work? The Evidence in 2026

Accessibility overlays are JavaScript widgets that promise to make your website ADA and WCAG compliant by injecting automated fixes at page load — without touching your underlying code. Products like accessiBe, UserWay, AudioEye, and EqualWeb have marketed themselves as the fast, affordable solution to ADA liability. The reality, documented by disability researchers, advocacy organizations, and the FTC, is significantly more complicated.

What Accessibility Overlays Are (and Claim to Do)

An accessibility overlay is a third-party JavaScript snippet you embed on your website. At load time, the script scans your page and attempts to automatically fix accessibility violations — adding alt text to images, labeling form fields, adjusting color contrast, and remediating ARIA attributes. Most also display a "widget" (usually a floating accessibility icon) that allows users to toggle settings like increased text size, high contrast mode, or reduced motion.

Vendors market these tools with strong compliance language. Historic accessiBe marketing claimed sites would be "fully compliant with the ADA, WCAG 2.1, and other international regulations" within 48 hours. UserWay has made similar claims about instant WCAG compliance. These assertions are central to how overlays are sold — and central to why they have attracted regulatory and legal scrutiny.

What the Evidence Actually Shows

Peer-Reviewed Research

Studies by accessibility researchers — including work published by WebAIM, the Accessible Technology Initiative, and Deque Systems — consistently find that automated tools (including overlays) can identify and remediate roughly 30–40% of WCAG 2.1 AA violations. The remaining 60–70% require human evaluation: keyboard navigation flows, screen reader interaction patterns, cognitive task completion, and dynamic content behavior that no JavaScript can evaluate at runtime.

Overlays typically score even below that ceiling. Unlike developer tools like axe DevTools that evaluate code at build time, overlays must guess at context that isn't deterministic — an image's alt text, a form's purpose, the logical heading structure of a page they didn't build. Incorrect auto-generated alt text is often worse than no alt text, because screen reader users receive misleading descriptions.

The Overlay Fact Sheet

In 2021, over 400 accessibility professionals — including disabled users, screen reader specialists, WCAG authors, and assistive technology developers — signed the Overlay Fact Sheet, a public statement documenting that overlays do not provide the accessibility compliance they claim. The statement has since grown to over 800 signatories.

Key documented findings from the Overlay Fact Sheet and subsequent research:

• Overlays cannot fix inaccessible content — they can only attempt to annotate it
• AI-generated alt text frequently misidentifies image content, producing worse outcomes than missing alt text
• Overlay widget JavaScript often conflicts with JAWS, NVDA, and VoiceOver, breaking navigation that previously functioned
• Many overlays inject visual elements that are themselves inaccessible or keyboard-trappable
• Overlays cannot remediate issues in PDFs, embedded videos, or third-party iframes
• Custom settings toggled by the widget are typically not persistent between sessions or devices

The FTC Action Against accessiBe

The FTC action was significant not just for accessiBe specifically but for the entire overlay industry. It established that marketing an accessibility widget as a compliance guarantee constitutes deceptive trade practice. Other overlay vendors have since modified their marketing language, but the fundamental product limitations remain unchanged.

Businesses Sued While Running Overlays

One of the clearest data points against overlay effectiveness: documented cases of businesses sued for ADA website violations while actively running overlay products.

Accessibility researchers and plaintiff attorneys have documented multiple cases where sites running accessiBe, UserWay, or similar products were still named in ADA demand letters or federal complaints. The pattern is consistent: plaintiff attorneys use disabled users with assistive technologies to manually test sites, not automated scanners. Their testing identifies keyboard navigation failures, screen reader incompatibilities, and modal/popup traps that overlays do not fix — and sometimes make worse.

When Overlays Make Things Worse

For some users with disabilities, accessibility overlays actively degrade their experience — making a previously navigable site harder to use:

What Overlay Vendors Say in Their Defense

Overlay vendors have pushed back on these characterizations, making several counterarguments worth examining honestly:

What to Do Instead of an Overlay

The alternative to an overlay is fixing the actual underlying HTML, CSS, and JavaScript. This is harder and costs more than a $50/month widget subscription — but it produces genuine compliance rather than the appearance of it.

The Bottom Line

The accessibility overlay industry built a market by selling a shortcut to a real problem. The shortcut doesn't work as advertised. The FTC confirmed it. Ongoing ADA litigation confirms it. Disability advocates who test these products confirm it.

This doesn't mean every overlay product is equivalent. AudioEye's hybrid model with manual remediation is substantively different from a passive AI widget. Some overlays catch real violations that genuinely help some users. But no current overlay product delivers full WCAG 2.1 AA compliance, and no overlay eliminates ADA lawsuit risk.

If you've been paying for an accessibility overlay as your primary compliance strategy, the practical advice is: don't cancel it tomorrow out of panic, but don't rely on it as your only defense. Use the time to run a real audit, understand your actual violations, and build a remediation roadmap that fixes your underlying code. That's the only path to genuine compliance.

Frequently Asked Questions