How a VPAT Becomes a Completed ACR

A VPAT becomes a completed ACR when you fill the template in with accurate conformance findings from an audit. The empty template is the VPAT; the finished report is the ACR. Same document, two states.

Think of a VPAT as a blank report card that a teacher fills in. Until someone evaluates the product and writes down the results, it says nothing about your accessibility.

The difference between the two, in plain terms

VPAT stands for Voluntary Product Accessibility Template. It’s the shell, published by the ITI, that lays out the structure for reporting conformance.

ACR stands for Accessibility Conformance Report. That’s what you have once the shell is populated with real results.

So the words describe the same file at different points. Before findings, it’s a VPAT. After findings, it’s an ACR.

What has to happen in between

The step that converts one into the other is the evaluation. You cannot fill in conformance levels honestly without testing the product against the relevant success criteria first.

Turning a VPAT into a credible ACR takes a defined sequence of steps:

1. Pick the right VPAT edition (WCAG, EU EN 301 549, Section 508, or International) for your buyers.
2. Set the target conformance level, defaulting to WCAG 2.1 Level AA unless a contract says otherwise.
3. Conduct an audit of the product against every applicable success criterion.
4. Record a conformance level for each criterion: Supports, Partially Supports, Does Not Support, or Not Applicable.
5. Write the remarks and explanations that justify each rating with specifics.
6. Review the finished report for accuracy before it goes to a buyer.

Skip the audit and you don’t have an ACR. You have a guess typed into a template.

Why the remarks column decides everything

If there’s nothing in the remarks and explanations column, your ACR is near worthless. A buyer reading a wall of “Supports” with no evidence has no reason to trust it.

Good remarks name the element, describe the behavior, and explain the rating. That’s the difference between a snapshot and a rubber stamp.

Here is what each conformance level should communicate to a buyer:

• Supports: the criterion is met across the product, with any minor context noted.
• Partially Supports: the criterion is met in some places and not others, with the exceptions spelled out.
• Does Not Support: the criterion is not met, described honestly rather than hidden.
• Not Applicable: the criterion doesn’t apply to this product, with a reason given.

VPAT versus completed ACR at a glance

Attribute	VPAT (template)	ACR (finished report)
State	Blank structure	Populated with findings
Requires an audit	No	Yes
Conformance levels	Empty	Filled for every criterion
Remarks column	Empty	Detailed and specific
Useful to buyers	No	Yes, when accurate

Accuracy is the whole point

An ACR only brings value if it’s accurate. An ACR is not certification, and it doesn’t guarantee anything on its own. It reports what an evaluation found.

Because of that, the audit behind it matters more than the formatting. We only sell fully manual accessibility audits, since automated scans catch roughly a quarter of issues and leave the rest for a human to catch.

If you want to understand how the underlying evaluation should be conducted before you commit, our writing on what separates a thorough review from a shallow one covers the ground well, as does our explanation of how the finished report earns a buyer’s trust.

Getting yours done

Do you need a VPAT turned into an ACR? Contact us and we’ll send a quick quote right away.

We deliver for most clients within 1 to 2 weeks after they reach out, at competitive pricing. send a message and we’ll respond ASAP, usually within a few hours.