VPAT Explained: What It Is, Why It Matters, and How to Get Started

If your organization sells software, websites, digital documents, mobile apps, learning platforms, or other technology-enabled services, there is a good chance you will eventually be asked for a VPAT. That request often shows up during procurement, in an RFI or RFP, or late in the sales process when a buyer wants to understand your accessibility posture before moving forward. Federal buyers, public-sector organizations, higher education institutions, and enterprise procurement teams increasingly expect vendors to provide clear accessibility documentation.

A VPAT can feel intimidating the first time you encounter it, but the core idea is straightforward: it is a standardized way to document how accessible your product is against recognized accessibility requirements. For organizations that want to compete for public-sector business, reduce procurement friction, and demonstrate a serious commitment to inclusive design, understanding the VPAT process is increasingly important.

What is a VPAT?

VPAT stands for Voluntary Product Accessibility Template. It is a free template published by the Information Technology Industry Council (ITI) that translates accessibility standards and requirements into a format vendors can use to document testing results for products and services. Once completed with actual testing results, that document becomes an Accessibility Conformance Report, or ACR.

That distinction matters. The VPAT is the template. The ACR is the finished report a buyer reviews. In practice, many people use “VPAT” as shorthand for both, but procurement teams are usually looking for the completed report, not the blank form.

What standards does a VPAT cover?

The current ITI template is VPAT 2.5Rev (April 2025). ITI provides four editions so vendors can align their report to the standards most relevant to the market or solicitation: Section 508, WCAG, EN 301 549, and the International edition that combines all three. ITI also notes that the WCAG edition supports WCAG 2.0, 2.1, and 2.2.

For many digital products, WCAG is the foundation buyers care about most. W3C’s current WCAG 2 guidance includes WCAG 2.1 and 2.2, and WCAG continues to be the common framework organizations use to evaluate web and digital accessibility.

Who usually needs a VPAT?

A VPAT is especially important for vendors selling information and communication technology to the U.S. federal government. Section508.gov recommends that vendors generate an ACR for any ICT intended to be marketed to the federal government, and notes that contracting officials use ACRs during market research and proposal evaluation. GSA guidance also explicitly recommends asking vendors for an updated VPAT or comparable ACR during pre-solicitation market research.

But federal sales are not the only reason to care. State and local government accessibility requirements are also getting more attention. Under the Department of Justice rule published April 24, 2024, state and local governments generally must make web content and mobile apps conform to WCAG 2.1 Level AA by April 24, 2026 if they serve populations of 50,000 or more, and by April 26, 2027 for smaller governments and special district governments. That means accessibility documentation is becoming more relevant across the broader public sector as well.

Even outside government contracting, a VPAT can strengthen trust with enterprise buyers. It gives procurement, legal, and accessibility reviewers a standardized way to understand where a product supports requirements, where gaps remain, and how mature the vendor’s accessibility program really is. This is especially valuable when the product in question is business-critical or customer-facing.

What goes into a VPAT or ACR?

A completed ACR is more than a one-line claim that a product is “accessible.” Section508.gov’s guidance explains that vendors should document the product name and version, report date, product description, contact information, evaluation methods, and the conformance results for the applicable criteria. The conformance language in the report uses standardized terms such as Supports, Partially Supports, Does Not Support, and Not Applicable.

Just as important as the rating itself is the explanation. The remarks column is where a vendor shows its work: what was tested, what is supported, where exceptions exist, and what limitations a buyer should understand. That detail is what makes an ACR useful in a real procurement setting.

Is a VPAT a certification?

No. ITI is explicit on this point: there is no VPAT certification, no official submission process, and no conformance logo issued for completing one. The VPAT is not a pass/fail badge. It is a reporting format that gives buyers a clearer picture of a product’s accessibility features and gaps.

That means a VPAT should never be treated as a marketing trophy. A strong ACR is honest, specific, and grounded in real testing. If a product partially supports a criterion, the report should say so plainly and explain the limitation. In fact, Section508.gov specifically advises buyers to look closely at claims like “supports” and “partially supports” rather than assuming all entries are equal.

What kinds of products can have a VPAT?

VPATs are used for a broad range of ICT products and services. Section508.gov describes ACRs as applying to software, hardware, electronic content, and support documentation. WCAG also applies beyond traditional web pages, including mobile experiences and non-web ICT guidance in related resources. In practical terms, that means a VPAT may be relevant for learning management systems, courseware, websites, SaaS platforms, mobile apps, PDFs, support portals, knowledge bases, and digital support documentation.

For organizations in learning and workforce development, this is a major consideration. A buyer may not only ask about the accessibility of the LMS itself, but also the accessibility of course content, learner-facing documents, assessments, help documentation, and mobile access points. A credible accessibility story usually has to address the whole experience, not just one component. This is an inference based on how Section 508 and WCAG apply across software, electronic content, support documentation, and mobile apps.

How do you create a VPAT the right way?

The first step is selecting the correct template edition. Section508.gov advises vendors selling to the U.S. federal government to use the Revised Section 508 edition or the International edition. From there, the product owner or vendor should test the product against the applicable criteria and document the results in the template. Section508.gov also points vendors to the OpenACR Editor as a way to create machine-readable ACRs.

In practice, a strong VPAT process usually includes a combination of manual testing, automated testing, assistive technology checks, and review by people who understand both the product and the standards. The goal is not to produce a perfect-looking document; the goal is to produce an accurate one. A rushed or overly optimistic VPAT can create sales friction later if a buyer’s review team finds that the report overstates accessibility support.

Common mistakes vendors make

One common mistake is treating the VPAT like a paperwork exercise instead of an evidence-based assessment. Another is using vague remarks that do not tell the buyer what actually works, what does not, and under what conditions. A third is failing to update the report after product changes. Because ACRs are used in active procurement decisions, outdated information can undermine credibility quickly. ITI’s guidance also makes clear that buyers may receive ACRs directly from vendors or see them posted publicly, so accuracy matters.

Another mistake is assuming that a partially accessible product has no path forward. In many cases, buyers are trying to understand risk, available workarounds, remediation plans, and whether a product is the best available fit. A transparent ACR is usually far more useful than a polished but unsubstantiated claim of full conformance. This is supported by Section508.gov’s guidance on how buyers interpret vendor claims.

Why this matters now

Accessibility expectations are not moving backward. Federal procurement already relies on Section 508 requirements, and the DOJ’s state and local government rule has added more urgency around accessible web and mobile experiences. At the same time, buyers are under pressure to evaluate digital tools more carefully, especially when those tools are central to service delivery, workforce training, or public access.

For vendors, that means accessibility documentation is becoming part of basic business readiness. A current, well-supported ACR can help reduce procurement delays, demonstrate organizational maturity, and make conversations with buyers more productive. It also helps internal teams see accessibility not as a one-time compliance event, but as an ongoing product quality discipline. This last point is an inference based on how ACRs are used in procurement and product evaluation.

Final takeaway

A VPAT is not just a form to fill out when a buyer asks hard questions. It is a structured way to show how your product performs against recognized accessibility requirements and where additional work may still be needed. For organizations selling digital products, platforms, or learning solutions, that transparency can make the difference between stalled procurement and forward momentum.

If your team needs to prepare an ACR, evaluate a learning platform, review digital courseware, or build a practical roadmap for accessibility improvements, starting early is the best move. The organizations that treat accessibility documentation as part of product readiness, rather than a last-minute scramble, are usually the ones best positioned for long-term growth. This is an inference based on current procurement guidance and the increasing formalization of accessibility requirements.

Need help evaluating the accessibility of your digital learning platform, course content, documents, or web experience? PowerTrain helps organizations assess current conformance, document findings clearly, and build practical next steps for accessibility improvement.