AODA Accessibility Report
An AODA accessibility report turns testing results into an actionable record. It should be clear enough for executives to understand risk and detailed enough for developers, content teams and accessibility specialists to remediate issues.
Recommended report structure
- Executive summary.
- Organization and project scope.
- Pages, templates and workflows tested.
- Testing methodology and tools.
- Standards and criteria used.
- Detailed findings and evidence.
- Severity and user impact.
- Recommended remediation.
- Retest results.
- Limitations and assumptions.
AODA compliance reporting
Website audit reporting and statutory accessibility compliance reporting are different activities. A technical audit report documents accessibility findings; an AODA compliance report is a legal filing for organizations required to submit one. Do not present an audit report as a statutory filing.
Make reports useful
Avoid lists of scanner errors without context. Each finding should explain the affected component, the barrier, the user impact and a practical fix.
Frequently Asked Questions
What is included in an AODA accessibility report?
Typically scope, methodology, findings, evidence, applicable criteria, severity, remediation recommendations and retest status.
Is an accessibility report the same as an AODA filing?
No. A filing is submitted through the Ontario accessibility compliance reporting process when legally required. An audit report is a technical assessment document.
Can reports include screenshots?
Yes. Screenshots and code examples can make findings easier to reproduce and remediate when handled accessibly.
Need an accessibility assessment?
Discuss your website, web application, testing scope and reporting requirements with TechnoAccess.
Contact TechnoAccess