← Back to guides

Why Accessibility Overlays Dont Work

Accessibility overlay widgets promise a tempting shortcut: add one line of JavaScript to your site and become ADA compliant overnight. Companies like accessiBe, UserWay, and AudioEye have built entire businesses on this premise. The problem is that it does not work, and the evidence against overlays has become overwhelming. As we detail in our post on the real cost of ADA lawsuits, overlay usage has not been accepted as a legal defense.

What Overlays Actually Do

Overlay widgets inject a JavaScript layer on top of your existing website. They typically add a toolbar icon that lets users adjust font sizes, contrast, cursor size, and other visual settings. Some claim to use AI to automatically fix accessibility issues like missing alt text and form labels.

On the surface, this sounds reasonable. In practice, overlays create more problems than they solve.

The Technical Problems

They cannot fix structural HTML issues. If your site uses <div> elements instead of semantic <button> or <nav> elements, an overlay cannot fix that. Screen readers rely on the DOM structure, not a JavaScript layer on top.

AI-generated alt text is unreliable. Overlays that claim to auto-generate image descriptions produce generic, often inaccurate results. A product photo might get described as "image of a rectangular object" instead of "Blue wireless headphones, model XR-500." Bad alt text can be worse than no alt text.

They conflict with assistive technology. Screen reader users often report that overlay widgets interfere with their existing tools. The National Federation of the Blind published a position statement specifically calling out accessiBe for making websites harder to use, not easier.

They add performance overhead. A typical overlay widget adds 200-500KB of JavaScript that loads on every page. This slows your site down for all users.

The Legal Reality

Courts have consistently ruled that overlay widgets do not constitute ADA compliance:

  • The FTC fined accessiBe over $1 million in 2025 for deceptive marketing claims about their product's compliance capabilities.
  • Multiple federal lawsuits have been filed against websites that used overlay widgets, with courts finding the overlays did not address the underlying accessibility barriers.
  • The DOJ's 2024 rulemaking on web accessibility standards did not recognize overlay solutions as a path to compliance.

Using an overlay actually increases your legal risk because it shows awareness of accessibility requirements without actually addressing them.

What Actually Works

Real accessibility compliance requires fixing the underlying code:

  • Automated scanning identifies machine-detectable violations across your entire site -- missing alt text, contrast failures, broken ARIA, keyboard traps.
  • Developer remediation fixes each violation at the source: proper HTML semantics, color updates, label associations, keyboard handlers.
  • Manual testing covers the 60-70% of WCAG criteria that automated tools cannot check -- content quality, logical flow, assistive technology compatibility.
  • Ongoing monitoring catches regressions as your site changes. New content and code updates can reintroduce violations.

The Cost Comparison

Overlay vendors charge $500 to $2,000+ per year for a product that does not work. Proactive compliance through scanning and remediation costs a similar amount but actually fixes the problems. Litmus starts at $49/month for automated WCAG 2.1 AA scanning with prioritized violations and actionable fix guidance -- a fraction of what a single demand letter settlement costs.

There are no shortcuts to web accessibility. Skip the overlays and invest in real fixes.

Find accessibility issues before they find you

Litmus scans your entire website against WCAG 2.1 AA using axe-core. Get prioritized violations, element-level detail, and actionable fix guidance. Start your free 14-day trial — no credit card required.

Start Your Free Trial