All articles
WCAGCheck Editorial

40% of Sites Sued for Accessibility Had Overlays Installed: What This Means for Your Compliance Strategy

New data shows 40% of websites sued for accessibility violations already had overlay tools installed. Here's what actually works.

40% of Sites Sued for Accessibility Had Overlays Installed: What This Means for Your Compliance Strategy

The AudioEye 2026 Web Accessibility Litigation Report contains a statistic that should make every developer pause: nearly 40% of organisations sued for web accessibility violations in 2025 already had an overlay tool installed when the lawsuit was filed.

Read that again. These weren't sites that had done nothing about accessibility. They'd paid for a solution. They'd installed the widget. They had the little icon in the corner. And they still got sued.

For anyone who's been sold an overlay as a quick fix for WCAG compliance, this data confirms what accessibility professionals have been saying for years: overlays don't prevent lawsuits because they don't fix the underlying problems.

What Overlays Actually Do (and Don't Do)

Accessibility overlays—sold by companies like accessiBe, UserWay, and AudioEye—typically work by injecting JavaScript that attempts to modify how a page behaves. They might offer features like text resizing, contrast adjustments, or screen reader "optimisation."

Here's the problem: these tools can't fix structural accessibility issues in your code.

Consider WCAG 2.1.1 (Keyboard). If your custom dropdown menu isn't keyboard accessible because it relies entirely on mouse hover events, an overlay can't rewrite your JavaScript to add keyboard handlers. The underlying code is still broken.

Or take WCAG 1.1.1 (Non-text Content). If your product images have no alt text, an overlay might attempt to generate descriptions using AI. But automated image recognition can't understand context. It might describe a photo as "person wearing blue shirt" when what matters is "CEO Sarah Chen announcing the merger." That's not equivalent alternative text.

The technical limitations are fundamental. Overlays sit on top of your site; they can't restructure your HTML, fix your heading hierarchy, repair broken form labels, or make your custom components properly expose their state to assistive technology.

Why Overlays Can Make Things Worse

Beyond failing to fix issues, overlays often create new problems for disabled users.

Screen reader users frequently report that overlays interfere with their existing assistive technology. These users have already configured their systems—their screen reader, their browser settings, their preferences—to work the way they need. An overlay that forces its own "screen reader mode" can override those carefully tuned settings.

The National Federation of the Blind has been vocal about this. Users don't want websites making assumptions about what they need. They want websites that follow standards so their existing tools work correctly.

There's also the performance impact. Loading additional JavaScript affects page speed, which matters for users on slower connections or older devices—groups that often overlap with disabled users.

What the Litigation Data Tells Us

Plaintiff firms aren't checking whether you have an overlay installed before filing suit. They're running automated scans that detect WCAG failures.

These scans catch issues like:

  • Missing alt text on images (WCAG 1.1.1)
  • Insufficient colour contrast (WCAG 1.4.3)
  • Form inputs without associated labels (WCAG 1.3.1)
  • Missing skip navigation links (WCAG 2.4.1)
  • Empty buttons and links (WCAG 2.4.4)

An overlay doesn't make these failures disappear from automated scans. The underlying HTML still has the problems. The lawsuit proceeds.

This is why the 40% figure exists. Organisations thought they'd addressed the risk. They hadn't addressed the actual accessibility failures.

What Actually Works

Fixing accessibility properly means fixing your code. There's no shortcut, but it's also not as overwhelming as it might seem.

Start with automated testing to identify the obvious issues. Tools can catch around 30-40% of WCAG failures—things like missing alt text, contrast problems, and form label issues. These are often the same issues plaintiff firms scan for.

Then prioritise manual testing for the issues automation can't catch. Keyboard navigation, screen reader compatibility, and cognitive accessibility all require human evaluation.

Build accessibility into your development process rather than treating it as an afterthought. Train your team on WCAG requirements. Include accessibility checks in code review. Test with actual assistive technology.

For existing sites, an accessibility audit gives you a clear list of what needs fixing. Work through it systematically, starting with the most severe issues and the highest-traffic pages.

The Business Reality

Overlays are attractive because they promise a quick solution. Install a script, pay a monthly fee, done. The reality is that you're paying for something that doesn't deliver compliance and doesn't prevent legal action.

The money spent on overlay subscriptions would be better spent on actual remediation. Fix the problems once, properly, and you've addressed both the legal risk and—more importantly—made your site actually usable for disabled visitors.

That 40% statistic isn't just a number. It represents organisations that thought they'd solved the problem and found out the hard way that they hadn't.

WCAGCheck scans your website for WCAG compliance issues and tells you exactly what to fix. Try it free at wcagcheck.co.uk