VPAT vs Accessibility Statement 2026 | What's the Difference?

Last updated: 2026-06-29

A VPAT (Voluntary Product Accessibility Template) and an accessibility statement are two documents people constantly confuse, and using the wrong one in the wrong situation can cost you a sale or weaken your legal position. A VPAT is a formal, standardized report that documents how a product conforms to accessibility standards such as WCAG 2.1, Section 508, and EN 301 549. It is produced by the vendor, written in technical conformance language (Supports, Partially Supports, Does Not Support), and is most often requested during a procurement process by government agencies, universities, and large enterprises before they buy your software. An accessibility statement, by contrast, is a short public-facing webpage where you tell visitors how committed you are to accessibility, which standard you aim to meet, how to report problems, and what to expect when they do. One is a sales and compliance artifact for buyers; the other is a trust-and-feedback channel for end users. This comparison explains exactly when you need each, what goes inside them, and why many organizations end up needing both.

At a Glance

Feature VPAT (Voluntary Product Accessibility Template) Accessibility Statement
Primary audience Procurement teams and buyers (B2B, government, education) End users and the general public
Format Standardized table rating each WCAG / Section 508 criterion Plain-language webpage describing commitment and contact info
Who requests it Buyers during purchasing / RFP processes Nobody requests it — you publish it proactively
Conformance detail High — criterion-by-criterion Supports / Partially / Does Not Support Low — states a target standard but no per-criterion breakdown
Legal / compliance role Evidence of conformance for Section 508 / EN 301 549 procurement Evidence of good-faith effort under ADA / EAA
Effort to produce High — requires full WCAG testing of the product Low — can be drafted in an afternoon
How often it must be updated Re-issued whenever the product changes meaningfully Reviewed periodically; updated when your target or contact changes
Public or private Usually shared privately with buyers on request Published openly on your website (often linked in the footer)

VPAT (Voluntary Product Accessibility Template)

Type: Standardized vendor conformance report Pricing: Free template (ITI/Section 508); professional VPAT authoring by a consultant typically $3,000-$15,000 depending on product complexity Best for: Software vendors, SaaS companies, and agencies selling digital products to government, education, or enterprise buyers who require documented Section 508 / WCAG / EN 301 549 conformance.

Pros

  • Required to win contracts with US federal agencies, public universities, and many large enterprises that mandate Section 508 conformance during procurement
  • Uses a standardized format (WCAG 2.x, Section 508, EU EN 301 549 editions) that buyers' accessibility teams know how to evaluate
  • Documents conformance criterion-by-criterion, giving buyers an honest, auditable picture of what works and what does not
  • An accurate VPAT signals organizational maturity and can be a competitive differentiator in B2B and govtech sales

Cons

  • Time-consuming to produce correctly — every WCAG success criterion must be tested and rated, ideally by someone trained in conformance evaluation
  • A dishonest or copy-pasted VPAT is a serious liability — overstating conformance can be treated as misrepresentation if a buyer later finds the product inaccessible
  • Goes stale quickly; it must be re-tested and re-issued whenever the product changes significantly
  • Not meant for end users — its dense conformance tables are useless to a customer who just wants to know how to get help

Accessibility Statement

Type: Public-facing commitment and feedback page Pricing: Free — typically a single webpage you write yourself or generate from a free template (e.g. W3C accessibility statement generator) Best for: Every website owner — small businesses, nonprofits, e-commerce stores, and content sites — that wants to show good faith and give users a way to report accessibility problems.

Pros

  • Expected (and in some jurisdictions effectively required) for the European Accessibility Act and public-sector accessibility regulations as a way to show good-faith effort
  • Gives users with disabilities a clear, human way to report barriers and request an accessible alternative
  • Demonstrates good faith, which can be a meaningful factor if you ever face an ADA demand letter or complaint
  • Quick to publish and easy to keep current — no formal conformance testing required to get a basic version live

Cons

  • Carries no procurement weight — a buyer's accessibility team will not accept a statement in place of a VPAT
  • Easy to write empty promises that you cannot back up, which can actually hurt you if your site is clearly inaccessible
  • Should reference a real conformance target and contact method; a vague statement with no follow-through provides little protection
  • Does not document criterion-level conformance, so it tells technical buyers nothing concrete about what passes or fails

Our Verdict

These documents are not interchangeable, and for most growing organizations the answer is to have both. If you sell software or digital services to government agencies, universities, or large enterprises, a VPAT is non-negotiable — it is the document their procurement and accessibility teams will ask for, and an accessibility statement will not satisfy that requirement. If you run a website, store, or content business that serves the public, an accessibility statement is the right starting point: it costs nothing, gives users a way to report barriers, and demonstrates the good faith that matters if you ever receive an ADA demand letter. Crucially, neither document makes your product accessible on its own — they describe accessibility, they do not create it. Write the VPAT only after you have actually tested against WCAG, and write the statement only with a real conformance target and a monitored contact method behind it. An honest VPAT plus a maintained accessibility statement, both backed by real remediation work, is the combination that holds up under both procurement scrutiny and legal pressure.

Further Reading

Other Comparisons