Accessibility audit report template (free Excel download)
A findings sheet for recording accessibility issues, rating them against WCAG 2.2 AA, and tracking fixes until they're confirmed. It's the same structure I use for real audits, with a status column and a summary that counts itself.
Last updated November 1, 2026
What's in the template
- How to use: six steps, severity ratings, conformance levels and a worked example of a finding.
- Findings: room for 200 issues, with drop-down lists so ratings stay consistent, a frozen header and filters you can use to sort by page, severity or status.
- Summary: counts of findings by severity, status and conformance level, plus the share fixed, calculated by formulas.
The columns, explained
| Column | What to write |
|---|---|
| ID | A short reference such as A-01, so developers and testers can discuss each issue. |
| Page or URL | Where the issue appears. Use the template or page name for issues that repeat. |
| Issue | A short title that states the problem. |
| Screenshot | A screenshot or the element's selector, so the issue can be found quickly. |
| Actual Result | What happens now, and who is affected. |
| Expected Result / Remediation | What should happen, with recommended steps and a code example. |
| Severity | High, Medium or Low (see below). |
| WCAG Conformance Level | A, AA or Best practice. |
| WCAG Success Criteria | The criterion number and name, such as 2.1.1 Keyboard. |
| EN 301 549 Clause (optional) | For EU work. For web content, clause 9 mirrors WCAG, so WCAG 2.1.1 becomes 9.2.1.1. |
| Comments | Who is affected and how to confirm the fix. |
| Status and Retest Date | Open, Fixed, Partly fixed or Not fixed, and when you re-checked. |
Severity ratings
- High: prevents or seriously hinders someone from completing a key task, such as buying.
- Medium: causes difficulty or confusion, but a workaround exists.
- Low: a small inconvenience or best-practice improvement.
How to use it
- Test each page and journey against WCAG 2.2 AA with a keyboard and a screen reader. Use automated scans as a starting point.
- Add one row per issue, with an ID.
- Write the actual and expected results, with a code-level fix.
- Pick the severity, level and criterion from the drop-down lists.
- Update the status as fixes are made, and add a retest date.
- Check the Summary sheet to see progress.
What a good finding looks like
Issue: Cart confirmation message is not announced (Product page, High, Level AA, WCAG 4.1.3).
Actual result: After "Add to cart" is activated, a notice appears on screen but isn't announced by screen readers. As a result, people using screen readers can't tell whether the item was added.
Expected result / remediation: Status messages should be announced without moving focus. Add an empty element with role="status" to the page when it loads, then write the confirmation text into it after the item is added.
See 13 findings written this way in the sample audit report.
Common questions
What should an accessibility audit report include?
For each issue, the page, a screenshot, what happens now, what should happen, a severity rating, the WCAG criterion and level, and a code-level fix. It should also state the standard tested, the pages in scope and the assistive technologies used.
What is the difference between an audit report and a VPAT or ACR?
An audit report is a detailed list of problems with fixes, written for your developers. A VPAT, completed as an ACR, summarizes how well a product conforms to a standard, written for buyers. The audit is the evidence the ACR should be based on. Read the VPAT and ACR guide.
Which standard should I audit against?
For a general web audit, WCAG 2.2 Level A and AA is a useful current baseline. Confirm the version, pages and complete processes required by your contract or applicable framework. Revised Section 508 incorporates WCAG 2.0 A and AA and includes additional ICT requirements; EN 301 549 also extends beyond web content. Compare the frameworks.
Can I use this template for client work?
Yes, for your own audits and internal tracking. A template helps you record issues consistently, but it doesn't replace manual testing with a keyboard and screen readers.
Rather have someone test your site?
I'll test your homepage by hand and send you a free one-page report on the top 3 barriers, with a plain-English fix for each. Or see what a full audit costs.
Sources and standards
Sources reviewed November 1, 2026. Requirements depend on the applicable standard, product and jurisdiction.