VPAT vs ACR vs VPAC in one line: the VPAT is a free template published by ITI, an ACR is that template filled in with your product’s real conformance data, and VPAC is a label with no official standard behind it. Buyers evaluate the ACR, and they grade it as evidence of your engineering process. Get the document wrong and a deal can die in the final week, as one SaaS founder I work with learned on a $180,000 state contract after submitting a 2022 PDF labeled “VPAT” and never hearing back.
What Is the Difference Between a VPAT, an ACR, and a VPAC?
The first problem is that vendors treat these acronyms as interchangeable. Buyers do not. If you sell software to federal agencies, state governments, higher education, or enterprise companies with accessibility procurement clauses, you need to know the difference cold.
Here is the plain-language breakdown:
| Term | What it is | Who creates it | Who consumes it |
|---|---|---|---|
| VPAT | A free template published by the Information Technology Industry Council (ITI) | ITI, versioned (current: 2.5Rev, April 2025) | Nobody directly. It is the blank form |
| ACR | A completed VPAT. Your product’s conformance report filled into that template | The vendor, ideally after real testing | Procurement officers, accessibility subject matter experts, evaluators |
| VPAC | Not an official standard. A label used for proposed “process-based” conformance models | No standards body owns it | Nobody, yet |
The shorthand that saves you in a sales call: the VPAT is the form, the ACR is the filled-out form, and VPAC is a term you will hear in procurement meetings that has no official document behind it.
That third row matters more than most vendors realize, because a growing number of AI-generated and SEO-driven guides describe VPAC as if it were a published W3C draft replacing the VPAT. It is not. There is no W3C specification, no working draft, and no ITI announcement under the name VPAC. If a buyer asks about your “VPAC readiness,” the correct answer is to ask what document they are referencing. Half the time they read the same bad guide you did. The other half they mean something real: the move toward process-based conformance evidence, which I cover below.
The confusion costs real money. In my remediation work, roughly 1 in 3 vendors I audit has handed a buyer a document labeled VPAT that is actually a marketing one-pager with checkboxes. Evaluators spot this in seconds and it reads as either incompetence or evasion. Both kill deals. If you want the buyer’s side of that exchange first, our guide to the VPATs and ACRs procurement teams actually evaluate covers what reviewers screen for before you write a single row.
What Are VPAT Standards?
The Voluntary Product Accessibility Template has existed since 2001, created by ITI so vendors could report how their products conform to Section 508 of the Rehabilitation Act. It stayed roughly stable for two decades, then ITI began shipping yearly revisions to track the WCAG 2.x updates and the refreshed Section 508 standards, which incorporate WCAG 2.0 Level AA by reference under the revised Section 508 Standards published by the U.S. Access Board.
The current release, VPAT 2.5Rev (April 2025), comes in four editions. Pick by market, because the edition decides which WCAG version your rows are built on:
- WCAG edition: WCAG 2.2. Use for private-sector and general reporting.
- Revised 508 edition: WCAG 2.0 mapped to Section 508. Use for US federal agencies.
- EN 301 549 edition: WCAG 2.1 mapped to the European standard. Use for EU public sector.
- INT edition: all three combined. Use if you sell across markets.
The WCAG 2.2 alignment in the current edition matters for two reasons. WCAG 2.2 added criteria buyers now ask about, including 2.4.11 Focus Not Obscured (Minimum) and 3.3.7 Redundant Entry, and it retired 4.1.1 Parsing, which axe had flagged for years. An ACR built on a 2.3-era template misses all of that. Federal buyers’ own guidance walks vendors through the process at Section508.gov’s ACR guide, which is worth reading before you write a single row.
You can download the official template free from ITI’s VPAT page. Never pay a third party for the blank template. Anyone selling you the template itself is selling a free Word file.

Is an ACR the Same as a VPAT?
The Accessibility Conformance Report is the document with your company name on it. Each row of the VPAT template maps to a success criterion in WCAG 2.2, and you record one of four conformance levels:
- Supports: the criterion is fully met with no known defects
- Partially Supports: some functionality does not meet the criterion
- Does Not Support: the criterion fails
- Not Applicable: the criterion does not apply to your product
Two failure modes show up constantly in ACRs I review:
- Everything marked “Supports.” If your web app has any interactive widgets, there are almost certainly open defects against 4.1.2 (Name, Role, Value) or 1.4.11 (Non-text Contrast). A 100% Supports report for a complex SaaS product is a red flag to any accessibility SME, and evaluators grade your credibility accordingly.
- Wrong success criteria listed. I once reviewed an ACR where the vendor claimed support for 1.4.3 Contrast Minimum with a note saying “we use brand colors.” Contrast is measured, not declared. WCAG defines minimum ratios: 4.5:1 for normal text, 3:1 for large text. You verify with a tool like axe DevTools (free browser extension) or WAVE, record the actual result, and move on.
An honest ACR with two Partially Supports entries and clear remediation dates beats a suspiciously perfect one every time. Buyers’ accessibility teams know WCAG is hard. They are auditing your honesty as much as your code.
If your product has a public website component, our guide on web accessibility under WCAG walks through the criteria most commonly cited in ACR rows, and the testing work behind each one.
What Is Actually Replacing the Snapshot ACR
Here is what most guides get wrong about the “post-VPAT” future: they invent a named standard. The real shift has no catchy acronym yet, and it comes from two directions.
WCAG 3.0 changes the conformance model itself. The W3C’s draft successor standard moves away from pass/fail success criteria toward scored outcomes, and its conformance section explicitly targets the snapshot-report problem: a one-time ACR says nothing about the release you shipped last Tuesday. If WCAG 3.0 lands on its current trajectory (normative text targeted around 2029), procurement language will follow it, because federal and EU policy tracks W3C standards by reference.
Europe already forces process thinking. The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025. It covers e-commerce, banking, e-books, and more, and EU member states enforce it through conformity assessment referencing EN 301 549. Unlike a US solicitation that accepts a self-reported ACR, EAA conformity expects evidence a product stayed conformant, not a PDF from two years ago.
The practical position: VPAT 2.5Rev ACRs are what solicitations ask for now, and process evidence is what sophisticated buyers will grade next. You can read the draft conformance direction in the W3C’s WCAG 3.0 working draft, and it costs nothing to start aligning your development process now, since those requirements (automated accessibility testing in the pipeline, defect tracking) are good engineering practice regardless.
What Buyers Actually Evaluate in Your ACR
Having sat on both sides of procurement reviews, here is what evaluators actually do with your ACR:
- Check the date and version. Older than 12 months or using a VPAT 2.3 template when 2.5Rev exists signals neglect.
- Skim for honest failures. Experienced reviewers read the Remarks sections hunting for known defects. Finding none is worse than finding real ones.
- Spot test 3 to 5 criteria. Keyboard-only operation (2.1.1), form labels (3.3.2), focus visibility (2.4.7) are the usual picks. If your claim of Supports fails their five-minute test, your entire report is discredited.
- Check remediation commitments. Partially Supports rows should name a target release and owner. Vague language like “on our roadmap” reads as a brush-off.
Legal pressure keeps this scrutiny high. Website accessibility lawsuits filed in US federal court hit 3,117 in 2025, up 27% from 2,452 in 2024, per Seyfarth Shaw’s ADA Title III filings analysis. Government buyers know they inherit vendor risk. Our analysis of ADA website lawsuit trends covers why procurement teams treat a weak ACR as a liability transfer, not a formality.

A Checklist for Producing Your First Credible ACR
If you are a small vendor staring at a solicitation deadline, this is the sequence I run with clients. Budget 40 to 120 hours depending on product complexity. The document structure and the auditor rejections to avoid are laid out in our VPAT and ACR writing guide.
- Download the free VPAT 2.5Rev template from ITI. Pick the edition that matches your market: INT for international coverage, Revised 508 for US federal.
- Run an automated scan first. axe DevTools (free tier) or WAVE will catch 30 to 50% of failures: missing labels, contrast errors, empty buttons. Log every finding by success criterion, then cover the manual checks scanners miss with Google’s web.dev accessibility material.
- Do manual keyboard and screen reader testing. NVDA (free, Windows) plus Chrome is the evaluator’s most common combo. Tab through every core workflow. If a modal traps focus or a dropdown does not open with the keyboard, that is a 2.1.1 or 2.4.3 failure in your report.
- Write honest conformance levels. Mark Partially Supports where defects exist, and put the defect list in the Remarks column with ticket references.
- Add a contact and a date on page one. Name a person. Evaluators email questions to that person.
- Review with an accessibility SME before submission if the contract is worth more than about $50K. A two-day external review costs $2,000 to $4,000 with firms like TPGi or Deque (consulting rates typically $200 to $300 per hour) and catches the credibility-killing errors.
- Reissue with every major release. Set a calendar trigger. A stale ACR is worse than a late one.
Process Practices Worth Adopting Now
Whatever name the post-ACR era ends up with, adopting process-based practices strengthens your ACR today and shortens future audits:
- Wire axe-core into CI. The axe-core npm package (free, open source) runs in Playwright or Cypress. Failing the build on new critical violations costs one engineer about two days of setup and prevents regression of anything you already fixed.
- Publish an accessibility statement page. State current conformance status, known issues with workarounds, and a feedback channel. Buyers check for this.
- Track accessibility defects in your normal backlog with a dedicated label, so remediation dates in your ACR are verifiable rather than aspirational.
There is a real ROI case here. In my client work, vendors with credible ACRs close government and enterprise deals 30 to 60 days faster than vendors scrambling to produce paperwork mid-procurement, because the accessibility review stops being the long pole. Pairing this discipline with the measurement approach in our framework for measuring AI ROI in small businesses gives you a clean way to attribute revenue to accessibility investment when your CFO asks why engineering time went to WCAG remediation.

Common Mistakes That Kill Deals
Beyond the two ACR failure modes above, these come up in almost every procurement post-mortem I am brought into:
- Sending a VPAT template with no data filled in. It happens more than you would believe. The evaluator sees a blank form and moves on.
- Claiming Section 508 certification. There is no such certification. Section 508 is a regulation, not a certifying body. Any claim of official 508 certification marks your document as written by someone who has not done the work.
- Ignoring EN 301 549 and the EAA when selling to universities or EU buyers. Many state systems and public universities outside the US reference EN 301 549, and the European Accessibility Act now makes accessibility a legal requirement for consumer-facing digital services across the EU. The INT edition of VPAT 2.5Rev covers EN 301 549 in the same document.
- Treating the ACR as a legal shield. An ACR that materially misrepresents conformance exposes you to False Claims Act risk in federal procurement, with treble damages. Honesty is not just ethical here, it is cheaper.
The Bottom Line on Cost
Producing your first credible ACR costs between $5,000 and $15,000 in engineering and testing time for a typical SMB SaaS product, less if your codebase is clean. Maintaining it costs under $2,000 per year. Losing one mid-sized government contract because of a sloppy document costs far more. I have watched it happen more than once.

What Most Guides Get Wrong
Most guides on this topic get the vendor’s job backwards. They frame the ACR as a documentation task, something a technical writer assembles the week a solicitation drops. In practice, evaluators grade the report as evidence of your engineering process, which means the document cannot be written faster than the testing behind it. A second common error: guides tell vendors to mark everything Supports because “Partially Supports looks bad.” My review experience says the opposite. A report with two dated Partially Supports rows reads as tested, while a perfect report reads as copy-pasted, and accessibility SMEs spot the difference within minutes. Guides also overstate the cost of compliance tooling, telling readers to budget for enterprise audit suites when axe DevTools, NVDA, and WAVE cover most of what a first ACR needs for free. Fourth, they treat the VPAT version as trivia. Using a 2.3-era template when 2.5Rev exists is one of the first things a federal evaluator checks, because it signals nobody owns accessibility at your company. Finally, most guides ignore the timing problem entirely: they never tell you to set a calendar trigger tied to your release cycle, so the report is stale the moment the next deploy ships. The vendors who lose deals rarely fail on accessibility. They fail on freshness, honesty, and ownership.
Conclusion
VPAT is the free template, ACR is your filled-in conformance report, and VPAC is a label without a standard behind it, so do not let a procurement meeting ambush you with a fictional document. Right now, solicitations want a current, honest VPAT 2.5Rev ACR with real test results, named contacts, and dated remediation commitments. Write the honest version. Evaluators reward it, buyers trust it, and it is the only version that survives a spot check. Then put process practices in place, because WCAG 3.0’s conformance model and the European Accessibility Act both point the same direction: proof that conformance is ongoing, not a PDF. When those requirements harden, your next procurement cycle is paperwork instead of panic.



