Guide
Accessibility overlays vs real compliance
Last updated: 27 June 2026
If you've searched for a quick way to make your website compliant, you've probably seen accessibility overlay widgets — products like accessiBe, UserWay, AudioEye, and similar. They promise instant compliance from a single line of JavaScript. It's an appealing pitch. It's also one the accessibility community broadly rejects, for reasons worth understanding before you buy.
What an accessibility overlay is
An overlay is a script you add to your site that layers an accessibility toolbar and a set of automated adjustments on top of your existing code — things like a contrast toggle, font resizing, and attempts to auto-fix some issues at runtime. The underlying HTML doesn't change; the overlay tries to patch over it in the browser.
Why overlays don't equal compliance
The core problem: an overlay can't fix what it can't understand. Automated detection only catches a portion of WCAG criteria, and automated correction is even more limited. An overlay can't reliably write meaningful alt text, fix a broken keyboard flow in a custom widget, repair illogical reading order, or judge whether link text makes sense. It papers over symptoms rather than fixing the source.
There's also evidence that some overlays actively interfere with the assistive technology people already use — fighting with screen readers, hijacking keyboard shortcuts, or adding confusing extra controls. Many disabled users report turning overlays off to use a site. A fix that the people it's meant to help disable is not a fix.
The community position
Accessibility practitioners and disabled users have been consistent and public about this. A widely signed open letter (Overlay Fact Sheet) calls for overlays to be avoided as a compliance solution, and many accessibility professionals refuse to recommend them. The guiding principle — "nothing about us without us" — is why community-aligned products avoid overclaiming. (Specific signatory counts and individual vendor disputes change over time, so check current sources before quoting any.)
The legal-risk angle
Here's the part that surprises people: an overlay can increase legal exposure rather than reduce it. Buying an overlay does not make a site immune to accessibility complaints or lawsuits, and there have been cases where sites running overlays were still the subject of accessibility litigation. A widget that advertises "compliance" but doesn't deliver it can also create a gap between what you've claimed and what's true. Litigation specifics and outcomes vary by jurisdiction and case, so treat this as general context, not legal advice, and consult counsel for your situation.
What real compliance looks like
The path that actually works is unglamorous but durable: audit, fix the source, and re-test.
- Audit: run an automated scan to find machine-detectable issues, then do manual testing (keyboard, screen reader, zoom, forms, media) for the rest.
- Remediate at the source: fix the actual HTML, ARIA, and content — real alt text, real labels, real focus management — not a runtime patch.
- Re-test and prevent regressions: verify the fixes, then build accessibility into design and QA so it doesn't decay.
- Document: keep a record and publish an accessibility statement with a way to report problems.
For a step-by-step version of this, see our EAA compliance checklist and how to check if your site is WCAG 2.2 AA compliant.
Where WCAGwise fits — and where it doesn't
WCAGwise is the opposite of an overlay. It does not inject anything into your live site and it makes no "now you're compliant" claim. It's an audit aid: it scans a page in your browser, shows you the real issues worst-first with the WCAG criterion for each, and — with Pro — exports a report you can use to plan and evidence remediation. The fixing still happens in your code, where it belongs, and manual testing is still required.
That honesty is deliberate. The goal is to help you do the real work, not to sell you a shortcut that doesn't exist.
A better starting point than a widget
If you were about to add an overlay, do this instead: Free scanner (coming soon) with WCAGwise, see the actual issues, and fix them at the source. When you need to show your work, export an EAA-mapped report — see the Pro report option. It's an audit aid, not a legal guarantee of compliance — and that's exactly the point.