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.