Turning an Accessibility Scan Into EAA Evidence

Most accessibility checkers hand you a wall of warnings and a number. That is useful for a developer on a Tuesday. It is not what a market-surveillance authority, an enterprise procurement team, or your own legal counsel is asking for. They want evidence: what was tested, when, against which standard, and what the result was — in a form nobody can quietly edit afterwards.

From findings to a record

A11yProof loads your page in a real headless browser and runs axe-core, the same open-source engine accessibility teams trust, against the WCAG 2.2 AA rule set. Every finding is tied to the exact element, the failing rule, and the matching WCAG success criterion — so a finding is traceable, not just a colour-coded blob.

Those findings then roll up into two artefacts you can actually hand over:

• A PDF audit report — an executive summary plus severity-grouped findings and remediation pointers.
• An EAA accessibility statement — templated around what EN 301 549 and the EAA expect: conformance level, known limitations, assessment method and date, and a feedback contact.

Tamper-evident by design

Evidence you can silently rewrite is not evidence. Every A11yProof document carries a unique reference and a SHA-256 fingerprint. Anyone — an auditor, a customer, a regulator — can visit the public verify page, upload the PDF they were given, and confirm it is byte-for-byte the document on record. The comparison runs entirely in their browser; the file never leaves it.

Scope that matches the law

The EAA is about whole services, not single pages. A11yProof crawls your site and audits each page, then aggregates the result — so your evidence reflects the checkout flow and the account pages, not just the homepage you remembered to test.

The honest part

We will never print "100% compliant" on a document, because no automated tool can establish it. Automated testing covers roughly 30–40% of WCAG success criteria. What A11yProof gives you is the fast, repeatable, documented baseline — the part you can automate and prove — which you then pair with manual review for full coverage. An accessibility statement built on that footing is one you can defend.

General information, not legal advice.