Complete Guide to VPATs and ACRs for Accessibility

A VPAT and ACR may sound technical, but together they simply show buyers and vendors how accessible a digital product really is. If you sell software, a website or an app to government or enterprise buyers, sooner or later someone will ask for your VPAT and ACR, so it pays to understand both documents before that request arrives. A VPAT and its completed form, an ACR — the Voluntary Product Accessibility Template and the Accessibility Conformance Report — provide that standardised format, enabling procurement teams to compare options objectively and giving vendors a dated, auditable record to prioritise fixes and demonstrate inclusive design.

VPAT Defined

Definition: A Voluntary Product Accessibility Template is a standardised form that vendors complete to describe a product’s accessibility.

• Completed form: When filled out, the VPAT becomes an Accessibility Conformance Report (ACR) that documents test results and evidence.
• Standards covered: Commonly maps product conformance to WCAG, Section 508, EN 301 549, or international variants.
• Purpose: Helps procurement teams compare accessibility claims and make informed purchasing decisions.
• Typical users: Software vendors, government buyers, and private-sector procurement officers.
• Contents: Includes product details, evaluation methods, and conformance entries (e.g., Supports; Partially supports; Does not support; Not applicable).
• Limitations: Serves as a transparency tool, not a formal certification.
• Best practice: Producing a credible ACR usually requires expert accessibility testing.

ACR Defined

An Accessibility Conformance Report (ACR) is the completed VPAT. In simple words, the VPAT is the blank form and the ACR is the filled-in, dated report that a buyer actually reads. Many people say “VPAT” when they really mean the ACR, which is why the two names are usually written together as VPAT and ACR.

• Author: The vendor, or an independent accessibility consultant who tests the product on the vendor’s behalf.
• Scope: The exact product name, version number, platforms tested and the date of the evaluation.
• Body: One row for every success criterion of the chosen standard, with a conformance level and a short remark that explains the result.
• Evidence: The testing methods used — automated tools, manual keyboard checks and screen reader testing with JAWS, NVDA, VoiceOver or TalkBack.
• Honesty: A credible VPAT and ACR admits partial support and known gaps; a report that claims “Supports” on every row is usually the first thing an experienced buyer questions.

Because the VPAT and ACR travel together through procurement, the quality of the ACR decides whether your product moves to the shortlist or is rejected at the first screening.

Using a VPAT and ACR to Drive Accessibility Improvements

Overview

A VPAT and ACR — the Voluntary Product Accessibility Template and its completed form, the Accessibility Conformance Report — are practical tools that translate technical accessibility testing into a clear, comparable format for buyers and stakeholders.

Key reasons to have one

• Procurement readiness: Buyers and procurement teams use ACRs to compare accessibility claims consistently during RFPs and vendor evaluations.
  
• Risk reduction: Documenting test methods and results demonstrates due diligence and can lower legal and compliance exposure.
  
• Market access: Public-sector contracts and many enterprises require documented accessibility evidence; an up-to-date ACR improves chances of winning bids.
  
• Product improvement: Preparing a VPAT and ACR forces teams to test core user flows, prioritise fixes, and track remediation over time.
  
• Customer trust: Transparent reporting builds credibility with procurement officers, accessibility reviewers, and end users.

Best practices

• Use the VPAT edition that matches buyer requirements (e.g., WCAG, Section 508, EN 301 549).
  
• Describe testing methods (automated scans, manual review, user testing) and include sample evidence.
  
• Update the ACR with each major release and involve accessibility experts for credible results.

How does a VPAT demonstrate conformance with WCAG standards?

Definition

A Voluntary Product Accessibility Template (VPAT) for WCAG compliance is a standardised form vendors use to describe how a website, application, or digital product aligns with the Web Content Accessibility Guidelines. The template breaks WCAG success criteria into a consistent checklist so each item can be marked as Supports, Partially Supports, Does Not Support, or Not Applicable, and paired with concise evidence.

From VPAT to ACR

When a VPAT is completed after a thorough accessibility assessment, it becomes an Accessibility Conformance Report (ACR). The ACR is the finished, evidence-based document that procurement teams and reviewers use to understand which WCAG criteria are met, which need work, and the scope of testing performed.

Editions and versions

Modern VPAT releases (for example, VPAT 2.5) come in multiple editions to match regulatory needs: a WCAG-focused edition, a Section 508 mapping for U.S. federal procurement, an EN 301 549 mapping for European public tenders, and an international edition that consolidates mappings for cross-region use. Selecting the right edition ensures the report aligns with buyer expectations.

What to include?

A credible WCAG VPAT and ACR lists the product version, scope of testing, date, criterion-by-criterion results, representative examples of findings, and any exclusions or limitations. Clear notes on unresolved issues help readers assess risk.

Testing approach and upkeep

Excellent reports combine automated scans, manual inspections, assistive technology checks, and real user scenarios. Keep the ACR current after major releases and document methods and evidence to maintain credibility and support procurement decisions.

Types of VPATs

VPAT Type	Primary Standard/Framework	Purpose & Use Case	Region/Market Focus
VPAT 508	Section 508 of the U.S. Rehabilitation Act	Demonstrates compliance with accessibility requirements for federal procurement in the United States.	United States (federal agencies, contractors)
VPAT WCAG	Web Content Accessibility Guidelines (WCAG) 2.x	Used to show conformance with international web accessibility standards, often required by organizations worldwide.	Global (web-based products/services)
VPAT EU	EN 301 549 (European accessibility standard)	Required for ICT products and services sold in the European Union, aligning with EU accessibility directives.	European Union
VPAT INT	International accessibility standards (general)	Provides a flexible template for documenting accessibility compliance outside the U.S. and EU.	Global (non-U.S./EU markets)

✅ Key Notes for Choosing the Right VPAT

• U.S. federal contracts → VPAT 508 is mandatory.
• Web-based products → VPAT WCAG is most widely recognized.
• European procurement → VPAT EU aligns with EN 301 549.
• Other international markets → VPAT INT provides a general framework.

⚠️ Risks & Considerations

• Incomplete VPATs can harm credibility; buyers expect detailed testing results in a VPAT and ACR, not vague claims.
• Jurisdiction mismatch (e.g., using VPAT 508 for EU contracts) can lead to rejection.
• Updates matter: VPAT versions are revised regularly (the current series is VPAT 2.5 Rev), so using outdated templates may cause compliance issues.
  

📝 Common VPAT and ACR Mistakes to Avoid – Checklist

1. Clarity of Responses
   • Avoid vague answers like “Supports” without explanation.
   • Provide evidence or examples of testing results.
     
2. Template Accuracy
   • Use the correct VPAT type (508, WCAG, EU, INT) for the target market.
   • Confirm you’re working with the latest version (e.g., VPAT 2.5Rev).
     
3. Evidence of Testing
   • Document actual accessibility testing outcomes.
   • Do not rely on generic or copied language.
     
4. Transparency in Compliance
   • Acknowledge partial support or limitations honestly.
   • Avoid overstating compliance, as it reduces credibility.
     
5. Regular Updates
   • Revise the VPAT when product features change.
   • Update references to match evolving accessibility standards.
     
6. Market-Specific Requirements
   • Tailor the VPAT to regional procurement rules.
   • Ensure alignment with Section 508 (U.S.), EN 301 549 (EU), or WCAG (global web).

VPAT and ACR: Frequently Asked Questions

What is the difference between a VPAT and ACR?

A VPAT is the empty template published by the Information Technology Industry Council (ITI); an ACR is that template after it has been completed with real test results. So the VPAT and ACR are two stages of the same document — the form and the finished report. When a buyer asks for your “VPAT”, what they actually want is the completed ACR.

Who needs a VPAT and ACR?

Any vendor selling software, websites, apps or hardware to the US federal government needs one, because Section 508 procurement rules require accessibility evidence. Universities, state agencies, healthcare organisations and large enterprises also ask for a VPAT and ACR before signing a contract, and European public tenders ask for the same evidence against EN 301 549.

Which VPAT edition should I use?

Choose the edition that matches your buyer. VPAT 508 for US federal contracts, VPAT WCAG for web products sold worldwide, VPAT EU for European public procurement, and VPAT INT when one VPAT and ACR must cover several markets at once. If you are not sure, the INT edition includes all three standards in a single report.

How long does a VPAT and ACR stay valid?

There is no official expiry date, but buyers expect a report that describes the current version of the product. Good practice is to refresh the VPAT and ACR after every major release, or at least once a year, and to keep the older versions on file as an audit trail of your accessibility progress.

Can a vendor write its own VPAT and ACR?

Yes, the template is voluntary and self-declared, but a report prepared by an independent tester carries far more weight with procurement teams. At Ananyoo, a DHS Trusted Tester and IAAP-certified colleagues test every product with JAWS, NVDA, VoiceOver and TalkBack before writing the criterion-by-criterion VPAT and ACR, and we list every finding the way we do in our web accessibility case study.

✅ Conclusion

To summarize, preparing a VPAT and ACR demands precision, transparency, and alignment with the correct accessibility standards. Avoiding vague responses, outdated templates, and overstated compliance helps maintain credibility with procurement teams. Regular updates and evidence-based documentation strengthen accessibility claims. By following best practices, organizations can demonstrate genuine commitment to inclusivity. Ananyoo, with a DHS Trusted Tester and IAAP-certified colleagues on the team, prepares every VPAT and ACR with the same clarity, evidence and usability focus, so the documentation supports diverse markets and fosters equal access for all users.

Need a VPAT and ACR for your product? Ananyoo tests with real assistive technology and writes procurement-ready reports. See our web accessibility case study, our accessibility-ready themes and WordPress accessibility plugins, or read how to reach WCAG conformance. Learn more at ananyoo.com.