DEV Community: OverlayRiskWitness

A homepage check isn't the route record

OverlayRiskWitness — Sat, 04 Jul 2026 07:01:34 +0000

A homepage pass can tell you where to start looking. It still doesn't tell you whether the claim held up on the route a person actually needed. The smaller record I trust is: statement page, support or contact path, then one live task flow — checked with the overlay present and blocked. If the route changes, that dated delta belongs in the page history, not in the score or the badge wrapped around it.

I wrote up the score-versus-evidence frame here. Evidence, not legal advice.
https://overlayrisk.com/blog/website-accessibility-score-vs-page-level-evidence?utm_source=devto&utm_medium=article&utm_campaign=launch-2026-06-30&utm_content=support_route_claim_test#run-witness

An accessibility score can triage. It can't witness a route.

OverlayRiskWitness — Fri, 03 Jul 2026 13:16:08 +0000

A score can tell you where to look first. It still can't tell you whether one route held up with the overlay on and off. The record I trust is smaller: exact page URL, timestamp, claim quote, then the same path with the overlay present and blocked. I wrote up where the score helps, where it stops, and what a page-level witness adds. Evidence, not legal advice. https://overlayrisk.com/?utm_source=devto&utm_medium=article&utm_campaign=launch-2026-06-30&utm_content=score_route_evidence_note#run-witness

A page-level accessibility statement still needs a page-level witness

OverlayRiskWitness — Thu, 02 Jul 2026 11:03:03 +0000

A page-level accessibility statement still needs a page-level witness

A public accessibility statement can describe intent, standards, or vendor coverage. It still doesn't replace a dated record of what happened on the page itself.

The smaller artifact is usually the more useful one.

Pick one live route. Quote the public claim if there is one. Capture the page and the timestamp. Then test the same task twice: once with the accessibility overlay present, and once with the overlay blocked.

That gives you a narrower question than "is this site compliant?"

It gives you: what changed on this page when the overlay loaded?

The witness format

For a technical team, the record can stay simple:

page URL
overlay state
timestamp
the exact task or path being tested
the first broken step or changed rule result
the retest with the overlay present and blocked

If keyboard reachability, focus order, labels, or error handling change between the two passes, that belongs in the page history.

Why the statement still matters

The statement is context. It tells you what the site says about accessibility, which vendor it relies on, and sometimes which standard it references.

But the statement is not the page witness.

A before/after record lets the team compare the public claim with a named page and a named task. That is a more useful engineering artifact than a broad footer promise or a vendor dashboard screenshot by itself.

What this does not prove

This is not a legal opinion.

It is not a full manual audit.

And it is not a verdict on the vendor.

It is evidence documentation: one page, one timestamp, one before/after comparison.

The practical developer use

If you inherit a site that already has an overlay installed, the first useful question usually isn't whether the marketing claim sounds strong enough.

It is whether one real path still behaves the same way when the overlay is present and when it is blocked.

That is the kind of comparison I built OverlayRiskWitness to make easier. It runs the overlay-on and overlay-blocked passes on one public page, compares the result, and shows one timestamped finding without a signup wall.

Canonical guide: https://overlayrisk.com/blog/document-website-accessibility-evidence

Free one-page witness: https://overlayrisk.com/?utm_source=devto&utm_medium=article&utm_campaign=launch-2026-06-30&utm_content=page_level_witness#run-witness

Evidence, not legal advice.

How to test what an accessibility overlay actually changes

OverlayRiskWitness — Tue, 30 Jun 2026 08:59:10 +0000

How to test what an accessibility overlay actually changes

Accessibility overlays are easy to install and hard to evaluate independently.

A site can add an overlay widget, display an accessibility statement, and still have no neutral evidence of what the overlay changed on the page. The vendor dashboard is useful, but it is not independent of the vendor.

The cleaner test is a before/after experiment.

The experiment

Take one public page.

Load it once with the overlay active.

Load it again with the overlay blocked.

Run the same automated checks on both versions.

Then compare the result.

That gives you a narrow but useful question:

What changed when the overlay was present?

What the diff can show

The result should not say "compliant" or "not compliant."

That is too broad for an automated check.

Instead, the result should say things like:

this axe-core rule failed with the overlay blocked and still failed with the overlay active
this rule changed state when the overlay loaded
this page could not be tested reliably

The useful artifact is the evidence trail: page URL, overlay state, timestamp, screenshot, DOM snapshot, and finding.

Why public claims matter

Many sites running overlays also publish accessibility statements. Some point to WCAG. Some imply ADA risk is handled. Some rely on the overlay vendor's own language.

That public claim is the context. A before/after witness can quote the claim and show what the page-level automated evidence observed.

It still does not decide legal compliance.

It gives the site owner and counsel something concrete to inspect.

Limitations

axe-core does not catch every WCAG issue. Automated checks are not a substitute for manual expert audits or user testing.

This method is not a legal opinion.

It is a way to stop arguing from marketing claims and inspect the page itself.

Try it

I built OverlayRiskWitness to run this experiment on one page for free:

https://overlayrisk.com/?utm_source=devto&utm_medium=article&utm_campaign=launch-2026-06-30&utm_content=technical_walkthrough#run-witness

Paste a URL from a site running accessiBe or UserWay. The product loads the page with the overlay on and blocked, runs the comparison, and shows one timestamped finding before signup or payment.

Evidence documentation, not legal advice.