Why a pack, and not just a report
A report says what a tool found. A pack shows the whole chain: the pages visited, the raw output the rules produced, the screenshots of the elements in place, the person who tested what rules cannot, and a manifest that ties each file to a hash and a date.
That difference is what a procurement reviewer is trained to look for. Accessibility statements are read with suspicion now, and the follow-up question is always the same: how do you know. The pack is the answer you can send without writing an essay.
What is inside a pack
One archive per scan. Automated artefacts are produced by the workers; manual artefacts arrive when a tester signs the checklist.
| File | What it contains | Format | Source |
|---|---|---|---|
| executive.pdf | Two pages: score, delta, open criticals | automated | |
| technical.pdf | Finding by finding, with selectors | automated | |
| findings.json | Machine-readable findings and mappings | JSON | automated |
| axe-raw/ | Unmodified scanner output per page | JSON | automated |
| screens/ | Element screenshots in context | PNG | automated |
| checklist.pdf | Manual criteria, tester, assistive tech | manual | |
| evidence/ | Screen recordings from manual testing | MP4 | manual |
| statement.pdf | The declaration as published | manual | |
| manifest.txt | sha256 for every file, plus scan metadata | TXT | automated |
What it proves, and what it does not
The pack is deliberately honest about its own limits, because an overstated claim is the fastest way to lose an argument you were winning.
Automated testing covers a subset of accessibility barriers. Manual verification is required for a complete assessment.
How a pack is sealed
- Every file is hashed on write, and the manifest records hash, size and timestamp, so integrity can be checked with standard tools.
- The pack is immutable. A re-run produces a new pack with a new date rather than overwriting the previous one.
- The statement version that was live on the scan date is included, because an audit reads the version of the day, not the current one.
- Packs stay downloadable for the retention period even after a subscription ends, so an old claim can still be defended.
Questions we get on this
What exactly is an evidence pack?
A dated archive per scan: executive and technical reports, raw scanner output, element screenshots, the signed manual checklist and a manifest with a sha256 for every file.
Why does the manifest matter?
It lets a reader verify that the file in their hand is the file produced on that date. Without it a PDF is an assertion; with it the archive can be checked independently.
Is it a certificate?
No, and it never says it is. It is the material behind a declaration made by the operator responsible for the site.