No. A VPAT or ACR is not required for ADA compliance. The ADA does not reference VPATs, ACRs, or any specific accessibility documentation format. ADA compliance for digital assets is measured against accessibility outcomes, with WCAG 2.1 AA serving as the practical standard courts and regulators point to. A VPAT is a procurement document used to communicate how a product maps to accessibility standards. An ACR is the completed version of that document. Neither is mandated by the ADA. They serve a different purpose and a different audience.
| Question | Answer |
|---|---|
| Required for ADA compliance? | No. The ADA does not require a VPAT or ACR. |
| What the ADA expects | Accessible digital experiences, with WCAG 2.1 AA as the working standard. |
| Primary purpose of an ACR | Procurement disclosure for buyers evaluating a product’s accessibility. |
| When an ACR matters | Government, education, healthcare, and enterprise procurement. |
| What proves ADA readiness | An accessibility audit against WCAG 2.1 AA and remediation of identified issues. |
What the ADA Actually Requires
The ADA does not list documents. It sets an expectation that goods, services, and programs are accessible to people with disabilities. For websites, web apps, and mobile apps, that expectation has been interpreted through enforcement actions, settlements, and the recent ADA Title II web rule.
The working standard is WCAG 2.1 AA. That is what plaintiffs cite, what the Department of Justice references for Title II entities, and what most defense attorneys advise clients to meet. None of that involves a VPAT.
What a VPAT and ACR Actually Do
A VPAT (Voluntary Product Accessibility Template) is a structured form maintained by ITI. It is filled in to describe how a product conforms to a chosen standard such as WCAG, Section 508, or EN 301 549. Once completed, the document becomes an Accessibility Conformance Report, the ACR.
The audience for an ACR is a procurement team. A buyer, often a government agency, university, hospital system, or large enterprise, requests the ACR to evaluate whether the product meets their internal accessibility requirements before purchase. The document supports a buying decision. It does not satisfy the ADA on its own.
Why People Confuse VPATs With ADA Compliance
The confusion is understandable. ACRs reference WCAG. WCAG is the standard tied to ADA expectations. So the logic shortcuts to: produce an ACR, satisfy the ADA. That logic skips the part that actually matters.
An ACR describes a product’s accessibility status. If the product has issues, the ACR will say so. Producing the document does not fix anything. ADA risk reduction comes from the underlying accessibility work: a thorough audit, remediation of identified issues, and validation that fixes hold.
When Does an ACR Actually Matter?
An ACR matters when a buyer asks for one. That happens most often in:
Federal, state, and local government procurement. Higher education and K-12 vendor reviews. Healthcare systems evaluating SaaS contracts. Enterprise software purchases with accessibility requirements built into vendor questionnaires.
If your buyers are not asking, you likely do not need one. If your buyers are asking, an ACR backed by a real accessibility audit is the right path. An ACR written without an audit behind it tends to fall apart under scrutiny.
What Reduces ADA Risk Instead
For a website or app, ADA risk reduction follows a predictable pattern. Conduct an accessibility audit against WCAG 2.1 AA. Address the issues the audit identifies, starting with the items most likely to appear in demand letters. Publish an accessibility statement. Keep a record of the work.
None of that requires a VPAT. A VPAT is a separate track for a separate audience. The two can run in parallel when a company has both procurement pressure and ADA exposure, but one does not substitute for the other.
Frequently Asked Questions
Should I get a VPAT or focus on ADA compliance first?
If you have no procurement requests on the table, focus on ADA readiness. Conduct an audit against WCAG 2.1 AA and work through remediation. If procurement requests start arriving, an ACR can follow, and the audit work already done feeds directly into it.
Does an ACR protect me from a website accessibility lawsuit?
Not directly. An ACR is a disclosure document, not a legal shield. What helps in a lawsuit context is evidence of an accessible product: audit reports, remediation records, and ongoing accessibility work. An ACR can support that record, but it does not stand alone.
Is there any law that requires a VPAT?
No U.S. law requires a private company to produce a VPAT. Section 508 applies to federal agencies and how they procure technology, which often pushes vendors to provide ACRs, but the requirement sits with the buyer, not the seller. The ADA itself says nothing about VPATs.
What is the difference between a VPAT and an ACR?
A VPAT is the blank template. An ACR is the completed document produced after filling in the template based on accessibility evaluation results. People often say VPAT when they mean ACR. The deliverable a buyer receives is always an ACR.
Can I produce an ACR without an audit?
Technically yes, practically no. An ACR written without evaluation behind it is a guess. Buyers who know what to look for will catch it, and the document can create more risk than it removes. A real ACR is built from real audit findings.
The shortest version: the ADA cares about whether your product is accessible. A VPAT cares about whether you can communicate that to a buyer. Both have a place. Only one is tied to legal exposure under the ADA.
Contact Kris for guidance on ADA compliance, VPATs, and ACRs.