Fictional example

A reviewable accessibility evidence pack.

This example shows the kind of dated, traceable record BarrierTrace can produce. Every organisation, website, person and result below is invented and does not describe a real customer.

Evidence snapshot

Harbour Services Portal

Example Organisation · Public website and account-registration journey

Download example JSON Verify its checksumGenerated 3 September 2026 · Example pack 1.0

Automated Health88%Down 3 points from the previous like-for-like run

Pages sampled12 / 12Stable core set, 100% completed

Open findings72 serious · 5 moderate

Human checks8 / 102 checks still need evidence

Scope and method

The snapshot covers 12 saved pages representing the homepage, service information, registration, sign-in and support journeys. The automated run completed on 3 September 2026 using the Standard portfolio profile.

Standard lens: WCAG 2.2 AA web criteria
Automated engine: CWAC with axe-core 4.12.1 plus title, reflow and readability evidence
Viewports: Mobile 375 × 812 and desktop 1440 × 900 where supported by the check
Evidence coverage: 34 automated rule candidates and 10 planned human checks, reported as coverage rather than a compliance percentage
Comparison basis: Same pages, profile and scanner signature
Known boundary: Authenticated payment and back-office screens excluded

Prioritised findings

Findings remain tied to their affected scope, current status and accountable owner. The table is a short sample from the fictional pack.

Sample accessibility findings
ID	Impact	Finding	Scope	Status	Owner
BT-104	Serious	Form controls need accessible names	Account registration	Open	Digital delivery team
BT-099	Moderate	Heading order skips a level	Service information	Retest due	Content team
BT-087	Serious	Keyboard focus was obscured by the sticky header	Apply online	Resolved	Frontend team

Human verification

Passed

Keyboard navigation

Registration and help journeys completed without a pointer. Focus order was logical after BT-087 was retested.

Recorded by Example Tester · 2 September 2026

Needs evidence

Screen-reader errors

Error identification was checked, but the recovery path has not yet been verified with the supported screen-reader matrix.

Owner: Assurance lead · Due 10 September 2026

Governance and next work

Accessibility statement: Reviewed 28 August 2026; next review due 28 November 2026
Contact route: Documented and tested
Known limitations: Payment journey and PDF correspondence need separate evaluation
Next decision: Complete the two missing human checks before making any conformance statement

Checksum and correlation

The companion JSON demonstrates the machine-readable structure used to correlate the report scope, methods, run, pages and evidence records. Its SHA-256 checksum covers the compact UTF-8 JSON representation with the integrity property removed and can help detect accidental changes.

This checksum is not a digital signature. It can be recomputed after editing and does not prove who created the pack or that it is authentic.

SHA-256: 0a56ad2c695e36ddfd2c275b98c74876a09b8e0554d312a9b097f019b0fb7641

Run: example-run-2026-09-03 · Schema: barriertrace.evidence-pack/1.0

Use your own evidence

See what this could look like for your service.

Request a pilot or POC