VPAT vs. ACR: What Are They and How Are They Different?

Accessibility documentation isn’t optional — especially for government agencies or large enterprises. But when someone asks for your “VPAT” or your “ACR”, it’s easy to feel lost in a sea of acronyms. Are they the same thing? Which one do you need and when? And what actually goes into creating either document?

The short answer: a VPAT and an ACR are related but not identical. Understanding the difference isn’t just technical trivia; it can mean the difference between winning a contract, avoiding legal risks, and confidently proving your commitment to accessibility.

Below, we’ll break down what a VPAT is, what an ACR is, and why the distinction matters.

VPAT: What Is It?

A VPAT — voluntary product accessibility template — is a standardized document that shows how well your digital products, including software, websites, mobile applications, electronic devices, etc., meet specific accessibility standards. 

Created by the Information Technology Industry Council (ITI), the VPAT provides a structured template for describing whether or not your product conforms, partially conforms, or does not conform to guidelines like:

• Section 508 of the Rehabilitation Act (U.S. federal government accessibility requirements)

• The Web Content Accessibility Guidelines (WCAG)

• EN 301 549, the European Union accessibility standard

Think of the VPAT as a “blank form” or questionnaire — something you fill out to describe how accessible your existing product is, feature by feature, against accessibility standards. 

A VPAT typically includes:

• The name, version, and description of the product being evaluated.

• The accessibility standards (such as WCAG 2.0, Section 508, or EN 301 549) used during evaluation.

• The methods and tools used for the evaluation.

• The evaluation results, along with explanations and further information where relevant.

One thing to call out around VPATs: They’re completely voluntary. There are no legal requirements to produce one unless it’s part of a procurement process or a client request. Additionally, a VPAT is a self-reported document, meaning accuracy depends on your level of expertise and honesty. It also doesn’t guarantee real-world usability for people with disabilities, nor does it replace thorough accessibility testing by users or independent audits.

Despite its limitations, a VPAT does provide a solid foundation for an ACR, which we’ll discuss in more detail below.

ACR: What Is It?

An Accessibility Conformance Report is the completed document that comes from filling out a VPAT. Like a VPAT, the ACR summarizes how well a specific product meets accessibility standards like WCAG, Section 508, EN 301 549, etc.

However, unlike the VPAT, an ACR includes actual findings, details, and explanations about how and where a product conforms, partially conforms, or does not conform to specific accessibility requirements.

A checklist with an accessibility symbol at the top of the page, in front of a laptop computer.

VPAT vs. ACR: Differences and Similarities

At first glance, a VPAT and ACR seem like the same thing. But VPATs and ACRs each have unique roles, audiences, and ways of being created. Here’s how.

Purpose of VPAT vs. ACR

The biggest difference between a VPAT and an ACR lies in their purpose:

• A VPAT is a blank template you use to document how your products or services meet specific accessibility standards. It’s a structured form designed to help you capture key conformance details.

• ACR is the completed report that results from filling out the VPAT. It includes a summary of actual findings and details, providing customers, procurement teams, or government agencies with a clear understanding of how accessible your digital content is. 

Put simply, the VPAT is the template; the ACR is the filled-in template.

Information Covered in VPAT vs. ACR

Both the VPAT and the ACR explain similar technical standards — but differ significantly in how much detail they contain. 

For example, a VPAT will list all the criteria from relevant accessibility standards (e.g., WCAG success criteria) and whether each criterion is met, partially met, or not met, with brief explanations. 

An ACR, on the other hand, provides more detailed statements about a product’s overall accessibility. Most ACRs include additional remarks explaining gaps, workarounds, or plans for future fixes.

Audience of VPAT vs. ACR

The VPAT and ACR are intended for slightly different audiences:

• VPATs are typically intended for internal teams (like compliance or product teams) who need to conduct the assessment and record results in a standard format.

• ACRs are primarily shared with external stakeholders — including government procurement officers, enterprise buyers, or potential clients — to demonstrate accessibility conformance and help inform purchasing decisions. However, they can also be useful for internal teams looking to enhance accessibility features.

If you receive an RFP (request for proposal) or bid on a government contract, you’ll typically be asked for your ACR.

Who Does the Testing

Another key difference between a VPAT and an ACR involves who conducts the actual accessibility testing.

For example, for a VPAT, you may perform an initial assessment that involves your developers or compliance teams documenting how a product meets standards based on code reviews or simple testing.

An ACR, on the other hand, might also come from internal testing, but you may also involve third-party accessibility experts to create a more credible, objective report. Independent audits add weight to an ACR's findings and help build trust with your clients.

How Testing is Done

Finally, while the VPAT and ACR both rely on accessibility testing, the depth and methodology of testing varies. 

VPATs might be based on partial testing, self-reported statements, or documentation review. The process is sometimes less rigorous, again depending on the expertise and resources available in your organization. 

ACRs usually involve a more in-depth evaluation, often combining manual testing with assistive technologies (like screen readers, magnifiers, or voice input tools) with user experience testing by people with disabilities and in-depth code analysis using accessibility testing tools. 

Here’s the bottom line: If you’re involved with digital accessibility compliance, you need to understand the difference between a VPAT and an ACR. While a VPAT is the standardized template you complete, the ACR is the actionable report that communicates your actual level of accessibility conformance. 

How Do VPAT and ACR Protect Digital Content?

Completing a VPAT — or even better, producing a thorough ACR — can help protect your digital content from legal risk, especially if your product’s accessibility is challenged. Let’s explore how these documents provide that protection.

Legal Protection and Risk Mitigation

Both a VPAT and an ACR can help reduce your legal risk by demonstrating your organization takes digital accessibility seriously. For example:

• A completed VPAT documents how your website, mobile app, or digital product aligns with accessibility requirements such as Section 508 standards or EN 301 549 best practices. While not legally required, a VPAT can serve as evidence that you’ve audited your product for accessibility and made efforts to comply.

• An ACR goes a step further, turning the VPAT into a finished report that clearly outlines which accessibility criteria your product fully supports, partially supports, or does not support. For government agencies and enterprise clients, an ACR may be required during the procurement process to ensure vendors are purchasing accessible technology.

If you face an accessibility lawsuit — such as an ADA demand letter or Section 508-related claim — a VPAT or ACR won’t shield you from liability. However, both documents can serve as good faith efforts to meet accessibility obligations, potentially influencing legal outcomes or reducing penalties. Plus, they show you’re committed to accessibility, which can improve your reputation with customers and stakeholders.

General Services Administration (GSA) Recommendations

The U.S. General Services Administration (GSA) offers guidance on creating VPATs and ACRs to support accessible technology procurement, including:

• Using the most current version of a VPAT template (currently VPAT 2.5 or higher) to ensure consistency and alignment with updated standards like WCAG 2.1.

• Providing clear, accurate, and detailed statements in the ACR to help government buyers evaluate accessibility. Vague or generic statements can be rejected or lead to additional scrutiny. 

• Including explanatory notes or remarks in the ACR to clarify partial support or known accessibility gaps. Include your plans for fixes if possible.

Following GSA recommendations helps you create VPATs and ACRs that fulfill expectations during federal or state procurement and reduces the chance of delays or rejections.

Ultimately, a VPAT or an ACR isn’t going to make you immune to accessibility lawsuits. However, they are vital tools for demonstrating your commitment to compliance, reducing legal exposure, and gaining trust in procurement processes. More simply, they show your organization understands — and is actively addressing — digital accessibility requirements.

An accessibility icon with a bar graph in the background, surrounded by a scatterplot and circular graph.

Beyond the VPAT: Achieve True Accessibility with AudioEye

Both a VPAT and an ACR are great tools for understanding where your website, app, or digital product stands on the accessibility spectrum. But they’re just part of the picture. These documents help document your conformance level and demonstrate a commitment to accessibility, but they don’t guarantee full compliance or eliminate legal risks.

True peace of mind — and actual accessibility — go beyond documentation and happen with the help of an experienced accessibility partner like AudioEye. 

At AudioEye, we take a three-pronged approach to accessibility, combining powerful automation with human-assisted AI technology to detect and fix accessibility issues, helping you achieve industry-leading compliance with accessibility standards. Additionally, AudioEye offers a VPAT service that provides detailed reports on how your digital content meets technical standards and highlights your commitment to accessibility, inclusivity, and legal compliance.

Ready to move beyond paperwork and put accessibility into action? Get started with a free accessibility scan. 

Want to learn more about our Automated Accessibility Platform or VPAT services? Get in touch with us!