SaaS companies are pursuing Accessibility Conformance Reports (ACRs) because procurement buyers now expect them. An ACR, completed using the Voluntary Product Accessibility Template (VPAT), documents how a web app or software product conforms to WCAG 2.1 AA or WCAG 2.2 AA. Without one, deals stall or go to a competitor who has one ready.
The shift is not philosophical. It is commercial. Enterprise buyers, government agencies, and education institutions increasingly require ACRs before signing contracts. SaaS companies that recognized this early are already closing deals faster.
| Factor | Detail |
|---|---|
| Primary Driver | Procurement requirements from enterprise, government, and education buyers |
| Standard | WCAG 2.1 AA (most common); WCAG 2.2 AA adoption growing |
| VPAT Edition | WCAG edition is default for most SaaS companies |
| Prerequisite | An accessibility evaluation of the product against WCAG |
| Update Frequency | After significant product changes (no formal expiration) |
What Is Driving the Demand for ACRs in SaaS?
Three forces are converging. First, government procurement at the federal and state level increasingly references Section 508 and WCAG conformance. Vendors without documentation are filtered out before a demo ever happens.
Second, enterprise buyers are building accessibility into their vendor evaluation criteria. A SaaS company selling a CRM, LMS, HR platform, or project management tool will eventually face a procurement questionnaire that asks for an ACR. Not having one is an immediate disqualifier in many cases.
Third, the European Accessibility Act (EAA) went into effect in June 2025, requiring digital products and services sold in the EU to meet EN 301 549. SaaS companies with global customers are now working through compliance across multiple standards. An ACR built on the INT edition of the VPAT maps conformance against WCAG, Section 508, and EN 301 549 simultaneously.
The ACR as a Competitive Advantage
For most SaaS companies, the ACR started as a checkbox. It has become a differentiator.
When two competing products are evaluated side by side, the one with a current, independently issued ACR signals maturity. It tells the buyer the company invested in a real accessibility evaluation, addressed conformance gaps, and documented the results transparently. That is a trust signal procurement teams respond to.
How Does the VPAT Process Work for a SaaS Product?
The process follows a clear sequence. An auditor evaluates a representative sample of screens and user flows from the web app or software against the chosen WCAG standard. The evaluation identifies accessibility issues at the success criteria level.
After the audit report is delivered, the company remediates the identified issues. Once remediation is complete and fixes are validated, the VPAT template is filled in. Each WCAG criterion receives a conformance status: Supports, Partially Supports, Does Not Support, or Not Applicable. The completed document is the ACR.
The WCAG edition of the VPAT is the default for most SaaS companies selling primarily to U.S. buyers. Companies selling into government or EU markets may need the Section 508 or INT edition.
Why Timing Matters More Than It Used To
Procurement cycles have deadlines. When a buyer requests an ACR and the SaaS company does not have one, the timeline to produce one can be weeks or months depending on the product’s complexity and current conformance posture.
Companies that wait until a deal is on the line often lose that deal. The audit, remediation, and ACR process takes time. Starting before the request arrives means the documentation is ready when it counts.
ACRs do not have a formal expiration date. But the recommendation is to update them after significant product changes. A major redesign, a new feature set, or a migration to a new framework are all triggers. Buyers notice when an ACR references an outdated product version.
Cost and Pricing Considerations
Pricing for a VPAT engagement varies based on the number of screens, the complexity of the application, and the WCAG standard chosen. A web app with 15 screens and standard interactive components costs less to evaluate than a platform with 60 screens, complex data tables, and embedded media.
Most SaaS companies find the cost reasonable relative to the contract value they are protecting or pursuing. A single enterprise deal can justify the audit and ACR investment many times over.
What Happens If a SaaS Company Skips the ACR?
The consequences are commercial, not hypothetical. Without an ACR, a SaaS company is excluded from procurement shortlists. Government agencies under Section 508 are required to evaluate accessibility documentation. Education institutions purchasing EdTech often mandate ACRs. Healthcare organizations increasingly follow the same pattern.
Beyond procurement, ADA compliance risk is real. SaaS products that serve the public or are used by organizations with accessibility obligations can become the subject of demand letters or lawsuits. An ACR does not eliminate legal risk, but it demonstrates a documented commitment to conformance.
Do SaaS companies need a new ACR for every product update?
Not for every update. Minor patches and bug fixes rarely affect WCAG conformance. A new ACR is recommended after significant product changes: redesigns, new feature modules, or infrastructure migrations that alter the user interface. Keeping the ACR current with the product’s actual state is what matters.
Which VPAT edition should a SaaS company choose?
The WCAG edition covers most SaaS companies selling to private-sector and education buyers in the U.S. Companies selling to federal agencies may need the Section 508 edition. Companies with EU customers should consider the INT edition, which maps conformance against WCAG, Section 508, and EN 301 549 in a single document.
Can a SaaS company fill out the VPAT internally?
Technically, yes. Practically, independently issued ACRs carry more weight with buyers. An ACR completed by the same company that built the product raises credibility questions. Procurement teams increasingly look for third-party evaluation as the basis for the conformance claims documented in the ACR.
SaaS companies that invest in accessibility documentation now are positioning themselves ahead of a market that is only moving in one direction. The ACR is no longer optional in competitive procurement. It is table stakes.
Contact Kris Rivenburgh to discuss VPAT and ACR services for your SaaS product.