Compare
OverlayRisk vs UserWay claims
UserWay is sold as a fast widget that brings a site toward WCAG and ADA compliance. OverlayRisk is an independent witness that loads your page with the widget on, then off, runs axe-core both ways, and documents the measurable difference. It produces evidence about your specific page, not a conclusion about the vendor.
What this is
OverlayRisk documents observable differences in axe-core output between widget-enabled and widget-blocked renders of your page. It is evidence, not a compliance certification, and it is not legal advice. References to UserWay describe how the product is publicly marketed and what independent testers have widely reported — not a determination that any specific site is non-compliant.
The claim being tested
UserWay is one of the most widely deployed accessibility widgets. It is marketed as a way to improve WCAG conformance and address ADA obligations by adding a small script, typically with an accessibility menu and statement displayed on the site. Many site owners install it, publish a compliance statement, and assume the work is done.
Independent accessibility professionals and disability-advocacy organizations have repeatedly reported that a widget does not necessarily change what a real assistive-technology user experiences on the underlying page, and overlays have been named in ADA web-accessibility litigation. OverlayRisk does not assert that about your site. It measures it.
The regulatory record
The overlay category is already under regulatory scrutiny. In April 2025 the FTC approved a final order requiring accessiBe — a competing overlay vendor — to pay $1 million over the claims it made about its accessibility overlay. That order is specific to accessiBe, not UserWay, but it is the reason a published compliance statement and a vendor badge are no longer self-evident proof for any overlay.
UserWay also publishes a large customer footprint that is publicly enumerable through tools like BuiltWith, so a site running the widget is straightforward for a plaintiff or researcher to identify. OverlayRisk does not argue about what that means for you; it gives you your own timestamped before/after evidence so the question is answered with data instead of the vendor's assurance.
Sources: FTC final order (Apr 2025); BuiltWith UserWay website list.
Side by side
| Question | UserWay | OverlayRisk |
|---|---|---|
| What it is | Accessibility widget you install | Independent before/after witness you run |
| Who runs it | The vendor’s script, on your site | You or your agency, from outside |
| Tests widget off? | No | Yes — both states, same page |
| Output | Compliance scan + accessibility menu | Rule-by-rule axe-core diff + snapshots |
| Timestamped evidence? | Not as neutral proof | Yes — every finding |
| Independent of vendor? | No | Yes, by design |
How the independent before/after test works
- You submit a URL from a site running UserWay.
- OverlayRisk loads the page in a hosted headless browser with the UserWay widget active and runs axe-core.
- It reloads the same page with the widget blocked and runs axe-core again.
- It records the rule-by-rule difference between the two runs — which violations the widget added, removed, or left untouched.
- It captures timestamped DOM snapshots and screenshots of both states and packages them into a Risk Packet.
The Risk Packet is the artifact that answers the real question: not “is the widget running?” but “what did the widget actually change on this page?”
Frequently asked
Does the UserWay widget make a website WCAG compliant?
UserWay markets its accessibility widget as a fast path to WCAG and ADA conformance. Independent accessibility testers and disability-advocacy groups have widely reported that overlays often leave the underlying page unchanged for people using real assistive technology. OverlayRisk does not resolve that by opinion — it runs your specific page with the UserWay widget on and off and records the measurable axe-core difference. The result is evidence about your page.
How is OverlayRisk different from UserWay’s own scanner?
UserWay sells the widget and the scanning tools that report on it. Those tools tell you what the widget detects. They do not load your page with the widget blocked, so they cannot show you what the widget actually changed. OverlayRisk is run by you or your agency, not the vendor, and tests the page from outside the widget’s own system.
Is this legal advice or a compliance certification?
No. OverlayRisk produces evidence documentation only. Every finding is tied to a page, a timestamp, and a snapshot. It documents observable differences in axe-core output; it does not determine whether your site meets any legal standard. What the evidence means for your site is a question for your counsel.
Will running this affect my UserWay subscription or installation?
No. OverlayRisk loads your public page in a hosted headless browser the same way a visitor would, once with the UserWay widget active and once with it blocked. It does not modify your site, your UserWay account, or any of your code.
How much does an independent UserWay test cost?
The Free Witness tests one page and shows one real before/after finding at no cost and no signup. The full Risk Packet — every rule diff, timestamped DOM snapshots, and screenshots — is $49 one-time. Ongoing monitoring is $99/mo (Drift Monitor, up to 20 pages) or $249/mo (Agency Watch, multi-client).
Test your UserWay page now
One page, no signup. If a UserWay overlay is detected, you'll see one real before/after finding for free. The full packet is $49.