SaaS providers are increasingly being asked to provide a VPAT/ACR for their product to be eligible for purchase. The Voluntary Product Accessibility Template (VPAT), once completed, becomes an Accessibility Conformance Report (ACR) that shows procurement teams how your product or service conforms to technical accessibility standards (usually WCAG).
| Core Concept | What SaaS Providers Need to Know |
|---|---|
| Documentation Purpose | ACRs give procurement teams standardized information to evaluate and compare vendor accessibility |
| Market Drivers | Section 508, ADA obligations, and the European Accessibility Act push buyers to require documentation |
| Recommended Standard | WCAG 2.1 AA conformance satisfies most procurement requirements across sectors |
| Process Timeline | Audit through ACR delivery typically takes 2-4 weeks depending on scope and remediation |
Table of Contents
Why Do Buyers Require ACRs from SaaS Providers?
Organizations purchasing SaaS (Software-as-a-Service) products and services face their own accessibility obligations. Federal agencies must comply with Section 508. Universities navigate ADA requirements. European public entities follow EN 301 549 under the European Accessibility Act. When these buyers adopt your SaaS offering, they inherit accessibility risk.
An ACR transfers confidence. Procurement teams use this standardized documentation to verify that your product or service meets WCAG criteria before bringing it into their environment. Without an ACR, buyers cannot objectively assess your accessibility or compare you against competitors who provide documentation.
This requirement has expanded well beyond government procurement. Enterprise companies now routinely request ACRs during vendor evaluation. Healthcare systems need documentation before adopting patient-facing tools. Educational institutions evaluate accessibility before selecting learning platforms. The expectation has become standard across B2B SaaS markets.
How Should SaaS Providers Time Their First VPAT?
Timing involves balancing product stability against market opportunity. Documentation requires evaluating a specific version of your product, so creating an ACR during heavy development produces documentation that quickly becomes outdated.
The strategic moment arrives when three conditions align:
- Your core interface has stabilized enough that major changes are quarterly rather than weekly
- Your target market demonstrably expects accessibility documentation
- Your product roadmap shows a clean window before the next significant release
SaaS providers targeting enterprise, government, or education segments should budget for documentation once their product reaches this stability threshold. Waiting until a deal requires documentation creates pressure that compromises quality or loses opportunities.
Coordinate ACR creation with your release schedule. If version 3.0 launches in two months, wait for that release rather than documenting version 2.9. Accessible.org clients often align audit timing with stable releases to maximize documentation lifespan.
What Belongs in Scope for a SaaS Audit?
Scoping identifies which screens and functionality require evaluation. Most SaaS applications share interface patterns throughout, so representative sampling provides accurate conformance information without exhaustive assessment.
Effective scoping considers:
- Primary user flows representing core product value
- Distinct screen types introducing unique interface elements
- Role-based experiences if your product serves different user types
- Desktop and mobile environments based on how customers access your product
A collaboration product might scope around workspace creation, document editing, commenting features, and administrative settings. A platform like Shopify requires evaluating merchant-facing administration separately from customer storefront templates, with clear documentation noting which components fall under platform control.
For SaaS providers offering multiple products, each product typically requires separate documentation. A suite of related applications may share interface patterns that reduce combined audit scope, but procurement agents expect ACRs specific to what they purchase.
What Happens During the Audit and Documentation Process?
The process begins with a technical accessibility expert systematically evaluating your scoped screens against WCAG success criteria. This involves screen reader testing, keyboard navigation assessment, visual inspection, code review, browser zoom testing, and color contrast analysis.
Each identified issue gets documented with specific location, applicable WCAG criterion, and remediation guidance. This audit report becomes the foundation for both fixing issues and completing the Voluntary Product Accessibility Template.
Many SaaS providers pause after receiving audit results to remediate before final documentation. This approach produces ACRs reflecting improved accessibility rather than a snapshot of problems. The workflow typically follows this pattern:
- Receive detailed audit findings
- Development team addresses identified issues
- Accessibility experts validate fixes
- Iterate until reaching desired conformance
- Complete VPAT and issue final ACR
Accessibility Tracker streamlines this remediation phase by letting teams track issue status and coordinate validation within a single platform.
What Makes ACR Documentation Credible?
Procurement agents with accessibility experience scrutinize ACRs for reliability signals. They evaluate whether documentation accurately represents product accessibility or overstates conformance for competitive advantage.
Credibility indicators include thorough evaluation methodology descriptions, detailed remarks explaining any partial conformance, and independent third-party issuance. Self-completed ACRs raise skepticism because product teams naturally view their own work favorably and often lack evaluation expertise.
Red flags that undermine credibility include empty remarks columns, blanket conformance claims without supporting detail, outdated evaluation dates, and association with overlay widget vendors. Experienced procurement agents recognize these patterns from reviewing hundreds of ACRs.
Beyond procurement, ACR quality matters for due diligence scenarios. Investors and acquirers increasingly examine accessibility documentation when evaluating SaaS companies. Credible ACRs signal operational maturity while questionable documentation raises concerns about technical debt and compliance risk.
When Do ACRs Require Updates?
ACRs document accessibility at a specific point in time. Product evolution triggers documentation updates to maintain accuracy and relevance.
Update triggers include:
- Major version releases introducing new functionality
- Interface redesigns changing user interaction patterns
- Significant remediation improving conformance levels
- Standards updates affecting evaluation criteria
- General freshness after 1-2 years
- Buyer requests for current documentation
Build ACR maintenance into your product roadmap. Planning documentation updates alongside major releases prevents scrambling when procurement opportunities require current information.
FAQ
How do SaaS providers choose the right VPAT edition?
Accessible.org recommends the WCAG edition as the default because it addresses requirements most buyers reference. Select the 508 edition for federal agency sales, the EU edition for European public sector under EN 301 549, or the INT edition when selling globally across multiple regulatory environments.
What does VPAT documentation cost?
Accessible.org charges $350 to complete the WCAG edition VPAT plus audit costs. Accessible.org audits typically range from $1,500-$2,750 depending on scope. Investment scales with product complexity and number of unique screens requiring evaluation.
Do accessibility issues disqualify SaaS products from consideration?
Documented issues do not automatically eliminate your product or service. Buyers expect varying conformance levels and evaluate whether gaps affect their specific needs. Transparent documentation with detailed remarks demonstrates integrity that procurement teams value over inflated claims.
Can SaaS providers create ACRs internally?
The Voluntary Product Accessibility Template is freely available from ITIC.org. However, completing it accurately requires genuine accessibility evaluation using diverse testing methodologies. Internal teams often lack this expertise, and self-issued documentation carries less weight with buyers.
The Accessibility Tracker platform features an AI VPAT generator for providers who have audit report and are issuing their own ACR.
Final Thoughts
The VPAT to ACR process is fairly simple and straightforward.
If you have the technical expertise in-house and an independently issued ACR isn’t necessary, you can get started with an audit now. Otherwise, sourcing out to a third-party specialist company like Accessible.org is the way to go.