Many SaaS teams first hear about VPATs during a sales deal. The buyer sends a checklist, and one line says "Please provide your VPAT / ACR." This guide explains which customers ask for one, why they ask, and when it makes sense to start preparing.
The short answer
Laws usually do not require a vendor to have a VPAT. A VPAT is a procurement document: buyers use it to show they met their own obligation to buy accessible products. So whether you need one depends on who your customers are. If you sell to government, higher education or large enterprises, someone will ask for one sooner or later.
Which customers ask for one
- US federal agencies. Section 508 requires federal agencies to buy accessible information technology, and the ACR is their standard way to evaluate vendors. They usually want the 508 or INT edition. See Section 508 vs. WCAG.
- US state and local governments. Many states have their own IT accessibility policies, usually based on 508 or WCAG. They often ask for an ACR during procurement.
- Universities. US colleges and universities routinely ask for a VPAT when they buy teaching and office software, because students, faculty and staff with disabilities use it directly.
- Large enterprises. More and more companies include accessibility in their vendor assessment questionnaires, sent alongside the security and privacy questionnaires.
- EU public sector and customers affected by the EAA. EU public procurement refers to EN 301 549, which matches the EU edition of the VPAT. See what EN 301 549 is.
What happens without an ACR
- The deal stalls at compliance review until you provide the document.
- In a public tender, a missing required document can disqualify you outright.
- If a competitor has an ACR and you do not, they have the edge when everything else is equal.
A report written in a rush often skips testing and ends up vague, which draws more questions in review. Preparing ahead is safer than letting a deal force your hand.
When to start
- Before you go after government, higher education or enterprise customers. Procurement cycles are long, so the earlier you have an ACR, the better.
- The first time a customer asks for one. Confirm which edition and which WCAG version they want before you start testing.
- After a major redesign. An old ACR no longer reflects the product and needs an update. Many teams update theirs once a year.
How to prepare your first report
- Confirm the edition the customer needs: 508, EU, WCAG or INT.
- Test the main workflows of your product. See how to test accessibility.
- Fill out the template section by section. See how to fill out a VPAT 2.5.
- Prepare a public accessibility statement at the same time, and keep it consistent with the ACR.
- Put the known issues on your fix schedule, so the next ACR has fewer Partially Supports entries.
Self-assessment or third party
You can complete the ACR yourself, or have a third-party auditor test the product and issue it. A self-assessment is cheaper and faster and suits an early stage. A third-party report carries more weight in large procurements. Either way, the report must say who tested the product and how.
Next step
The generator creates a self-assessed ACR draft and an accessibility statement. It helps you pin down the scope and the known limitations; then complete the draft with your actual test results.
Ready to draft your ACR?
The preview is free. US$49 one-time per product to download the ACR and the statement.
Open the generator