Why Accessibility Overlays Don't Comply with the EAA (And Can Get You Sued)

If you've looked into accessibility compliance, you've seen the ads: "Make your website ADA and EAA compliant in one line of code." It's a lie. Here's what the evidence shows.

What Overlays Are

An accessibility overlay is a JavaScript widget you add to your website. It typically shows a floating toolbar with options like "high contrast", "large text", or "screen reader mode". Popular vendors: accessiBe, UserWay, AudioEye, EqualWeb.

The promise: installs in one line, fixes accessibility automatically, keeps you compliant with WCAG, ADA, and EAA.

The reality: none of that is true.

The Evidence Against Overlays

1. They don't fix the code

Overlays add a layer on top of broken HTML. The underlying accessibility issues remain. Screen readers still encounter the broken code underneath.

• Automated tools detect only 30-57% of WCAG issues (WebAIM, 2024)
• Overlays can only attempt to fix what automated tools detect
• The remaining 43-70% of issues are completely untouched

2. The ACM study: blind users say they make things worse

The Association for Computing Machinery published a study where blind users said overlay widgets made problems worse:

• Overlays interfere with screen reader navigation
• "Screen reader mode" conflicts with actual screen readers (NVDA, JAWS, VoiceOver)
• Added keyboard shortcuts override users' existing shortcuts
• Users couldn't complete tasks they could previously do

3. The legal record is damning

2024-2025 in the US:

• 1,023 companies using overlay widgets received accessibility lawsuits
• 25% of all accessibility lawsuits in 2024 cited overlays as the problem
• 456 lawsuits filed against overlay-equipped sites in H1 2025 alone

The $1M fine: In January 2025, the FTC fined accessiBe $1 million for misrepresenting its AI capabilities and using fake reviews. The ruling specifically noted that the company's claims of automated ADA compliance were false.

The class actions:

• accessiBe — Class action filed June 2024 for false ADA compliance claims
• UserWay — Class action filed February 2025

4. The European Commission rejects them

The European Commission has explicitly stated that accessibility overlay widgets do not constitute compliance with the EAA. The EAA requires remediation of the actual product, not a cosmetic layer on top.

When Spanish enforcement bodies start auditing (the EAA entered into force in June 2025), overlay-equipped sites will not pass.

5. Installing an overlay increases legal risk

This is counterintuitive but well-documented: installing an overlay signals that you know about accessibility issues but chose a known-ineffective solution. Plaintiffs' lawyers specifically target overlay-equipped sites because:

• The overlay itself is evidence of awareness
• The overlay doesn't actually fix the issues
• The sales claims create a basis for misrepresentation claims

What Works Instead

1. Use real automated testing

Instead of an overlay, use standards-based testing tools:

• axe-core (Deque, MPL-2.0) — The industry standard. Used by Google Lighthouse, Microsoft Accessibility Insights, and GitHub. Zero false positives. 6,900+ GitHub stars, 3 billion+ downloads.
• QualWeb — Used by the Portuguese government's accessibility observatory.
• IBM Equal Access — Complementary ruleset with cognitive accessibility focus.

These engines find ~57% of WCAG issues through automated scanning. That's not 100%, but it's a real 57% — not theater.

2. Fix the actual code

Automated scanning tells you what's broken. Fix it in the HTML, CSS, and JavaScript. Yes, this takes developer time. Yes, this is the only thing that actually works.

Common fixes:

• Add alt text to images
• Add proper labels to form fields
• Fix heading hierarchy (h1 → h2 → h3)
• Add ARIA labels where needed
• Ensure keyboard focus is visible
• Check colour contrast ratios

3. Do manual testing

Automated tools miss 43% of issues. For full compliance, you need:

• Screen reader testing (NVDA free, JAWS or VoiceOver)
• Keyboard-only navigation testing
• Testing with users with disabilities
• Cognitive accessibility review

4. Generate a real accessibility statement

EN 301 549 and the EAA require you to publish an accessibility statement that declares your compliance status honestly. If you're partially conformant, say so. If you have known limitations, list them. Lying on an accessibility statement is worse than having accessibility issues.

Regulia generates EAA-compliant accessibility statements based on real scan results.

5. Monitor continuously

Accessibility is not a one-time fix. Every deployment can introduce new issues. Integrate testing into your CI/CD pipeline and run scheduled scans on production.

The Cost Comparison

What This Means for You

If you're currently using an overlay widget:

1. Don't panic, but plan to remove it
2. Run a real scan with axe-core or our free scanner
3. Fix the actual issues starting with critical and serious violations
4. Publish an honest accessibility statement
5. Document your remediation plan — this is your defense if sued

If you haven't done anything yet:

1. Don't buy an overlay — you've been warned
2. Start with a free scan to see what you're dealing with
3. Budget developer time for code-level fixes
4. Consider tools like Regulia that use real testing + AI-assisted remediation

A Quick Self-Test

Visit your website. Try these:

• Can you navigate the entire site using only the Tab key?
• Can you fill out and submit a form using only the keyboard?
• Turn off your monitor or close your eyes. Can you use the site with a screen reader?
• Is all text readable at 200% zoom without horizontal scrolling?
• Does every image have a meaningful alt text?

If any of these fail, an overlay won't fix it. Code-level work will.

The Bottom Line

Overlay widgets are a legal, technical, and ethical failure. The FTC fined them. Blind users reject them. The EU Commission rejects them. The accessibility community has been warning against them for years.

There's no shortcut to accessibility compliance. The shortcut is expensive, doesn't work, and increases your legal risk.

Use real tools. Fix the code. Be honest about your status. That's it.

---

Regulia uses axe-core — the open source industry standard from Deque — for real code-level accessibility scanning. No overlays, no promises of magic compliance. Try the free scanner.