If you’ve researched WordPress accessibility, you’ve likely encountered products like accessiBe, UserWay, and other “accessibility overlays.” These tools promise to make your site WCAG compliant by adding a single line of JavaScript. It sounds appealing — but the reality is far more complicated.
What Is an Accessibility Overlay?
An accessibility overlay is a JavaScript widget that loads on top of your website. It typically adds a floating button that opens a panel with options like font size adjustment, contrast modes, and reading aids. Some overlays also use AI to attempt runtime fixes, like adding alt text to images or modifying ARIA attributes.
The key word is “runtime.” Overlays don’t change your actual HTML. They layer modifications on top using JavaScript. When the script is removed, blocked, or fails to load, all the accessibility improvements vanish.
Why the Accessibility Community Opposes Overlays
The opposition to overlays is not a fringe opinion. It is the mainstream position of the accessibility profession:
- The National Federation of the Blind publicly asked accessiBe to stop claiming their product makes sites accessible and to stop targeting the blind community in their marketing.
- The FTC fined an accessibility overlay provider $1 million for deceptive marketing practices.
- Over 700 accessibility professionals signed the Overlay Fact Sheet (overlayfactsheet.com) opposing overlay products.
- WebAIM’s Million study found that sites with overlays did not show measurable accessibility improvements.
The Problems with Overlays
They Don’t Fix the Code
If your HTML has a missing alt text attribute, an overlay might inject one via JavaScript. But screen readers often process the page before the overlay script runs. The fix is inconsistent, unreliable, and invisible to search engines. The actual HTML remains broken.
Single Point of Failure
If the overlay’s CDN goes down, your accessibility features disappear. If a visitor uses an ad blocker that catches the script, the widget never loads. If the overlay company changes their code, your site’s behavior changes without your knowledge or consent.
Privacy Concerns
Overlays load external JavaScript from third-party servers on every page. This means the overlay company can track every visitor to your site. For sites that need GDPR compliance, this is an additional liability.
Legal Risk
Companies using overlays have been sued for ADA violations. Courts have consistently found that having an overlay installed does not constitute adequate accessibility remediation. The Department of Justice has stated that overlays alone are not sufficient for compliance.
How EASWP Is Different
EASWP takes the approach recommended by accessibility experts: fix the actual code.
- Code-level scanning: EASWP scans your HTML across 11 WCAG categories and identifies specific issues in your content.
- Permanent fixes: When you apply a fix, it modifies your actual WordPress content. The fix persists regardless of whether EASWP is active.
- Self-hosted: Everything runs on your server. No external scripts, no CDN dependency, no data leaving your site.
- Human review: AI generates fix suggestions, but you review and approve every change before it’s applied.
Yes, EASWP also includes a front-end accessibility toolbar — because user preference controls (like font size and contrast adjustments) are genuinely useful features for visitors. But the toolbar is a complement to real code-level fixes, not a substitute for them.
The Bottom Line
Overlays cost more ($490/yr vs $69/yr for EASWP), provide less (no scanner, no reports, no permanent fixes), and carry legal risk. EASWP costs less, does more, and follows the approach recommended by every major accessibility organization.
Try EASWP Pro free for 7 days and see real, code-level accessibility for yourself.