Accessibility audit report example: what a good one looks like
An accessibility audit report example worth copying lists each error once, names the page it is on, the WCAG rule it breaks, how bad it is, how to see it and exactly how to fix it. A report that only prints a score or a long list of scanner codes is not an audit. This guide gives you a filled sample, a free template to copy, and a checklist for judging any report before you pay for the fixes. We are not lawyers; this is not legal advice.
What is an accessibility audit report?
An accessibility audit is a test of your website against a written standard, most often WCAG 2.1 or 2.2 Level AA from the W3C. The report is the paper you get at the end. It is what a developer works from, what you show a client or a lawyer who asks what you have done, and what you compare against after the fixes to prove the errors are gone. If you want the price side first, see website accessibility audit cost and ADA website compliance cost.
Reports come from three kinds of testing. Automated tools such as axe, WAVE and Lighthouse find what code alone can show: missing alt attributes, low contrast, empty buttons, unlabeled fields. Deque, the company behind axe, has said automated tools find roughly a third to over half of the issues on a typical page, depending on how you count. The rest needs a person using the keyboard, a screen reader and zoom. A full audit report mixes both and says which finding came from which.
The parts of an accessibility audit report
Whatever the firm, a useful report has the same bones. If one of these is missing, ask for it.
- Scope: which pages and flows were tested (home, contact form, checkout), the date, the browsers and the assistive tools used.
- Standard: the version and level (for example WCAG 2.1 AA). A report that says "ADA compliant" without a standard has not said what it tested against.
- Summary: how many errors, how many are severe, and which two or three patterns cause most of them. One paragraph a non-technical owner can read.
- Findings: one row per problem with the page, the WCAG criterion, severity, steps to see it, and the fix.
- What was not tested: PDFs, embedded booking tools, video, anything behind a login.
- A retest plan: when the errors are checked again and how a pass is shown.
An accessibility audit report example with real findings
The sample below is invented for teaching: a small dental office site with four tested pages. The findings are the kinds that scans keep finding on small business sites. Severity here means the effect on a visitor: blocker stops a task, serious makes it hard, minor is an annoyance.
Report header
| Item | Entry |
|---|---|
| Site | example-dental.test (WordPress, a paid theme) |
| Pages tested | Home, Services, Book online, Contact |
| Standard | WCAG 2.1 Level AA |
| Method | axe DevTools on every page, then keyboard-only and screen reader walk-through of the booking flow, plus 200% zoom |
| Date | 2026-11-10 |
| Summary | 14 errors on 4 pages. 2 blockers, both in the booking form. Most errors come from one cause: the theme's button style |
Findings
| # | Where | Problem | WCAG | Severity | Fix |
|---|---|---|---|---|---|
| 1 | Book online, date field | The date picker cannot be reached or used with the keyboard. A visitor who does not use a mouse cannot book. | 2.1.1 Keyboard | Blocker | Add a plain text date field next to the picker, or replace the picker with one that opens on Enter and moves with arrow keys. |
| 2 | Book online, all fields | Fields use placeholder text instead of labels. The hint vanishes when you type and a screen reader says only "edit text". | 1.3.1, 3.3.2 | Blocker | Add a visible label tied to each field with for and id. Keep placeholders only as examples. |
| 3 | All pages, buttons | White text on a light teal button measures 2.6 to 1. The rule needs 4.5 to 1 for normal text. | 1.4.3 Contrast | Serious | Darken the button colour in the theme settings to a teal around #0b6e6e, which measures above 5 to 1. |
| 4 | Home, hero photo | The photo of the front desk has no alt text, so a screen reader reads the file name. | 1.1.1 Non-text content | Serious | Add alt text: "Reception desk at Example Dental with the front-office team". |
| 5 | Services, three links | Three links all read "Learn more", so a list of links gives no clue where each goes. | 2.4.4 Link purpose | Serious | Rename to "Learn more about whitening", "...about braces", "...about check-ups". |
| 6 | Home and Services | Headings jump from h1 to h4 because the h4 style looked right. | 1.3.1 | Minor | Use h2 for sections and style it in CSS instead of changing the tag. |
| 7 | All pages | No visible outline when a link or button gets keyboard focus. | 2.4.7 Focus visible | Serious | Remove the theme rule that sets outline: none, or add a 3px outline in a dark colour. |
| 8 | Contact, map | The embedded map has no title, so it is announced as "frame". | 4.1.2 Name, role, value | Minor | Add title="Map to the Example Dental office" to the iframe. |
The real report would continue to row 14 in the same shape. Notice what makes it usable: each fix is something a person with the theme editor, or a developer on a one-hour ticket, can do without asking questions. Notice, too, that the first two rows are the ones a lawsuit would be built on, since they stop the customer from doing the one thing the site is for.
Accessibility audit report template you can copy
Copy this into a spreadsheet. One row per error, one sheet per site. It is free to use. Fill the first five columns when you test and the last two when you fix.
| Column | What goes in it | Example |
|---|---|---|
| ID | A running number | 7 |
| Page and place | URL and the part of the page | /contact, map under the form |
| What happens | One plain sentence on what a visitor sees or hears | Screen reader says "frame" with no name |
| WCAG criterion | Number and name from the W3C quick reference | 4.1.2 Name, role, value |
| Severity | Blocker, serious or minor, by what the visitor can no longer do | Minor |
| Fix | The exact change, in words a developer can follow | Add a title attribute to the iframe |
| Status and retest date | Open, fixed, retested, and the date | Fixed 2026-11-14, retested 2026-11-21 |
To fill the sheet, run a free scanner on each page (our Chrome extension guide shows how), then work through the keyboard and zoom checks in the ADA compliant website checklist. The WCAG 2.1 AA checklist PDF gives a printable sheet for the manual part.
How to tell a good audit report from a scan printout
Many cheap "audits" are a scanner's output with a cover page. That is not worthless, but it is a scan, and it should be priced like one. Use these tests.
| Look for | A real audit | A scan printout |
|---|---|---|
| Pages | A named list of pages and flows | One URL or "your site" |
| Manual testing | Says keyboard and screen reader checks were run, and which | Does not mention it |
| Fix text | Specific to your platform and theme | Generic ("add alt text to images") |
| Standard | Version and level written out | "ADA compliant" or a score out of 100 |
| Limits | Lists what was not tested | Claims to find everything |
| Retest | Offers to check again after fixes | One-off PDF |
A score out of 100 on its own tells you little. Two sites can each score 85 and one of them can still have a form nobody can submit. Ask what the blockers are, not what the score is.
What is an accessibility audit, and how is it different from a scan?
A scan is a program reading your page's code and flagging rules it can check. It takes seconds and costs nothing. An audit adds a person who tries to use the site the way people with disabilities do, and then writes down what failed and why. A scan can say a field has no label. Only a person can say whether the alt text on the front desk photo describes it, or whether the booking flow still makes sense with a screen reader.
Common mistakes in audit reports
- One entry per instance. A hundred product photos with no alt text is one pattern with a hundred places. A good report groups them and says how many.
- Fixes that cannot be done. "Rebuild the navigation" is not a fix for a small owner. Ask for the smallest change that clears the error.
- Everything marked urgent. If all fourteen findings are blockers, severity was not judged.
- No retest. A report with no retest leaves you guessing whether the fixes worked.
- Promising compliance. No report can prove a site meets every requirement, and no court certifies one. Watch for wording that says it can. The US Federal Trade Commission's January 2025 order against accessiBe was about claims of that kind.
What to do with the report once you have it
- Fix the blockers first: forms, checkout, booking, menus that cannot be used by keyboard.
- Next the serious items that appear on every page, since one theme change clears many rows.
- Hand the list to whoever edits your site. For WordPress, see fixing the theme vs adding a plugin. A plugin or widget alone will not clear most rows in the sample above; our accessiBe alternatives guide explains why.
- Retest the same pages and keep the dated before and after copies.
- Publish an honest accessibility statement that names what you fixed and how to reach you.
Frequently asked questions
What should an accessibility audit report include?
Scope, the standard tested (such as WCAG 2.1 AA), a plain summary, one row per finding with page, rule, severity and fix, what was not tested, and a retest plan.
Is there a free accessibility audit report template?
Yes. The seven-column table above works in any spreadsheet. The W3C also publishes an evaluation methodology, WCAG-EM, with a report tool you can use free.
How long is a typical report?
For a small site of four to ten pages, expect roughly 10 to 40 findings, grouped by pattern. A report running to hundreds of rows for a ten-page site is usually raw scanner output.
Can an automated tool produce the whole report?
It can produce the first half. Scanners cannot judge whether alt text is accurate, whether the reading order makes sense or whether a flow works with a screen reader.
Does a clean report mean my site is ADA compliant?
It means the pages tested met the standard on the day tested. The law has no certificate. Keep the report and the retest as a record of effort, and retest after big changes.
How much does an audit report cost?
From free for a scan to roughly $1,250–$2,750 for an expert manual audit, with small-site options in between. Our audit cost guide lists published prices.
Sources
- W3C, Web Content Accessibility Guidelines 2.1 and the Quick Reference.
- W3C Web Accessibility Initiative, Website Accessibility Conformance Evaluation Methodology (WCAG-EM) and its report tool.
- Deque Systems, statements on how much of WCAG automated testing can find.
- accessible.org, published audit price range (read 2026-11-03).
- FTC, order against accessiBe, January 2025.
Related: ADA website compliance checker.