# VPATs® for SaaS Companies: How to Get an Accessibility Conformance Report (ACR), Win the Contract

- Channel: [The ADA Book](https://www.youtube.com/channel/UCnBOveah3DC9YmK4A_-J0BQ)
- Published: 2026-03-03
- Source video: [Watch on YouTube](https://youtube.com/watch?v=Cv4r4RgwkNM)
- Read on ReadTube: https://www.read.tube/p/videos/Cv4r4RgwkNM
- Language: Original (source language)

## Summary

**VPATs Simplified for SaaS Deals**

SaaS companies often need a VPAT, which is really an Accessibility Conformance Report, to satisfy procurement requirements and win contracts. The video explains that the process is straightforward: choose the right VPAT edition, run a credible accessibility audit, fix issues if needed, and issue an accurate report that reflects the product’s current accessibility. It also notes that buyers increasingly expect this documentation, especially in universities, enterprise, government, and public-sector procurement.

A VPAT is a standardized template that, once completed, becomes an Accessibility Conformance Report, and the two terms are often used interchangeably in the market. For SaaS companies, the ACR functions like a report card or mirror for accessibility: it should accurately reflect the product’s current state, not future intentions or marketing claims. The speaker emphasizes that demand is growing because more organizations require this documentation as part of procurement, especially in regulated or accessibility-conscious buying environments.

The guide explains that the best edition depends on the target market. Most web-based SaaS products use the WCAG edition, while Section 508, EU, or INT editions may be appropriate for other buyers or multi-market sales. To complete the VPAT credibly, the company needs a real accessibility audit with a representative scope, and the audit should use multiple evaluation methods such as keyboard testing, screen reader testing, visual review, code inspection where relevant, and other applicable checks.

Key points include:
- Buyers want a clean, current ACR because it can affect competitiveness in procurement.
- A strong audit should document scope, findings, WCAG success criteria, screenshots, code references, and recommended fixes.
- Companies can pause after the audit, fix issues, and then validate those fixes to produce a cleaner ACR.
- Independent, reputable accessibility providers are preferred because buyers care about accuracy and bias.
- ACRs should be updated after major releases, substantial accessibility improvements, standard upgrades, or when buyers request current documentation.
- There is no universal rule requiring a new ACR every year, but freshness matters.

The speaker closes by stressing that the process is simpler than it sounds: procure the right documentation, make it accurate, and use it to show buyers the product’s real accessibility status at a given point in time.