A SaaS team gets a credible VPAT by having the product audited against WCAG 2.2 Level AA, then keeping the resulting ACR current after major releases. Most of the work sits inside your company. You need one accountable owner and an honest scope before the auditors start.

Software vendors selling to federal agencies have filled out VPATs since 2001, but the pressure has spread well past federal deals. State and local governments now have to meet WCAG 2.1 Level AA under the Americans with Disabilities Act (ADA) Title II rule, and they pass that requirement to the vendors they buy from. In the EU, the European Accessibility Act (EAA) has applied since June 28, 2025 to consumer-facing services like ecommerce and banking.

There’s real upside here beyond getting sales through the procurement door. This post walks through how to do it the right way, because yes, there are wrong ways.

A Note on Terms

The VPAT is the blank reporting template from the Information Technology Industry Council (ITI). Once it’s filled in with real test results, it becomes an Accessibility Conformance Report, or ACR. Most buyers say “VPAT” when they mean the ACR, and that’s fine.

For the full background on editions and versions, I cover it in what a VPAT and ACR are. This post is about getting one done inside a SaaS company.

Why Audit Depth Decides VPAT Credibility

A SaaS company gets a credible VPAT by having its product audited. Not by someone on staff who has tried a screen reader a few times. The depth of the audit decides the credibility of the ACR, and a shallow audit produces a shallow report that procurement reviewers see through.

A good audit also gives your developers clearer remediation guidance, and the product ends up working better for more people. So the money buys a better product as well as a document.

Having WCAG testing tools in your workflow and people who can run a screen reader doesn’t prepare you to author a VPAT that survives procurement scrutiny. The author needs deep knowledge of WCAG and of how people with different disabilities actually use software. They also need to understand your front-end code and how your product gets built and shipped.

That takes a comprehensive audit, which is more than an in-house team can usually produce with basic testing tools. An experienced consultant who knows SaaS gets you a clean ACR and a lot more value along the way.

Who Owns VPAT Readiness Inside a SaaS Organization?

VPAT readiness is cross-functional, and product management usually drives it. Give one person accountability, often a product lead or an accessibility program manager, so the work doesn’t stall between teams.

Product management drives the process. PMs set the scope and turn audit findings into roadmap decisions. They’re the ones who get the call when procurement asks for documentation.

Engineering owns the technical work. They set up test accounts and explain custom components, and in the end they fix what the audit finds. Engineers who know the WCAG success criteria can head off issues before they become findings.

Design owns patterns and component libraries. If your design system has accessibility gaps, every product built on it inherits them. Design needs to see audit results to update shared patterns.

Legal and compliance care about the claims you make. They’ll want to understand what “Supports” versus “Partially Supports” means and how findings translate to risk. Plenty of the teams we work with route ACRs through legal before publishing.

Customer success and sales need to know what documentation exists and how current it is. They shouldn’t be discovering gaps in the middle of a request for proposal (RFP).

The common failure is treating accessibility as an engineering task alone. Organizations that name a single owner move faster.

What Scope Should a SaaS VPAT Cover?

A SaaS VPAT should cover the core application, authentication and onboarding, help documentation, and any third-party components users interact with. If people use your product on mobile, include that too. Define the scope explicitly and document what’s excluded, so procurement doesn’t have to ask.

Core application functionality is the baseline. Dashboards, data entry, reporting and configuration. If it’s behind the login, it’s likely in scope.

Help content and documentation often get missed. If users rely on a knowledge base, embedded help or PDF guides, those need testing. Inaccessible support content creates barriers even when the product itself works.

Authentication and onboarding are high-risk areas because they’re the first thing users hit. If someone using a screen reader can’t complete signup or a password reset, nothing else in the product matters to them.

Third-party integrations and embedded components are complicated. You may not control the code, but you’re responsible for the experience. If you embed a chat widget or payment form, its accessibility becomes your problem.

Mobile and responsive experiences matter if that’s how people use your product. A VPAT that covers only desktop when your users work from tablets leaves gaps procurement will notice.

What Slows SaaS Teams Down During VPAT Preparation?

The usual delays are accessibility debt in the design system, misplaced trust in third-party component libraries, complex custom interactions, slow test account provisioning, and a product that keeps changing mid-audit. Teams with simpler products and clear ownership get through preparation much faster.

Design system debt is the most common bottleneck. If shared components have problems like missing keyboard support or broken focus states, every product surface inherits them. Fix the system and you fix everything built on it.

Third-party component libraries create false confidence. “We use Material UI” isn’t evidence of accessibility. Libraries vary widely in conformance and the defaults often need customization, so test what you actually ship.

Custom interactive patterns need manual verification. Drag and drop, complex data grids, multi-step wizards and real-time collaboration are where automated tools miss problems. If your product stands out on interaction design, expect more manual testing time.

Authentication and role-based access complicate the logistics. Auditors need access to every user role and permission level. If provisioning test accounts means filing IT tickets, build that into your timeline.

Rapid releases create a moving target. If you ship weekly, the product changes during the audit, so decide up front whether to freeze the scope or accept that some findings will need re-verification. Feature flags and A/B tests add to it, and someone has to define what the “real” product is for audit purposes.

What Do SaaS Teams Misunderstand About VPATs?

“We’ll just run an automated scan.” Automated tools catch roughly 30% of WCAG issues. They can’t tell whether a screen reader user can finish a multi-step workflow or hear dynamic content when it changes, so a VPAT built on automated results won’t survive procurement scrutiny.

“We just need a template.” The VPAT is a reporting format, not a solution, and filling it out accurately takes evidence from real testing. Reviewers in government and higher education have seen enough weak VPATs to know what thorough looks like.

“Our component library claims WCAG conformance.” Library marketing isn’t evidence. How you implement and customize components, and how they interact in your product, decides conformance, and the VPAT has to reflect that.

“We’ll mark the gray areas as supported and explain later.” Reviewers can tell. They respect an honest “Partially Supports” or “Does Not Support” with a clear explanation far more than optimistic ratings that fall apart on the first test.

“We’ll handle this when a deal requires it.” Enterprise procurement timelines don’t wait for audits. If a contract needs documentation in 30 days and you haven’t started, you’re already late.

What Does Good Evidence Look Like for VPAT Claims?

A credible ACR rests on tested workflows, real assistive technology coverage, findings someone else can reproduce, and a clear version and date. The goal is enough evidence that a procurement reviewer can trust the claims without a novel attached.

  • Tested workflows, not page lists. Can a user complete onboarding, enter data and run reports without a mouse? Workflow-level evidence matters more than page-level scans.
  • Assistive technology coverage. Testing with at least one screen reader (commonly JAWS, NVDA or VoiceOver) plus keyboard-only and voice control use, such as Dragon, shows real-world validation.
  • Reproducible findings. Notes should give steps to reproduce each issue, not just “contrast failed on settings page.” That helps your team fix things and shows rigor.
  • Version and date stamps. Audits are point-in-time. State what version was tested and when, so procurement knows whether the ACR reflects the current product.

What Happens After the VPAT Exists?

Expect procurement follow-up questions. Reviewers may want remediation timelines for “Partially Supports” items or a look at your accessibility roadmap. Internal owners who can answer quickly make a difference.

A stale ACR invites skepticism, and keeping it fresh makes the next update faster because less has drifted.

Remediation doesn’t end with the audit. The audit finds issues, and fixing them is separate work. You need a realistic plan for anything rated “Does Not Support” or “Partially Supports.”

Long term, the teams that sustain accessibility build it into design reviews and release criteria. Then the VPAT is one output of a real capability instead of a one-time project.

How Often Should a SaaS VPAT Be Updated?

Update it after major product releases, and at least once a year. Buyers get wary of an ACR that’s more than a year old, especially for a product that ships often. Teams with fast release cycles often refresh quarterly, and that goes much faster when accessibility is already part of the development workflow.

Frequently Asked Questions

How long does it take to get a VPAT for a SaaS product?

It depends on product complexity and how much remediation you need. The audit itself typically takes 2 to 4 weeks, and internal preparation like setting scope and provisioning test access often adds several more. If you’re responding to RFPs, plan well ahead of the deadline.

Can we write our own VPAT in-house?

Technically yes, but procurement reviewers give more weight to ACRs from independent third-party evaluators. Self-authored VPATs invite questions about objectivity and often contain errors from unfamiliarity with WCAG details. Independent documentation signals rigor.

Do we need separate VPATs for the US, EU and Canada?

Not always. One thorough WCAG 2.2 Level AA audit can support every edition, but the report format changes by market. US federal buyers expect the 508 edition, EU buyers expect the EU edition built on EN 301 549, and Canadian federal buyers work from CAN/ASC-EN 301 549, the Canadian adoption of the same standard. The INT edition covers Section 508, EN 301 549 and WCAG in one document, which is the simplest answer when your buyers in all three markets actually ask for it.

How do we handle third-party components in our VPAT?

If users interact with third-party widgets, embeds or integrations inside your product, those are in scope. You’re responsible for the experience regardless of who owns the code. Document the components and note any gaps, with remediation plans where you have them.

What if our product can’t fully conform to WCAG 2.2 Level AA?

Say so. Use accurate conformance ratings like “Partially Supports” or “Does Not Support” with clear explanations of the gaps and your remediation plans. Procurement reviewers respect transparency and specific timelines over vague claims.

Should we update our VPAT every time we release a feature?

Not every release needs a full update, but major changes like new workflows or rebuilt components should trigger an ACR review. A yearly review on top of that keeps the date current.

Wrap Up

If your product team is staring down an RFP with a VPAT requirement, the fastest path is an audit by the people who’ll also write the report. The VPAT is the artifact. The capability behind it is what makes it credible.

See how our VPAT and ACR services work. You can get the blank template free from ITI’s VPAT page.