Guide
Generating a conformance report
Mend can turn the audits already on your dashboard into a downloadable Accessibility Conformance Report. This is what goes into it, how each row is decided, and — just as importantly — what the document is careful not to claim.
Last reviewed: 8 August 2026
Before this page
If you are not sure what a VPAT or an ACR is, who asks for one, or what one is used for, read VPATs and ACRs first. That guide covers the document; this one covers the generator.
What the report is built from
Generate one from the Reports page. It uses the audits you already have — there is no separate scan. For every URL on your account it takes the most recent run, and that set of pages is the report's evidence base.
This means the report is exactly as current and exactly as broad as your audit history. Auditing three pages of a fifty-page site produces a report about three pages, and it says so. If you have no audits at all, Mend declines to generate anything rather than producing a document full of passing rows backed by no evidence.
Each criterion is assessed against the WCAG 2.2 Level A and AA catalogue.
How each row is decided
For a given success criterion, Mend looks at which of your audited pages have findings against it:
- Findings on every audited page — Does Not Support.
- Findings on some pages — Partially Supports.
- Findings on no page — Supports.
Findings are listed worst impact first, then by how many places they affect, so the top of each section is what to fix first. The same data always produces the same document, which makes two reports generated a month apart directly comparable.
What “Supports” actually means here
This is the part to read before you send the document to anyone. In a Mend-generated report, “Supports” means automated checks found nothing — not that the criterion is met.
Those are very different claims. A large share of WCAG cannot be evaluated by a machine at all: whether alt text is accurate, whether a heading structure is meaningful, whether an error message is useful, whether a video's captions are correct. A scanner sees an alt attribute and stops there.
The generated document states this limitation itself, on the document, and that text is not optional or removable. It is there because an ACR is something you hand to a procurement team, and a report implying a machine certified your conformance would be misleading in a setting where people are relying on it.
Used honestly, the generated report is a strong starting point: it is accurate about what was tested, it is current, and it does the tedious mapping from findings to criteria for you. Completing it means a person reviewing the rows a scanner cannot answer. Nothing Mend produces removes that step, and the document does not pretend otherwise.
The download
You can preview the report on the site before downloading it. The download is a self-contained HTML file, named with the date it was generated. HTML rather than a PDF or a Word document deliberately: it opens anywhere, it can be printed to PDF in one step if that is what the recipient wants, and — for a document about accessibility — it is the format most likely to work with the tools its readers use.
The report names the product it describes. Left alone this defaults to the hostnames covered, so an untouched form still produces something that says what it is about.
Generating a report is read-only. It stores nothing, changes nothing, and can be run as often as you like.