Conformance report Template

# Accessibility conformance report: [name of the product], version [version]

> Template version 1.0, 2026-10-07, from https://auricartisan.com/templates/conformance-report/
> Licence: CC0 1.0 (https://creativecommons.org/publicdomain/zero/1.0/). Copy it, change it and use it for anything; no credit needed.
> Replace everything in [square brackets], then delete this note. The result for each criterion goes in conformance-report.csv.
> This is not the VPAT. VPAT is a registered service mark of the Information Technology Industry Council (ITI). If a buyer asks for a VPAT, fill in ITI's own template instead: https://www.itic.org/policy/accessibility/vpat

| Report | |
|---|---|
| Product | [Name of the product] |
| Version evaluated | [Version, release or build, and its date] |
| Report date | [YYYY-MM-DD] |
| Report version | [1.0] |
| Standard | Web Content Accessibility Guidelines (WCAG) 2.2 |
| Level | A and AA |
| Prepared by | [Name, role, organisation] |

Criterion,Name,Level,Conformance level,Remarks and explanations
1.1.1,Non-text Content,A,,
1.2.1,Audio-only and Video-only (Prerecorded),A,,
1.2.2,Captions (Prerecorded),A,,
1.2.3,Audio Description or Media Alternative (Prerecorded),A,,

Licence: CC0 1.0 Universal, a public domain dedication. Copy, change and use these files for anything, including paid work, without asking or giving credit. The files are plain ASCII text in English, so they open the same everywhere.

1. Product and version. The product's name and the exact version you evaluated, because the next release may differ.
2. Date and standard. When the report was written, and what it reports against: WCAG 2.2, Level A and AA.
3. Evaluation methods. Who evaluated it and when, the sample of pages and screens, the tools, and the browsers and assistive technology used.
4. Contact. Who a buyer can ask about the report, and how.
5. Summary. How many criteria have each conformance level, at Level A and AA, so a reader sees the picture before the detail.
6. Terms. What each of the five conformance levels means, and how you chose between them.
7. Results. One row per criterion: its conformance level, and remarks that say what does not work, where, and when it will be fixed.
8. Limits. That the report describes one version on the dates tested, is not a conformance claim and is not legal advice.

Choosing between Partially Supports and Does Not Support is a judgement of how much fails. Say on the cover how you decided, and use the same rule in every row.

1. Evaluate first. Test the exact version you will report on, against every criterion, with a sample that represents the whole product. Use the audit report template
2. Give every row a level. Use the five terms only, and write remarks a buyer can act on: what fails, where, and the way round it. Every success criterion, with tests
3. Fill in the cover. Count each level for the summary, and name the version, the dates, the methods and a contact.
4. Have it checked. Ask someone who did not do the evaluation to try a few rows against the product.
5. Keep it current. Issue a new report for each major release, and whenever a fix changes a row.

• Accessibility audit reportA report with a findings register, severity by user impact, results by criterion and retests, and a workbench to fill it in.
• Accessibility statementA public page that says how accessible the site is, what is not, and how to get help.
• WCAG 2.2Every success criterion, with live demos and tests
• Accessibility lawWhat twenty jurisdictions ask for, and when