title: Accessibility Overlays Don’t Work — And May Increase Your Legal Risk
published: false
canonical_url: https://wcagsafe.com/blog/accessibility-overlays-dont-work
description: Accessibility overlays promise instant ADA compliance, but they often fail in practice and may increase legal risk. Here's what actually works.
tags: accessibility, webdev, seo, legal
Using an accessibility overlay? You may still be at legal risk.
Dozens of ADA lawsuits have been filed against websites that had overlay tools installed. Courts assess whether users can actually access your site — not whether a widget is present.
What Is an Accessibility Overlay?
An accessibility overlay is a third-party script added to your website that layers user-facing controls on top of your existing pages.
Typical features include:
- Larger text
- High-contrast or dark mode
- Dyslexia-friendly fonts
- Keyboard navigation helpers
- Text-to-speech
- Pause animations
Some vendors claim AI can automatically fix accessibility issues by injecting ARIA labels or modifying structure dynamically.
Sounds good — but it doesn’t hold up in real-world use.
Why Businesses Fall for Overlays
Overlay tools sell a simple promise:
- “WCAG 2.1 AA compliant in 48 hours”
- “Reduce legal risk instantly”
- “No code changes needed”
For non-technical business owners, this feels like an easy solution.
But accessibility isn’t something you can bolt on afterward.
The Core Problem
Accessibility is about how your site is built, not how it looks.
Common issues include:
- Missing alt text
- Unlabeled form fields
- Non-semantic buttons
- Broken keyboard navigation
- Missing captions
- Poor heading structure
These exist in your actual code — not the visual layer.
An overlay is like painting a ramp over stairs in a photo. The stairs are still there.
8 Reasons Accessibility Overlays Fail
1. They Can’t Fix Semantic Structure
Screen readers depend on proper HTML structure. Overlays can’t reliably fix incorrect markup.
2. They Break Assistive Technology
Common issues:
- Duplicate screen reader output
- Keyboard traps
- Overridden user settings
3. They Only Catch ~30–40% of Issues
Automated tools miss most real accessibility problems.
4. They Shift the Burden to Users
Users must:
- Find the widget
- Activate it
- Configure it
Many can’t even access the widget in the first place.
5. Overlays Themselves Are Often Inaccessible
Many fail basic accessibility standards.
6. False Confidence
You think you're compliant → you stop fixing real issues.
7. Courts Don’t Care About Widgets
Legal standard = actual usability, not tools installed.
8. Single Point of Failure
If the script fails → accessibility disappears instantly.
Legal Reality
To meet accessibility expectations, your site must align with WCAG principles:
Perceivable
- Alt text
- Captions
- Contrast
Operable
- Full keyboard support
Understandable
- Clear navigation
- Helpful error messages
Robust
- Works with assistive tech
No major regulation considers overlays sufficient.
What Actually Works
1. Run an Automated Scan
Identify real issues quickly.
2. Fix Issues in Code
Update:
- HTML
- CSS
- JavaScript
3. Prioritize Critical Issues
Focus first on:
- Alt text
- Labels
- Keyboard access
4. Monitor Continuously
Accessibility is ongoing.
5. Document Everything
Keep records of:
- Fixes
- Scans
- Improvements
Cost Comparison
| Feature | Accessibility Overlay | Real Accessibility |
|---|---|---|
| Cost | $49–$490/month | One-time fixes |
| Fixes code? | ❌ No | ✅ Yes |
| Works with assistive tech | ❌ Often breaks | ✅ Yes |
| Legal protection | ❌ No | ✅ Yes |
| Dependency | Third-party | None |
| Reliability | Fragile | Stable |
Common Myths
“It’s better than nothing”
Not always — overlays can make things worse.
“We’ll fix it later”
Most teams don’t.
“The vendor says we’re compliant”
Vendors don’t decide legal compliance.
“Disabled users don’t visit our site”
They do — your site may just block them.
If You’re Using an Overlay
- Run a real accessibility scan
- Identify actual issues
- Fix them in code
- Monitor regularly
- Remove the overlay
FAQ
Do overlays make my site ADA compliant?
No.
Can I still get sued?
Yes.
What’s the difference?
- Overlay = visual patch
- Accessibility = structural fix
How do I find issues?
Run a WCAG scan and review violations.
The Bottom Line
Accessibility overlays are built on fear — not solutions.
They:
- Don’t fix real problems
- Can harm users
- Don’t prevent lawsuits
Real accessibility is:
- Built into your code
- Tested regularly
- Maintained over time
And most importantly — it actually works.
Originally published at https://wcagsafe.com/blog/accessibility-overlays-dont-work
Top comments (0)