What Is a VPAT? A Guide to VPATs and ACRs
Read the original on levelaccess.com ↗A Voluntary Product Accessibility Template (VPAT®) is a standard form for reporting product accessibility. Once completed, it becomes an accessibility conformance report (ACR) that buyers review.
A promising deal is moving toward signature when the buyer’s procurement team sends one more request: your VPAT report. If you build software for government agencies, colleges and universities, or large enterprises, you probably get that request often. And the document you send back can speed up the deal or stall it.
The good news? A VPAT isn’t complicated once you know how the pieces fit together. In this blog, we’ll explore what a VPAT is, how it differs from an ACR, and which of the four editions fits your market. You’ll also learn how to read an ACR, how to get a credible report for your product, and when to update it.
Key insights
- A VPAT is a free, standardized template. A completed VPAT is an ACR—the report buyers actually review.
- The current version, VPAT 2.5Rev, comes in four editions: 508, EU, WCAG, and INT. Choose the one that matches the standards your buyers require.
- A strong ACR describes its evaluation methods and pairs every conformance level with clear remarks, so buyers can judge real-world impact. It also includes strong scores: for example, no criteria marked “Does Not Support,” and minimal criteria marked “Partially Supports.”
- Public-sector organizations, including U.S. federal agencies, generally can’t buy your product without an ACR, and many other buyers—especially in regulated industries and enterprise markets—now ask for proof of accessibility, too. In fact, 83% of professionals we surveyed say their organization requires proof of accessibility at least most of the time in procurement.
- Update your ACR whenever your product changes. An ACR more than two years old will generally be regarded as outdated and unreliable by buyers.
- Credible ACRs come from comprehensive testing, including manual evaluation by experts. However, AI tools can generate a preview of your report based on a manual audit.
What is a VPAT, and how is it different from an ACR?
A VPAT is a blank template for documenting how well a product conforms to accessibility standards. An ACR is what you get when you complete that template for a specific product and version.
The Information Technology Industry Council (ITI) publishes and maintains the VPAT, and it’s free to download. The template started as a tool for U.S. federal procurement under Section 508 of the Rehabilitation Act of 1973. Today, a wide range of buyers—including state and local governments, higher education institutions, and enterprises—all use ACRs to evaluate vendor accessibility.
In practice, people often use the terms VPAT and ACR interchangeably. A request for proposal (RFP) might ask for “your VPAT,” but what the buyer wants is your completed ACR. Here’s how the two compare:
| VPAT | ACR | |
|---|---|---|
| What it is | A standardized, blank template | A completed report for a specific product and version |
| Who creates it | ITI publishes and maintains it | The product vendor, often with help from a third-party expert |
| What it contains | Instructions, conformance level definitions, and empty criteria tables | Test results, a conformance level, and remarks for each criterion |
| What buyers do with it | Nothing on its own | Compare products and assess accessibility risk before they buy |
The current version is VPAT 2.5Rev, released in April 2025. Building your ACR on the latest version signals to buyers that your documentation is current.
It’s worth clearing up a common misconception: There’s no VPAT certification. ITI confirms that no certification or conformance logo exists for the template. An ACR is your organization’s own statement of how well your product conforms.
The four VPAT editions and which one to use
VPAT 2.5Rev comes in four editions, and each maps to a different set of standards. Choose the VPAT edition that matches the standards your buyers require.
| Edition | Standards covered | Best for selling to |
|---|---|---|
| 508 | Revised Section 508 standards, which incorporate WCAG 2.0 AA | U.S. federal agencies |
| EU | EN 301 549, which incorporates WCAG 2.1 AA | Public-sector and private-sector buyers in the European Union (EU) |
| WCAG | WCAG 2.2 AA, with WCAG 2.0 AA (ISO/IEC 40500) and WCAG 2.1 AA also referenced | State and local government, higher education, enterprise |
| INT | Revised Section 508, EN 301 549, and WCAG 2.2 AA combined | Buyers across multiple markets |
You’ll note that the Web Content Accessibility Guidelines (WCAG), which are the global standard for digital accessibility, are at the core of all four. However, if you sell into the European market, be aware that EN 301 549 includes requirements outside the scope of WCAG, even though the current official version incorporates WCAG 2.1 Level AA. The Section 508 standards for U.S. federal agencies also go beyond WCAG, even though they incorporate WCAG 2.0 Level AA.
If you sell internationally, the INT edition lets you maintain one report instead of three.
What EN 301 549 V4.1.1 means for the EU edition
EN 301 549 is the harmonized European standard for accessible information and communication technology. Version 4.1.1, published on Sep 2, 2026, moves its web, document, and software requirements from WCAG 2.1 to WCAG 2.2 Level AA.
The new version isn’t yet an official requirement. That only happens once the European Commission cites it in the Official Journal of the EU, which is currently expected on Dec 16, 2026. Until then, the previous version, EN 301 549 v3.2.1, remains the presumed standard of conformity with laws like the European Accessibility Act (EAA) and the EU Web Accessibility Directive (WAD).
The current EU edition of the VPAT still maps to EN 301 549 v3.2.1, incorporating WCAG 2.1. However, if you sell into Europe, start testing against WCAG 2.2 Level AA now. That way, you’ll be ready when the new version of the standard becomes official and when the template catches up.
What’s in a VPAT report, and how to read one
An ACR lists every criterion in the standards it covers, assigns each one a conformance level, and explains the result in a remarks column. When you read an ACR, the remarks tell you far more than the levels alone.
Most ACRs follow the same structure:
- Product information: The product name, version, report date, and a contact for accessibility questions.
- Evaluation methods: The automated tools, manual techniques, and assistive technologies used to test the product.
- Applicable standards: The standards and guidelines the report covers, based on the edition.
- Conformance tables: One row per criterion, each with a conformance level and remarks.
ITI defines five conformance levels in the template’s instructions for authors:
| Conformance level | What it means |
|---|---|
| Supports | The functionality meets the criterion without known defects, or meets it through an equivalent alternative. |
| Partially Supports | Some functionality doesn’t meet the criterion. |
| Does Not Support | Most functionality doesn’t meet the criterion. |
| Not Applicable | The criterion isn’t relevant to the product. (According to WCAG, when a particular criterion isn’t present, it is considered “supported” rather than not applicable.) |
| Not Evaluated | The product hasn’t been tested against the criterion. Authors can use this only for WCAG Level AAA criteria. |
What good remarks include
Buyers don’t always expect a fully accessible product, but they do expect an accurate report. Strong remarks turn a conformance level into information a buyer can act on. For any criterion your product doesn’t fully support, your remarks should:
- Identify the gap: Name the specific feature, page, or component that doesn’t conform.
- Explain the cause: Describe why the issue exists in plain language.
- Describe the impact: Clarify how the issue affects people with disabilities, including users of assistive technology.
Compare “Partially Supports” with no comment to this: “Most form fields have programmatic labels. The date picker on the scheduling page doesn’t, so screen readers announce it only as ‘edit text.’ A fix is planned for version 4.3.” The second version builds trust because it’s specific.
Red flags for buyers reviewing an ACR
If you’re on the buying side, pay close attention to these warning signs:
- Every row says “Supports”: Few complex products conform fully, so a perfect report can point to light testing.
- No evaluation methods listed: Without knowing how a product was evaluated, you can’t judge how the vendor reached its conclusions.
- An outdated template or product version: A report built on an older VPAT version, or for a past release, may not reflect the product you’re buying.
- Empty remarks: A Partially Supports or Does Not Support result without explanation leaves you guessing about the real impact.
For more guidance on evaluating ACRs from buyers, explore our VPAT vetting checklist.
Who needs a VPAT, and how often to update it
If you sell to U.S. federal agencies, you need an ACR. If you sell to state and local governments, higher education, or enterprises, you’ll likely need one too. And once you have one, you’ll need to keep it current.
Federal sales depend on an ACR
Under Section 508, federal agencies use your ACR to assess your product’s accessibility. According to Section508.gov, the government generally can’t proceed with a purchase without one unless a special exception applies. So while the template is called “voluntary,” completing an ACR isn’t optional if you want agencies to consider your product.
Importantly, your product can still be considered even if it doesn’t meet every standard. Many agencies are directed to purchase the most accessible product that meets their business needs, a practice known as “best meets.” That’s why accuracy matters more than a perfect score.
Other buyers ask for proof, too
Proof of accessibility is now a procurement gate well beyond public-sector sales. In fact, 83% of professionals surveyed for our latest State of Digital Accessibility Report say their organizations require proof of accessibility most or all of the time when buying digital products, up from 75% in 2025. 42% say it’s always required, compared to 31% in 2025.
When to update your ACR
An ACR is a snapshot of one version of a product (or multiple products that are part of one solution) at one point in time. Section508.gov notes that any product change, from a version release to a bug fix, may call for an updated report. Here are the most common triggers:
- New product versions: Update your ACR when a release changes features, interfaces, or workflows.
- New standards: Revisit your report when the standards behind your edition change, such as the move to WCAG 2.2 in EN 301 549 V4.1.1.
- New template versions: Move to the latest VPAT version when ITI releases one.
- Time: Even without major changes to products, standards, or template versions, a yearly refresh keeps your report date current for buyers. An ACR more than two years old will likely be regarded as outdated and unreliable.
How to get a VPAT for your product
For the most credible and competitive documentation, many organizations choose to obtain a VPAT report from a third-party expert. A digital accessibility solution provider, like Level Access, has the resources to perform a comprehensive evaluation of your product, and the experience to complete the VPAT itself thoroughly and accurately.
An expert partner can also provide the tools and guidance you need to swiftly address any issues identified in your evaluation, so you can share a favorable report. And many buyers are more likely to trust ACRs from reputable vendors.
The alternative is to complete the VPAT yourself. This approach is only advisable if your organization already has significant in-house accessibility resources and expertise, including manual testers. If you are in a position to write your own VPAT, here’s how the process works.
- Choose the edition: Download the appropriate VPAT edition from the ITI’s website, based on the markets you sell into and the standards your buyers require. Use the editions table above as your guide.
- Test with automated and manual methods, including using assistive technology: Automated scans find many common issues quickly, but they can’t evaluate everything. Manual testing—including testing with assistive technologies, such as screen readers, keyboard-only navigation, browser zoom, and voice control software—catches the rest. Test the specific product version your report will cover.
- Document results and write clear remarks: Record a conformance level for every criterion, then write remarks that follow the guidance above.
- Review, publish, and maintain: Have someone with accessibility expertise review the report before you publish it. Then make it available upon request and plan your next update around your release schedule.
Common pitfalls to avoid
Most weak ACRs share the same problems. Teams complete the template from memory instead of testing, choose the wrong edition, or let the report go stale. Teams also mark criteria “Supports” without evidence, which carries significant risk—claiming conformance without the data to back it up can jeopardize a deal or existing contract.
For deeper insight on the VPAT process, explore our guide to accessibility conformance reports.
Can AI generate my VPAT report?
Providing buyers with a VPAT that has not been validated or updated by a human is not recommended. Your VPAT report will only carry weight when buyers can trust that the information in it is thorough and accurate. That typically means that your product was evaluated by a reputable expert, using both manual and automated testing, and that the VPAT itself was completed by a person who is knowledgeable about accessibility—not by AI. Some state agencies require that ACRs clearly state that any findings produced by AI were validated by people.
However, AI tools, like Level Access’s AI VPAT Previews, can give you a quick snapshot of what your ACR is likely to say based on existing manual test results. While not suitable for use in official procurement, these previews can help you understand which areas of your product need attention before you’re ready to produce a formal VPAT.
Turn your ACR into a sales advantage
A VPAT is just a template, but a well-built ACR is proof buyers can trust. Choose the edition that fits your market, test thoroughly, and write remarks that explain real impact. Then keep your report current as your product and the standards evolve.
With 25+ years of accessibility expertise, Level Access helps software vendors test products, fix and prevent issues, and produce credible conformance documentation that wins deals. Ready to give buyers the proof they’re asking for? Get a VPAT from Level Access today, or request a demo to explore how our platform helps you maintain ongoing conformance.
The post What Is a VPAT? A Guide to VPATs and ACRs appeared first on Level Access.