Accessibility Compliance Evidence and Reporting

Make the tested boundary explicit

Record product version, environment, tested templates, workflows, documents and relevant devices. The report should explain what was examined and what was excluded. A result without scope can be mistaken for coverage of the whole service.

Write reproducible findings

Include the affected page/state, user impact, exact steps, criterion reference, test method and evidence location. Separate confirmed failures from review items that need contextual judgement. A screenshot should be accompanied by enough information to reproduce the interaction.

Worked modal finding

The evaluator opens a settings modal with keyboard and observes focus moving behind it. Record the browser and assistive-technology context where tested, the steps and the responsible component. After a fix, repeat the relevant sequence and retain both the original finding and the retest outcome.

Evidence chain and ownership

Link findings to remediation owners and tickets. Record dates, code/build references and the retest assessor. Preserve remaining exceptions with reasons and next steps. A closed ticket without a verified retest is weaker evidence than a reproducible before-and-after result.

Prepare an honest summary

Summarise scope, methods, unresolved barriers and completed work without a fake pass rate or certification claim. Use the audit checklist and statement generator to communicate specific limitations. Share the evidence through approved storage, with appropriate access to any sensitive service information.