Audits & reports
Understand an accessibility report
Read findings, evidence, review status, and next steps without mistaking a sample for a guarantee.
Start with scope and review status
Check the website, report date, sampled pages, coverage limits, and whether the report is preliminary or engineer-reviewed. Public-page source checks identify potential issues and gaps; they do not independently complete every keyboard, contrast, transaction, media, screen-reader, or legal test.
Read a finding
- Affected page or element: where the potential barrier was found.
- Visitor impact: why it may make a task difficult.
- Severity or priority: where to focus attention within the report’s method.
- Technical reference: the relevant accessibility criterion or guidance.
- Repair and verification: suggested work and how to check the result.
Interpret visual indicators
A red cross means an item needs attention or further testing. A blue check records a pass within the tested scope. Neither symbol establishes the accessibility of the entire website. “Not tested,” missing evidence, or a coverage gap should remain visible in your improvement plan.
Separate findings from legal conclusions
An automated finding is not automatically a legal violation, and a clean sample is not proof of complete compliance. The report’s accessibility action priority is not a probability of being sued. Business-specific legal questions need qualified advice. ADAR engineering reports do not act as law-firm opinions.
Turn findings into work
- Identify high-impact visitor tasks and the most important barriers.
- Confirm which findings need manual reproduction.
- Assign repairs to your developer or agree them with Managed support.
- Record the change and retest the affected journey.
- Keep the dated evidence and remaining limitations with your report history.