FeaturesPricingAudit GuideFree StatementDashboard →

Why Accessibility-Only Tools Fail Legal Tests

Why accessibility-only tools and overlays don't work. Legal problems, coverage gaps, and why integrated compliance (accessibility + privacy + security) is required.

9 min read

Overview

Many companies sell 'accessibility overlays' and 'accessibility-only' tools promising to solve compliance in days. They fail. Courts reject overlays. Regulators don't recognize them. Disabled users find them insulting. This article explains why and the alternative.

Why This Matters

Accessibility overlay companies misrepresent their capabilities, charging $500-$5000/month for tools that don't work. Organizations waste money, don't achieve actual accessibility, then face lawsuits anyway. You're not alone in falling for this; 1000s have. But courts have decided: overlays are not acceptable.

Key Points

Overlays don't fix the underlying code; they hide problems

Overlays inject JavaScript to 'fix' accessibility via front-end manipulation. They don't fix HTML, CSS, or JavaScript issues. They mask problems; disabled users still encounter barriers. Courts view overlays as cosmetic, not substantive fix.

Overlays fail disabled users in real-world use

Overlays can't handle dynamic content, complex pages, or edge cases. Screen reader + overlay often clash, breaking accessibility worse. Disabled users hate overlays; they feel patronizing and often don't work.

Courts have rejected overlays as evidence of compliance

Multiple ADA lawsuits (Domino's, Winn-Dixie, HomeDepot) have had overlay companies sued ALONGSIDE the website. Courts refuse to view overlays as accessibility fix. Using overlay actually increases legal exposure (showing you knew about accessibility, didn't fix it).

Overlays don't cover privacy or security compliance

Overlay companies claim to cover ADA. They don't address GDPR, CCPA, HIPAA, or WCAG. Organizations using overlays miss privacy violations occurring simultaneously with accessibility violations.

Overlays create false sense of security

Organizations deploy overlay, believe they're compliant, ignore real accessibility work. Then lawsuit hits; overlay didn't help. Worse: showing you spent money on overlay (but not real fix) makes judge skeptical of 'good faith' defense.

SiteArmor's integrated approach solves accessibility + privacy + security

SiteArmor doesn't overlay; it identifies and helps remediate real issues. Covers accessibility (WCAG 2.1 AA), privacy (GDPR, CCPA), security (HIPAA, PCI). Single audit covering all compliance areas.

Action Items

True accessibility: WCAG 2.1 AA remediation (not overlays)Privacy: GDPR, CCPA compliance (overlays don't cover)Security: HIPAA, PCI-DSS (overlays don't cover)Legal defense: documentation of good-faith effortUser experience: real accessibility vs. theater
→

If using overlay: REMOVE IT. Overlays increase liability rather than reduce it. Courts have ruled them inadequate.

→

Conduct real accessibility audit: WCAG 2.1 AA compliance. Identify actual issues.

→

Fix code: update HTML, CSS, JavaScript. Make site genuinely accessible.

→

Test with disabled users: get real feedback. Overlays can't replace this.

→

Audit privacy/security: ensure GDPR, CCPA, HIPAA compliance concurrent with accessibility.

→

Document remediation: keep records of accessibility work. Show good-faith effort to court.

→

Use SiteArmor or similar: integrated platform covering accessibility + privacy + security audit, remediation, ongoing monitoring.

Common Mistakes

✗

Deploying accessibility overlay thinking it solves ADA compliance (it doesn't; courts have ruled against overlays)

✗

Believing overlay company's claims that they make sites accessible (false; overlays are theater)

✗

Using overlay as substitute for real accessibility work (sets up expensive lawsuit later)

✗

Not auditing privacy/security because 'accessibility tool covers it' (wrong; overlays only claim accessibility)

✗

Thinking bad accessibility is fine if overlay is deployed (actually makes things worse; shows you knew about it)

✗

Hiring accessibility overlay company instead of hiring accessibility auditor (auditor finds problems; overlay hides them)

✗

Not testing overlay with actual screen readers (overlay often breaks screen reader functionality)

Frequently Asked Questions

What are accessibility overlays?
Overlay companies (Accessibe, UserWay, Equalweb, etc.) inject JavaScript into sites promising to make them accessible. They offer widget that users click to 'adjust' page for disabilities. Courts and disability advocates say this is theater; doesn't provide real accessibility. Many overlays make experience worse.
Have overlays been tested in court?
Yes. Domino's lawsuit (SCOTUS rejected Domino's appeal of lower court ruling against overlay). Winn-Dixie, HomeDepot, and others: overlay company SUED alongside website owner. Overlay didn't help; actually increased liability by showing organization knew about accessibility and chose overlay instead of real fix.
Why don't overlays work?
Overlays try to fix accessibility via JavaScript after page loads. They can't: add alt text to server-side images, make keyboard navigation work (requires JavaScript every interaction), handle dynamic content updates, work with multiple assistive technologies. Disabled users report overlays often break accessibility worse.
What should I do if I'm using an overlay?
Remove it. Hire accessibility auditor to find real issues. Fix issues in code. Test with real disabled users. Deploy SiteArmor or similar for ongoing compliance monitoring. Overlay is sunk cost; real accessibility is investment.
Isn't SiteArmor just another tool?
No. SiteArmor is auditing + remediation + monitoring platform. It identifies real issues, suggests code fixes, tests with actual assistive tech, covers accessibility + privacy + security (overlays only claim accessibility). SiteArmor helps you actually fix problems; overlays hide them.

Check your website for free

Get your ADA, WCAG, privacy & security score in 90 seconds.

No credit card
WCAG 2.1
ADA
Privacy

Related guides