An Accessibility Overlay Alternative That Actually Fixes Things
Overlays like accessiBe, UserWay and AudioEye bolt a widget onto your site and promise automatic compliance. Loupe does the opposite: it finds the real WCAG issues in your code and shows you how to fix them — an honest audit, not a band-aid. Free, in Chrome & Edge.
No widget on your site · finds real issues · runs locally
If you've landed here, you've probably already had the suspicion: can you really make a website accessible by pasting in one line of JavaScript? It's a fair question, and the honest answer from the accessibility community is no. Overlay widgets — accessiBe, UserWay, AudioEye and similar — sit on top of your existing site and try to patch things at runtime. They can be a tempting shortcut, but they don't change the underlying code, and that's where real accessibility lives. Loupe takes the other road: it shows you the actual issues so you (or your client) can fix them properly.
What an accessibility overlay actually does
An overlay is a script you add to your site that injects an accessibility toolbar — usually buttons to change font size, contrast, spacing, or to trigger a screen-reader-like mode. Some of those user-preference controls are genuinely nice to have. The problem is the bigger promise that often comes with them: that the same widget automatically detects and fixes your site's accessibility problems and makes you WCAG or ADA compliant. That part is where overlays and the accessibility community part ways.
Why teams look for an alternative
The recurring reasons people move from an overlay to a real audit:
- They don't deliver real conformanceAn overlay can't restructure your headings, fix your form labels, or rewrite bad alt text in a way that holds up. Hundreds of accessibility professionals have publicly said overlays do not make a site conformant on their own.
- They can get in the way of real assistive techMany screen-reader users report that overlays interfere with the tools they already use and trust, sometimes making a site harder to use, not easier.
- A widget is not a legal shieldSites running overlays have still received ADA demand letters and lawsuits. In 2024 the U.S. FTC fined overlay vendor accessiBe $1 million over misleading claims that its product could make any website fully compliant automatically.
- The cost never stopsOverlays are an ongoing per-site subscription that masks the problem indefinitely — you pay forever and the underlying issues are still there.
- Nothing to hand a clientAn overlay gives you a badge, not evidence. Agencies and freelancers need to show what was actually checked and fixed.
Loupe vs an accessibility overlay, side by side
| Loupe | Overlay widgets | |
|---|---|---|
| Approach | Finds the real issues so you fix the code | Adds a script on top of the site |
| Helps you reach real WCAG conformance | Yes — by fixing the actual barriers | No — the underlying code is unchanged |
| Touches your live production site | No — scans locally, changes nothing | Yes — injects a widget for all visitors |
| Works with users' own assistive tech | Doesn't interfere with it | Can conflict with screen readers |
| What you get | An audit + plain-English fixes + report | A toolbar and a compliance claim |
| Evidence for clients | White-label PDF report (Pro) | A badge, not a record of work |
| Cost model | Free scan · $19/mo or $190/yr Pro | Ongoing per-site subscription |
| Made for | Devs, agencies & teams who want to fix it | Owners wanting a quick badge |
Overlays do offer some user-preference controls; the comparison above is about achieving genuine accessibility, which is a different job.
What to do instead
Real accessibility isn't a switch you flip — it's a short, repeatable loop: find the issues, fix them in the code, and keep a record. That's exactly the loop Loupe is built for. Open any page, click once, and every issue shows up in plain English with the WCAG success criterion behind it and how to resolve it. Fix it in your markup, re-scan, and export a report when you're done — proof of the work, with your own branding if you're handing it to a client.
And here's the honest part overlays never tell you: no automated tool, Loupe included, catches everything. Automated scanning is a fast, thorough first pass that handles the mechanical issues; a human still has to judge things like logical reading order, meaningful alt text, and keyboard flow. The difference is that Loupe is upfront about that line — and points you at the real work instead of hiding it behind a widget.
Fix it for real — no widget required
Add Loupe, open any page, and click once. Every accessibility issue in plain English, with the fix — and a client-ready report when you need one.
Add Loupe to Chrome — freeFree forever for scanning. Pro ($19/mo or $190/yr) adds full-site crawl, AI explanations, saved projects, and white-label PDF reports.
FAQ
Do accessibility overlays make a website WCAG compliant?
No. Overlays like accessiBe, UserWay and AudioEye add a layer on top of your site but don't change the underlying code, and accessibility experts widely agree they can't make a site conformant on their own. Sites using overlays have still received ADA demand letters. Real conformance comes from finding the actual issues and fixing them — which is what Loupe is for.
Is Loupe an accessibility overlay?
No — it's the opposite. Loupe doesn't inject anything into your live site or promise automatic compliance. You scan a page, it shows the real WCAG issues in plain English with how to fix them, and you fix them in your code. Nothing changes for your visitors until you ship a real fix.
What's a good alternative to accessiBe or UserWay?
If you want to actually fix accessibility instead of masking it, use an audit tool rather than an overlay. Loupe scans any page for contrast, alt text, labels, ARIA and heading issues, explains each with its WCAG criterion, and exports a white-label report. Scanning is free in Chrome and Edge.
Can an accessibility overlay get me sued?
Adding an overlay doesn't protect you from accessibility lawsuits — plaintiffs have specifically targeted sites using them, and in 2024 the FTC fined accessiBe $1 million over misleading compliance claims. The durable way to reduce risk is to fix the real barriers and keep a record of the work.