How can I prove my website is monitored for accessibility?

Q: How can I prove my website is monitored for accessibility?

Keep a dated record that someone else can check. Test regularly against WCAG 2.2 A and AA, log every check and fix with its date, chain the entries so a later edit would show, and have the record stamped by an outside RFC 3161 timestamp authority. No one can certify ADA compliance, so a verifiable record is what you can show.

Published 12 October 2026 · General information, not legal advice

This is general information, not legal advice.

Why "we monitor it" needs proof

No one can certify a website. The US Department of Justice does not certify any website or product as ADA compliant, so a certificate or "compliant" seal from a vendor is a marketing claim, not proof.
Demand letters ask for it. In the United States, a website accessibility demand letter usually asks for fixes, a commitment to keep monitoring and fees. See website accessibility law in the United States.
The EU asks you to explain it. Under the European Accessibility Act, an online shop must meet the accessibility requirements and publish information on how its service meets them. See does the European Accessibility Act apply to my online store?

In each case, what you can actually show is what you tested, what you found, what you fixed and when.

What makes a monitoring record believable

Property	Why it matters
Regular, dated checks	Shows monitoring was ongoing, not a one-off scan the week a letter arrived.
Every problem and fix recorded	Shows when a barrier was found and when it was removed.
Tamper-evident	If each entry carries a fingerprint (a hash) of the one before it, editing or deleting an old entry breaks the chain, so a change would show.
Independently timestamped	A Time-Stamp Authority under RFC 3161 certifies that a piece of data existed at a given time. Stamping the record's latest fingerprint proves the record existed then, without trusting whoever keeps it. Stamps can be checked with standard tools such as `openssl ts -verify`.
Exportable	Your lawyer, an auditor or a regulator can read it without an account.
Honest about limits	Automated testing against WCAG finds many, not all, accessibility problems. A credible record says so and includes manual testing.

How Jralo keeps that record

Daily checks. On paid plans Jralo checks your homepage and up to five linked pages every day against WCAG 2.2 A and AA with axe-core, plus website QA: broken links, page errors, broken images and slow pages.
An append-only, hash-chained evidence log. Every check, problem and fix is written to it in order, each entry linked to the one before.
An outside timestamp every day. The latest fingerprint of the log is stamped once a day by an outside RFC 3161 timestamp authority.
Export. Download the log as PDF and CSV.
Your own tests too. Results from axe-core, Playwright or Lighthouse in your CI can go into the same log; see accessibility testing in CI.
A public record, if you want one. An optional page at jralo.com/monitored/your-site, a live badge and a listing in the public directory show that the site is checked every day. They never show issues or scores, and they never say a site meets any law.

What a record does not do

It does not make a site compliant, and Jralo never says it does. Fixing the problems is what makes a site usable; Website Mechanic can fix them in your code as a pull request.
It is not legal advice. Whether a record helps with a particular claim is a question for your lawyer; see what to do with an ADA demand letter.

Check your site now

Jralo's free check tests your homepage and up to five pages for accessibility (WCAG 2.2 A and AA) and website QA problems. No sign-up.

Run the free check