Skip to main content

Why Accessibility Overlays Don't Protect You From ADA Lawsuits

22.6% of websites sued for ADA violations had an overlay installed. The FTC fined accessiBe $1 million. Here is why overlays fail and what to do instead.

Accessibility overlay products are a multi-million dollar industry built on a promise they cannot keep: install one line of JavaScript and your website becomes ADA compliant. The data shows this is not true, and regulators are starting to act.

What Overlays Claim to Do

Overlay products (accessiBe, UserWay, AudioEye, EqualWeb, and others) typically:

  • Add a toolbar widget to your site with options like "increase font size" or "high contrast mode"
  • Claim to use AI to automatically detect and remediate accessibility issues
  • Promise WCAG 2.1/2.2 AA compliance
  • Market themselves as lawsuit protection

The appeal is obvious: one line of code, no developer work, instant compliance. Unfortunately, it does not work that way.

The Evidence Against Overlays

The FTC's $1 Million Fine

In January 2025, the Federal Trade Commission fined accessiBe $1 million for deceptive marketing practices. According to the FTC's announcement, accessiBe made claims about its product's ability to make websites WCAG compliant and protect against ADA lawsuits that were not supported by evidence.

This is the first major regulatory action against an overlay company, but it may not be the last.

22.6% of Sued Sites Had Overlays

EcomBack's H1 2025 digital accessibility lawsuit report found that 22.6% of websites that received ADA lawsuits had an accessibility overlay widget installed at the time they were sued.

Having an overlay did not prevent the lawsuit. In some cases, plaintiffs' attorneys specifically cite the presence of an overlay as evidence that the site owner knew about accessibility issues but chose a superficial fix rather than actual remediation.

Disability Advocacy Organizations Oppose Overlays

The National Federation of the Blind, the largest organization of blind people in the United States, has publicly criticized overlay products. The Overlay Fact Sheet, signed by hundreds of accessibility professionals and disability advocates, states that overlays "do not provide adequate accessibility."

Their concerns are based on direct experience: blind users and other people who rely on assistive technology frequently find that overlays interfere with their existing tools rather than helping.

Why Overlays Fail Technically

They Cannot Fix Structural HTML Issues

If an image is missing alt text in your HTML, an overlay can try to guess what the image shows using computer vision. But automated image recognition frequently produces inaccurate or meaningless descriptions. A product photo described as "image of a rectangular object" is not meaningful alt text.

The same applies to unlabeled form fields, broken heading structures, and missing landmark regions. These are structural code issues that require actual code changes.

They Conflict with Assistive Technology

Screen reader users already have their own settings for font size, contrast, and reading preferences. Overlays that modify the page DOM often conflict with these existing tools, creating new barriers rather than removing old ones.

They Cannot Fix Keyboard Navigation

If a custom dropdown menu or modal dialog is not keyboard accessible, no overlay can make it keyboard accessible without rewriting the component. Overlay scripts cannot reliably modify the tab order and keyboard event handling of every possible custom widget.

They Add Performance and Privacy Concerns

Overlays load additional JavaScript that can slow your page. They also often track user interactions and preferences, raising privacy questions, particularly under GDPR and similar regulations.

What Actually Works

Fix Your Code

There is no shortcut. Accessibility compliance requires fixing your actual HTML, CSS, and JavaScript:

  1. Scan your site to identify current violations. OnePageAudit provides a free scan with specific fix instructions for each issue.
  2. Add real alt text to images. Write descriptions that convey the same information a sighted user gets.
  3. Label all form fields with proper elements.
  4. Fix heading structure to follow a logical hierarchy.
  5. Ensure keyboard navigation works for all interactive elements.
  6. Meet color contrast requirements (4.5:1 for normal text, 3:1 for large text).

Document Your Compliance Efforts

Maintain records of audits, remediation work, and ongoing monitoring. This demonstrates good faith to courts if a lawsuit does arise.

Monitor Continuously

New content, plugin updates, and design changes can reintroduce accessibility issues. Regular automated scanning catches regressions early.

The Bottom Line

Overlays are not compliance. They are a liability. The FTC has fined the largest overlay company. Nearly a quarter of sued websites had overlays installed. Disability advocacy organizations oppose them.

The only path to real accessibility compliance is fixing your actual website. Start with a scan, fix the issues found, and monitor going forward.

Scan your website for free with OnePageAudit Related reading:

Frequently Asked Questions

What is an accessibility overlay?
An accessibility overlay is a JavaScript widget you add to your website that claims to automatically detect and fix accessibility issues. Products like accessiBe, UserWay, AudioEye, and EqualWeb typically add a toolbar icon that lets users adjust font sizes, contrast, and other display settings. The core claim is that the overlay makes your site ADA/WCAG compliant without changing your underlying code.
Why did the FTC fine accessiBe?
In January 2025, the FTC fined accessiBe $1 million for deceptive marketing practices. The FTC found that accessiBe made misleading claims about its product's ability to make websites compliant with WCAG standards and protect against ADA lawsuits. The FTC determined these claims were not supported by evidence.
What should I use instead of an overlay?
Fix your actual website code. Run an automated scan (like OnePageAudit) to identify specific violations, then fix them in your HTML, CSS, and JavaScript. Add real alt text, proper form labels, correct heading structure, sufficient contrast, and keyboard navigation. This is the only approach that actually works for both compliance and real user accessibility.

Scan your website free

Find ADA compliance issues in under 60 seconds. No account required.

Run Free Scan