If you’ve searched for accessibility solutions, you’ve likely encountered overlay widgets — JavaScript-based tools from companies like accessiBe, UserWay, and others that add an accessibility layer on top of your site. EASWP takes a fundamentally different approach. Here’s how they compare and why it matters.
How Overlays Work
Overlay widgets inject a third-party JavaScript file into your site. This script runs in your visitor’s browser and applies cosmetic CSS adjustments — larger text, higher contrast, modified colors — at render time. The underlying HTML of your site is unchanged. Your actual code still has the same missing alt text, broken heading hierarchy, or unlabeled form fields.
This is sometimes called “remediation at the presentation layer.” The fixes are applied when the page renders, not in the source code.
How EASWP Works
EASWP is a WordPress plugin that runs inside your WordPress installation. It has two main components:
- An accessibility toolbar that visitors use to customize their browsing experience (similar to what overlays offer, but self-hosted)
- A WCAG scanner and fix engine that identifies issues in your actual code and, with Pro, suggests real code-level fixes you can review and apply
The key difference is that EASWP helps you improve your actual source code, not just change how it renders for visitors using the toolbar.
What This Means in Practice
For screen reader users: An overlay’s visual adjustments don’t change what a screen reader reads. Missing alt text is still missing. Broken heading structure is still broken. EASWP’s scanner and fixes address these at the code level, which benefits all users — including those using assistive technology.
For compliance: Major accessibility lawsuits have targeted sites using overlays, arguing that cosmetic presentation changes don’t constitute actual remediation. The FTC fined accessiBe $1 million in 2024 for deceptive claims about their overlay’s compliance capabilities. Whether this changes your legal strategy is a conversation for your legal counsel, but it’s context worth knowing.
For performance: Overlays load a third-party JavaScript file on every page load. EASWP’s toolbar is served from your own server with no external CDN dependency, giving you more control over performance.
Where Overlays Have Advantages
To be fair:
- Platform agnostic: Overlays work on any website (Shopify, Squarespace, custom builds). EASWP is WordPress-only.
- Faster initial deployment: Adding a script tag takes less time than running scans and applying fixes.
- Larger companies: accessiBe and UserWay have more brand recognition and larger support teams.
Our Perspective
We believe the best accessibility comes from fixing your actual code — not masking issues with JavaScript. For WordPress site owners, a WordPress-native tool that integrates into your admin dashboard, scans your real content, and helps you make real improvements provides more lasting value than a widget that sits on top.
That said, any accessibility effort is better than none. If an overlay is your starting point while you work toward deeper remediation, that’s a reasonable step. We’d just encourage you to not stop there.
See detailed feature comparisons →