A VPAT or ACR is not required for ADA compliance, and having one does not make a website or product ADA compliant. The VPAT is a template, and the ACR is the completed report that documents how a digital product measures against accessibility standards like WCAG 2.1 AA, Section 508, or EN 301 549. ADA compliance is determined by whether the product is actually accessible, not by whether a conformance report exists. That said, an ACR backed by a thorough accessibility evaluation is strong documentation of accessibility work and is often requested during procurement.
| Question | Answer |
|---|---|
| Is a VPAT/ACR required for ADA compliance? | No. The ADA does not require a VPAT or ACR. |
| Does an ACR prove ADA compliance? | No. It documents WCAG conformance status, not legal compliance. |
| When is an ACR useful? | Procurement, government contracts, B2B sales, and demonstrating accessibility work. |
| What actually supports ADA compliance? | An accessibility evaluation and remediation against WCAG 2.1 AA or 2.2 AA. |
What a VPAT and ACR Actually Are
The Voluntary Product Accessibility Template (VPAT) is a standardized document created by the Information Technology Industry Council. It exists in four editions: WCAG, Section 508, EN 301 549, and INT. The WCAG edition is the most common for SaaS companies and digital products sold in the United States.
Once the VPAT is filled in with evaluation results, it becomes an Accessibility Conformance Report, or ACR. The ACR explains how each success criterion is supported, partially supported, does not support, or is not applicable.
An ACR is a disclosure document. It tells buyers and decision-makers what the current state of accessibility looks like for a specific product.
Is a VPAT or ACR Required by the ADA?
No. The Americans with Disabilities Act does not mention VPATs or ACRs. The law focuses on whether goods, services, and digital experiences are accessible to people with disabilities, not on whether a particular document exists.
Title III applies to private businesses operating places of public accommodation. Title II applies to state and local government entities, with web and mobile app content now expected to meet WCAG 2.1 AA under the updated rule. Neither title creates a VPAT requirement.
Federal procurement under Section 508 is a different matter. Federal agencies often request an ACR as part of their buying process, but that is a procurement requirement, not an ADA requirement.
Why People Confuse VPATs/ACRs with ADA Compliance
The confusion is understandable. ACRs reference WCAG, and WCAG is the technical standard most often cited in ADA website lawsuits. So an ACR looks like it should be the document that confirms ADA compliance.
It isn’t. An ACR reports the conformance status at the time of evaluation. If issues are listed as partially supports or does not support, the product still has accessibility issues, and those issues can still create legal exposure under the ADA.
An ACR with strong results (most criteria supporting) reflects real accessibility work. An ACR with many issues simply documents that the product is not yet accessible.
What Actually Supports ADA Compliance
The work that supports ADA compliance is the same work that produces a clean ACR: a thorough accessibility evaluation, followed by remediation, followed by validation. The ACR is the byproduct of that work, not the work itself.
An evaluation identifies issues against WCAG 2.1 AA or WCAG 2.2 AA. Scans only flag approximately 25% of issues, which is why a scan alone cannot stand in for an audit. Remediation addresses the identified issues. Validation confirms the fixes hold.
VPAT details are discussed further here.
This sequence is what reduces legal risk. The ACR can document the result, but the audit and remediation are what move the product toward accessibility.
When You Actually Need a VPAT/ACR
A VPAT/ACR is appropriate when buyers ask for one. The most common scenarios are selling software to federal, state, or local government; selling to enterprises with accessibility procurement policies; responding to RFPs that request an ACR; selling to higher education and healthcare buyers; and selling into European markets where EN 301 549 references apply.
If none of these apply, an ACR is optional. A consumer-facing website that does not sell to enterprise or government buyers generally has no reason to produce one. The same site still needs to be accessible under the ADA.
What an ACR Does Demonstrate
An ACR backed by a real audit demonstrates that an organization took accessibility seriously enough to evaluate the product against WCAG. That documentation can support a defensive posture if accessibility is ever questioned, especially when paired with an accessibility statement and ongoing remediation work.
It is not a certification. No one issues an official ADA certification, and any vendor claiming to certify ADA compliance is overstating what is possible. Accessibility is an ongoing effort, and ACRs are point-in-time reports.
Frequently Asked Questions
Should we get a VPAT/ACR if we want to reduce ADA lawsuit risk?
Get an audit first. The audit identifies the issues that create legal risk, and remediation reduces that risk. An ACR documents the result. If you only produce an ACR without doing the underlying work, you are publishing a list of accessibility issues with your product name on it.
Can an ACR be used as evidence in an ADA case?
Yes, in either direction. A clean ACR backed by a real audit can support a defense. An ACR full of partial and non-supporting criteria can be used against the organization. Documentation cuts both ways, which is why the audit and remediation work matter more than the report itself.
Does the ADA reference WCAG or VPATs?
The ADA itself does not name WCAG or VPATs in its original text. The updated ADA Title II rule from the Department of Justice does reference WCAG 2.1 AA for state and local government web and mobile content. Title III enforcement and litigation routinely use WCAG 2.1 AA as the practical standard, but a VPAT is not named as a requirement.
Which standard should our ACR use for U.S. ADA-related purposes?
The WCAG edition of the VPAT, evaluated against WCAG 2.1 AA, is the most common choice. WCAG 2.2 AA is increasingly requested for newer procurement cycles. Section 508 and EN 301 549 editions apply when federal procurement or European obligations are in scope.
Accessible.org produces ACRs that are backed by a fully manual audit, which is the foundation that makes the report meaningful.
To discuss a VPAT/ACR or an accessibility audit for your product, contact Accessible.org.
