Compare
OverlayRisk vs accessiBe claims
accessiBe is sold as a one-line fix that makes a site WCAG and ADA compliant. OverlayRisk is an independent witness that loads your page with the overlay 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 overlay-enabled and overlay-blocked renders of your page. It is evidence, not a compliance certification, and it is not legal advice. References to accessiBe 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
accessiBe is one of the most widely deployed accessibility overlays. It is marketed as a way to make a website conform to WCAG and meet ADA obligations by adding a single line of JavaScript, with an accessibility statement and a badge 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 an overlay 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
In April 2025 the FTC approved a final order requiring accessiBe to pay $1 million over the claims it made about its accessibility overlay. That order is about the vendor's marketing, not about your specific page — but it is the reason a published compliance statement and a vendor badge are no longer self-evident proof.
accessiBe also publishes a large customer footprint that is publicly enumerable through tools like BuiltWith, so a site running the overlay 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 accessiBe website list.
Side by side
| Question | accessiBe | OverlayRisk |
|---|---|---|
| What it is | Accessibility overlay 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 overlay off? | No | Yes — both states, same page |
| Output | Compliance dashboard + badge | 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 accessiBe.
- OverlayRisk loads the page in a hosted headless browser with the accessiBe overlay active and runs axe-core.
- It reloads the same page with the overlay blocked and runs axe-core again.
- It records the rule-by-rule difference between the two runs — which violations the overlay 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 overlay running?” but “what did the overlay actually change on this page?”
Frequently asked
Does the accessiBe overlay make a website WCAG compliant?
accessiBe markets its overlay as a way to reach WCAG and ADA conformance from a single line of JavaScript. Independent accessibility testers and disability-advocacy groups have widely reported that the underlying page is often unchanged for people using real assistive technology. OverlayRisk does not settle that debate by opinion — it runs your specific page with the overlay on and off and records the measurable axe-core difference. The result is evidence about your page, not a general conclusion about the vendor.
How is OverlayRisk different from accessiBe’s own dashboard?
accessiBe sells the overlay and the monitoring dashboard that reports on it. That dashboard tells you whether the overlay appears to be running. It does not load your page with the overlay blocked, so it cannot show you what the overlay actually changed. OverlayRisk is run by you or your agency, not the vendor, and tests the page from outside the overlay’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 damage my accessiBe installation?
No. OverlayRisk loads your public page in a hosted headless browser the same way a visitor would, once with the overlay active and once with it blocked. It does not modify your site, your accessiBe account, or any of your code.
How much does an independent accessiBe 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 accessiBe page now
One page, no signup. If an accessiBe overlay is detected, you'll see one real before/after finding for free. The full packet is $49.