accessiBe, UserWay, and AudioEye are accessibility “overlay” widgets — a single line of JavaScript that adds a toolbar to your site. They’re popular because they’re cheap and fast to install, but they don’t fix the underlying code. The durable alternative is manual remediation: fixing the HTML so the site actually works for everyone.
If you searched for an alternative to one of these tools, you’ve probably already sensed the catch. Below is a fair, factual look at what overlays do, where they fall short for ADA Title III compliance, and what to use instead.
What overlays actually do
An overlay is third-party JavaScript that loads after your page does. It injects a floating accessibility menu and tries to auto-detect and “patch” issues on the fly — adjusting color contrast, guessing at alt text, or re-labeling form fields using automated rules and, in some products, AI.
The pitch is appealing for a small business: one snippet, a low subscription, and an accessibility statement generated for you. accessiBe, UserWay, and AudioEye each package this slightly differently, but the core mechanism is the same — a layer that sits on top of your existing markup rather than changing it.
The problem is that accessibility lives in the markup. A screen reader like NVDA, JAWS, or VoiceOver, and the keyboard a sighted-impaired user navigates with, both read the real DOM. An overlay can only intervene in the narrow set of cases its automation recognizes.
Why overlays fall short of ADA compliance
The general, documented criticisms of overlays are consistent across the accessibility community, including WebAIM and the broader W3C/WAI ecosystem:
- Automation can’t catch most issues. Audits show automated tooling reliably detects only a minority of WCAG 2.1 AA failures. Meaningful alt text, logical heading structure, correct ARIA roles, and sensible keyboard navigation order require human judgment.
- Overlays can break assistive technology. Because they manipulate the page after load, overlays sometimes interfere with the very screen readers and browser tools users already rely on.
- Screen-reader users tend to turn them off. When surveyed, most assistive-technology users say they don’t want the widget — and many disable it on sight.
- Lawsuits still happen. Plaintiffs and serial filers have brought thousands of ADA web cases each year, including against sites running overlays. The widget did not stop the demand letter.
None of this means an overlay is fraudulent or that these companies act in bad faith. It means an overlay is the wrong tool to rely on for compliance. It addresses the symptom — “we need an accessibility button” — not the cause, which is inaccessible code.
accessiBe vs UserWay vs AudioEye vs manual remediation
Here’s how the overlay model compares with the alternative most accessibility professionals recommend. The three products differ in branding and add-ons; their shared limitation is the overlay architecture itself.
| Factor | Overlay widgets (accessiBe / UserWay / AudioEye) | Manual remediation |
|---|---|---|
| How it works | JavaScript layer on top of your code | Fixes the actual HTML, ARIA, and CSS |
| WCAG 2.1 AA coverage | Partial; automated rules only | Full criteria, verified by testing |
| Screen reader / keyboard reality | Often unreliable; can interfere | Works in NVDA, JAWS, VoiceOver |
| Holds up to a lawsuit | Weak; cases proceed anyway | Strong; defensible conformance record |
| VPAT-ready evidence | No genuine VPAT | Yes — documented audit + report |
| Cost shape | Recurring subscription | One-time project, optional monitoring |
| What you’re left with | Dependency on the vendor | Your own accessible website |
What to use instead of an overlay
The real alternative isn’t a different widget — it’s a different approach. For US small businesses, the credible path to compliance under the ADA and (for federal-adjacent work) Section 508 is the same one the DOJ points toward: conform to WCAG, the recognized technical standard built on the POUR principles (Perceivable, Operable, Understandable, Robust).
That breaks into three concrete steps:
1. Get an honest audit
A proper accessibility audit combines automated scanning with manual testing — a human navigating your site with a keyboard and screen reader. This is the difference between “no errors detected” and “actually usable.” Automated-only checks, the same kind overlays run, miss the issues that get sites sued.
2. Remediate the code by hand
Remediation is where the work happens: writing real alt text, fixing color contrast, labeling forms, correcting heading order, repairing focus management, and making interactive components keyboard-operable. These changes live in your site permanently, regardless of what subscription you do or don’t keep paying.
3. Document and maintain conformance
Once remediated, you can produce a real conformance record — and, where customers or procurement require it, a genuine VPAT. Because websites change, ongoing monitoring catches regressions before they reappear as barriers. That documentation is what actually helps if a demand letter ever lands.
Can you keep an overlay after remediating?
Yes, technically. Once your code conforms to WCAG 2.1 AA, an overlay’s reorder/resize toolbar is mostly redundant with built-in browser and operating-system features, but it won’t harm a properly built site the way it can a broken one. Most businesses that remediate end up dropping the widget because they no longer need it — the website itself does the job.
The key shift is dependency. An overlay makes your accessibility contingent on a third-party script you don’t control. Remediation makes accessibility a property of your own site.
The bottom line for small businesses
If you came here looking for an accessiBe, UserWay, or AudioEye alternative, the most useful answer is to reframe the goal. The objective isn’t “a better accessibility widget” — it’s a website real people with disabilities can use, backed by documentation that holds up if challenged. That’s manual remediation, not a layer on top of the problem.
This page is general information, not legal advice; for your specific exposure, talk to an attorney who handles ADA matters. To see exactly where your site stands today — and what an overlay is silently leaving unaddressed — start with a free accessibility scan, or read our deeper breakdown of whether accessibility overlays work.