accessibility compliance

VPAT for SaaS: How to Produce a 2.5Rev ACR Buyers Will Trust

VPAT for SaaS: How to Produce a 2.5Rev ACR Buyers Will Trust

get in touch

Know where you stand. Know what to work on next.

Tell us what you’re working on and where you need support. Our accessibility specialists can help with audits, remediation, VPAT/ACR, accessible development, and ongoing compliance.

Free 30-minute consultation (opens in new tab)

Free 30-minute call: talk through where you stand, scope a project or get a quote.

Need technical answers now? Book the $100 one-hour consultation to walk through an audit, talk with a developer or review your site live.

Let’s find the barriers before your users do

Indicates a required field.


Your information is kept private and never shared with third parties.

A VPAT for SaaS is not a certificate and not a marketing PDF. The ITI Voluntary Product Accessibility Template (VPAT®) is a free reporting form. Once you fill it with tested results for a named product version, that completed document is an Accessibility Conformance Report (ACR), the format federal and enterprise buyers use to compare how your software supports accessibility standards. Buyers trust ACRs that name the product version, describe real evaluation methods, use honest conformance levels, and explain every partial or unsupported criterion.

This guide is written by accessibility testers who audit and remediate SaaS products for a living. It is not legal advice. It walks through how SaaS teams pick a VPAT 2.5Rev edition, scope what to test, write remarks that survive procurement review, and sequence audit → remediation → ACR so sales is not stuck with a stale or overstated report.

VPAT For SaaS At A Glance

Choose Your Next Step

Most SaaS teams start with a free call to work out which VPAT edition the buyer wants, what to test and when the ACR is due. Teams with an RFP date can request a VPAT quote. If you need test evidence first, our pricing lists the $500 Quick Audit and the $2,000 Complete Audit, and the SaaS B2B accessibility page shows how we test product workflows.

Free 30-Minute Call

Best for: SaaS teams who just got a VPAT request and are working out scope, edition or timing

A first conversation with our founder about where your product stands, which edition the buyer needs and what has to be tested before an honest ACR can be written. No prep needed.

Book a free 30-minute call (opens in a new tab)

VPAT & ACR Quote

Best for: teams with an RFP, a named edition and a delivery date

Manual testing of your sign-in, core workflows and admin screens against the edition you will file, then an ACR with remarks a procurement reviewer can check.

Request a VPAT quote

$100 Technical Consultation

Best for: teams with an ACR draft, audit findings or a developer to bring

A one-hour hands-on session to review conformance levels and remarks, walk through findings or check live issues in your product with your engineers. Not for first-time scoping.

Book the $100 technical hour

What VPAT vs ACR Means (ITI Definitions)

ITI is clear on the vocabulary:

VPAT and ACR terms, as ITI defines them
Term or questionWhat ITI says
VPAT®The blank template ITI publishes, free to use.
ACRA VPAT completed for a specific product is an Accessibility Conformance Report (ACR).
CertificationITI does not review, approve, or certify VPATs. There is no VPAT certification and no conformance logo.
Membership and namingMembership in ITI is not required. The VPAT name and report form are ITI registered service marks and should not be altered without ITI permission.

GSA’s Section508.gov sell guidance describes the ACR as the document that explains how ICT (software, hardware, electronic content, and support documentation) meets the Revised Section 508 Standards so federal contracting officials can assess accessibility during market research and proposal evaluation. For SaaS sellers, that means the ACR is a procurement artefact, not a substitute for fixing barriers.

If you need the wider map of WCAG, ADA, Section 508, EN 301 549, EAA, and VPAT, see our framework comparison: Which accessibility framework actually matters?.

Why SaaS Buyers Ask for a VPAT / ACR Now

Four kinds of buyer send most VPAT requests to SaaS vendors. Each one reads the ACR for something slightly different.

Federal and Section 508 procurement

U.S. federal agencies must procure accessible ICT under Section 508.

  • Recommended: Section508.gov recommends vendors generate an ACR for ICT marketed to the federal government.
  • Edition: its how-to guide says to use the Revised Section 508 or INT (International) edition for federal sales.
  • Not optional: the ACR/VPAT FAQ says the template is voluntary, but an ACR is needed if you want to be considered for purchase (absent a government-claimed exception).

Enterprise and education RFPs

Large commercial and higher-ed buyers often copy federal-style accessibility language into RFPs.

  • They ask for: a current ACR, the product version tested, evaluation methods, and a plan for known gaps.
  • What wins: a dated, criterion-level ACR beats an empty “we follow WCAG” sentence every time.

Title II covered entities buying SaaS tools

Public entities have their own web rule, so they check the tools they buy.

  • ADA: DOJ’s web guidance explains that Title II and Title III entities must provide accessible web content.
  • Deadlines: Title II entities face a WCAG 2.1 AA web and mobile rule; see our DOJ Title II web accessibility deadline post.
  • Limit: that buyer pressure is real; it does not create a private-SaaS VPAT deadline.

EU / EN 301 549 and EAA pressure (secondary)

European public procurement and EAA-covered services push buyers toward EN 301 549–aligned reporting.

If an RFP already names a VPAT edition and a delivery date, request a VPAT quote or start from our VPAT / ACR documentation and SaaS B2B software accessibility pages so audit scope matches what procurement will read. Not sure yet? A free 30-minute call (opens in a new tab) sorts the scope first.

Buyer channels that trigger a VPAT for SaaS Accessibility Conformance Report

Which VPAT 2.5Rev Edition to Pick

As of April 2025, ITI publishes VPAT® Version 2.5Rev in four editions (ITI VPAT page):

EditionBuilt forWCAG version in that edition
VPAT 2.5Rev WCAGBuyers who want WCAG reportingWCAG 2.0, 2.1, and 2.2
VPAT 2.5Rev 508U.S. federal / Revised Section 508WCAG 2.0 (as incorporated into 508)
VPAT 2.5Rev EUEN 301 549 / EU public procurementWCAG 2.1 (as incorporated into the EU edition)
VPAT 2.5Rev INTMulti-market / “cover everything” RFPsIncorporates 508 + EU + WCAG (includes WCAG 2.2 in the WCAG portion)
Practical SaaS edition picks, by what the contract says
If the RFP or contract says…Pick this edition
Federal opportunity, or Section 508 called out508 edition, or INT if the same ACR must also speak to EU/WCAG buyers (Section508.gov how-to)
Commercial / edu RFP asking for a “WCAG 2.2 AA ACR”WCAG edition (or INT)
EU public sector, or EN 301 549 namedEU edition (or INT)
One ACR for global enterpriseINT, knowing it is longer and costlier to keep current

Do not invent a fifth conformance story. Match the template to the contract language. For edition-specific testing help, HalfAccessible offers ADA / Section 508 accessibility audits and EU accessibility compliance audits.

Scope What to Test in a SaaS Product

An ACR that only covers the marketing site will fail the first procurement follow-up. Scope the product version named on the ACR title page, typically the production SaaS release buyers will log into. This is the minimum test surface for a credible ACR:

Minimum SaaS test surface for a credible ACR
Product areaWhat to test
AuthenticationSign-up, sign-in, SSO, MFA, password reset, session timeout messaging
Core customer workflowsThe journeys that close deals (create → edit → share → export, or equivalent)
Admin / settingsRoles, billing, integrations, feature flags that customers actually configure
Support content you ownIn-app help, knowledge base articles you publish, PDF exports (Section 508 Chapter 6 covers support documentation and services when applicable)
Third-party embedsChat widgets, analytics overlays, payment iframes, media players you ship in the product chrome
Responsive / mobile webIf customers use the product on phones and tablets; native apps can sit in the same ACR or a separate one (the Section508.gov FAQ allows one ACR covering software, documentation and a mobile app)

Name evaluation methods on the ACR: automated ruleset (if any), keyboard-only passes, screen reader platforms (for example NVDA (opens in a new tab), JAWS, VoiceOver), browsers, and whether testing was on production, staging, or a documented build. Section508.gov expects that field completed. Pair scanner output with manual testing: ADA.gov’s web guidance notes that automated checkers need careful use and that a “clean” report does not necessarily mean everything is accessible, and W3C WAI selecting tools guidance (opens in a new tab) reminds teams that evaluation tools cannot check every accessibility aspect.

For React-heavy SaaS frontends, bake fixes into shared components via accessible React development so the next ACR refresh is not a heroics cycle.

SaaS product areas to include when scoping a VPAT Accessibility Conformance Report

Honest Conformance Levels and Remarks That Will Not Get You Redlined

ITI’s VPAT 2.5Rev uses four conformance levels (ITI; definitions also summarised by Section508.gov):

VPAT 2.5Rev conformance levels and when a remark is needed
LevelWhat it meansRemark needed?
SupportsAt least one method meets the criterion without known defects (or meets with equivalent facilitation)Encouraged
Partially supportsSome functionality does not meet the criterion (this replaced the older “supports with exceptions” wording at the Access Board’s request, per ITI)Yes
Does not supportThe majority of product functionality does not meet the criterionYes
Not applicableThe criterion is not relevant to the productSay why, briefly

Section508.gov requires remarks when the level is partially supports or does not support. Remarks are encouraged even when you support a criterion.

Remarks buyers accept, and remarks that get redlined
Write remarks that…Avoid remarks that…
Name the affected feature or role (for example, “Admin → Integrations table: column sort buttons lack accessible names”)Mark “Supports” on criteria you never tested
Tie the gap to a WCAG or 508 criterionCopy-paste “N/A” across interactive UI
State who is blocked (keyboard-only, screen reader, low vision) without dramaBlame the user’s assistive technology
Note a workaround if one exists and is actually usableClaim ITI or a scanner “certified” the product (ITI says there is no VPAT certification)
Point to a roadmap item or ticket ID when remediation is fundedInvent a ship date you cannot keep

GSA also notes that even a product that conforms to relevant standards may still be difficult for some users, and a product that is not fully conformant may still work for others. The ACR’s job is accurate disclosure so buyers can compare options (ITI; Section508.gov FAQ). Incomplete accessibility does not automatically bar federal purchase; buyers compare ACRs. Silence loses.

Audit → Remediate → ACR: The Sequence That Protects Sales

Do not start by typing “Supports” into a blank Word file. Credible SaaS ACRs follow a fixed order:

The six-step sequence for a SaaS ACR
StepWhat happensWhere we help
1. Baseline auditManual + assistive technology testing against the edition you will fileAccessibility audit services, the $500 Quick Audit, or see a sample audit report
2. Remediate shared UIDesign system, auth shell, data tables, modals, toastsAccessibility remediation
3. RetestThe same scope with the same methodsRe-test after fixes (included in the $2,000 Complete Audit)
4. Author the ACROn the current ITI 2.5Rev editionVPAT / ACR documentation
5. Publish or deliverProduct page link for federal buyers (Section508.gov recommends making the ACR easy to find) plus NDA’d RFP packages when requiredACR wording review in a $100 technical hour
6. GovernTickets for residual “partially supports” rows so sales does not promise fixes engineering never scheduledAccessibility monitoring and governance

Target engineering hygiene at WCAG 2.2 Level AA even when a 508 edition still tabulates WCAG 2.0: you report against the edition’s tables, but building ahead reduces rework when buyers ask for 2.2 evidence.

Audit remediate ACR sequence for SaaS accessibility conformance reporting

Refresh Cadence (Best Practice, Not an ITI Mandate)

ITI does not publish a mandatory annual VPAT renewal clock. Treat refresh as product hygiene tied to change:

When to refresh a SaaS ACR
TriggerWhat to do
Product changed or updatedThe Section508.gov ACR/VPAT FAQ says every time your product is changed or updated (version change, bug fix, and similar), an updated ACR may be required.
ACR written to the 2001 Section 508 standardsRedo it against the Revised Section 508 Standards (2017), per the same FAQ.
Major release touching auth, navigation or high-traffic workflowsRetest those areas and refresh the affected rows.
A buyer RFP demands a report newer than N monthsRefresh before you submit, not after.
No change for a yearSchedule at least an annual review so sales never hands out an ACR for a version you no longer ship.

Keep the report date, product version, and evaluation methods truthful. A beautiful ACR for last year’s UI is a liability.

Get a VPAT for SaaS Buyers Will Actually Read

Enterprise and government deals stall when the only accessibility artefact is a vague WCAG claim. A trustworthy VPAT for SaaS path is straightforward: pick the April 2025 edition that matches the RFP, scope real product workflows, test with assistive technology, remediate shared UI, then file an honest ACR with remarks you can defend.

HalfAccessible helps SaaS teams run that sequence end to end: accessibility audits, remediation, accessible React development, and VPAT / ACR documentation scoped for SaaS B2B software. See how that looks on a live product in our VPAT for SaaS Happeo case study and the sibling accessibility audit and VPAT for SaaS engagement.

Work is led by our founder, Shadab Saifi, who holds the IAAP (opens in a new tab) CPACC, WAS and CPWA certifications and has audited, fixed and built accessible websites for 10+ years. Testing uses assistive technology such as NVDA (opens in a new tab), not scanners alone. Still working out scope? Book a free 30-minute call (opens in a new tab). Have an ACR draft or findings to review with your developer? Book the $100 technical consultation. Ready to price it? Request a VPAT quote, review accessibility audit pricing, browse all accessibility services, or open a sample audit report to see how findings become ACR-ready evidence.

Frequently Asked Questions

What is the difference between a VPAT and an ACR?

Per ITI, the VPAT is the blank template; a completed VPAT for a specific product is an Accessibility Conformance Report (ACR). Buyers ask for an ACR (sometimes still saying “send your VPAT”). HalfAccessible turns tested evidence into VPAT / ACR documentation for SaaS products.

Is there a VPAT certification for SaaS?

No. ITI states there is no VPAT certification, no ITI approval step, and no conformance logo. Third-party accessibility audits can strengthen evidence when a solicitation requires them, but they are not an ITI certificate.

Which VPAT 2.5Rev edition should a SaaS company use?

Match the buyer. Federal / 508 → 508 or INT. WCAG 2.2 commercial RFPs → WCAG or INT. EN 301 549 / EU procurement → EU or INT. ITI documents which WCAG version each edition incorporates (2.0 in 508, 2.1 in EU, 2.2 in WCAG and INT). For edition-specific testing, see our ADA / Section 508 accessibility audit and EU accessibility compliance audit.

Can we publish an ACR if the product is not fully accessible?

Yes. Section508.gov encourages completing an ACR even when not all applicable standards are met, so buyers can compare products. Use partially supports / does not support with clear remarks — do not mark supports for untested criteria. Known gaps should feed accessibility remediation before the next refresh.

Does an ACR prove ADA compliance for private SaaS?

No. An ACR documents tested conformance to the standards listed in the chosen VPAT edition. ADA.gov describes broader ADA web accessibility expectations for Title II and Title III entities. This post is not legal advice; counsel should review how you describe legal compliance in contracts.

How often should we update our SaaS ACR?

Update when the product changes in ways that affect accessibility, when buyers require a fresh report, and on a planned annual review at minimum. Section508.gov notes an updated ACR may be required after version changes and bug fixes. Book a consultation to plan a refresh cadence that matches your release train.

Who should fill out the VPAT — vendor, reseller, or auditor?

ITI says the OEM / product owner is usually best placed to complete it because they know the product; resellers or vendors may complete it depending on who can speak accurately. Follow solicitation rules if a third-party review is required. Our SaaS B2B software accessibility specialty covers product-owner and auditor workflows.

What goes in Evaluation Methods Used?

Describe how you tested: automated tools (if any), manual keyboard testing, screen readers and versions (we routinely include NVDA), browsers, devices, and environments. Section508.gov’s how-to lists evaluation methods as a required title-page field. W3C WAI notes tools alone cannot cover every criterion.

What is included in a VPAT for SaaS engagement?

A typical path is baseline accessibility audit (manual + assistive technology), optional remediation of shared UI, then authoring on the current ITI 2.5Rev edition via VPAT / ACR documentation. See the Happeo VPAT for SaaS case study for a 7-day procurement-ready example, and pricing for audit starting points.

How long does a SaaS ACR take, and what does it cost?

Timeline depends on product scope, edition (WCAG / 508 / EU / INT), and whether remediation lands before the report. A focused SaaS ACR can complete in days once testing evidence exists, as in our Happeo case study. Cost tracks audit depth, not a flat “VPAT fee”; start from accessibility audit pricing (the $500 Quick Audit or the $2,000 Complete Audit for test evidence), book a free 30-minute call to scope it, or submit a VPAT quote request for a scoped quote within 1 to 2 business days. We do not invent fixed VPAT prices here.

Should we start with the free call or the $100 consultation?

Start with the free 30-minute call if you have just received a VPAT request and are still working out the edition, scope or deadline. It is a first discussion with our founder to understand where your product stands and to start the project. Book the $100 one-hour technical consultation when you already have an ACR draft, audit findings or a vendor report to go through, or want your developer on a live session to check product issues.

Can an automated scan produce our ACR?

No. An ACR needs a conformance level and remarks for every criterion in the edition you file, plus a truthful Evaluation Methods Used field. A free scan such as AccessibilityScore.in (axe-core based, one public page) is a useful starting point to find common code-level issues, but its own FAQ says manual review is needed to confirm keyboard access, screen reader behaviour, forms and complete user journeys. Use it to triage, then run the manual testing an honest ACR depends on; our automated accessibility testing guide explains where scans stop.

Written by Shadab Saifi Published Last updated

Related Articles

View all