VPAT & Accessibility Conformance Reports
VPAT/ACR Services for Software and Digital Products
CompliCorp helps organizations evaluate digital products, document accessibility conformance, and prepare procurement-ready Accessibility Conformance Reports using the appropriate VPAT® edition. Our VPAT services connect testing evidence, remediation opportunities, conformance decisions, and buyer-facing documentation.
Testing and delivery
VPAT audit, testing, and ACR preparation
We identify the product version, required standards, and appropriate VPAT edition before testing. The completed ACR explains conformance for each relevant criterion, with remarks describing supported functionality and known barriers. We can also help your team answer technical follow-up questions from buyers and plan report updates after remediation.
Standards and reporting
The VPAT is a template published by the Information Technology Industry Council (ITI); the completed report is an ACR. WCAG and Section 508 reporting requirements depend on the edition selected. We confirm the requested edition and standards before the engagement.
Standards references: W3C WCAG overview · U.S. Access Board Section 508 standards · ITI VPAT resources
Planning the next step
Federal procurement may require Section 508 testing, including provisions beyond WCAG. For a web product, the evidence can begin with a manual WCAG accessibility audit.
Building or maintaining a product on a client’s behalf? Our accessibility services for digital agencies explain how testing and ACR preparation can fit into your client engagement.
For testing, buyer documentation, and a remediation roadmap in one coordinated engagement, explore the CompliCorp Procurement Readiness Program.
To understand the evaluation behind the report, read our comparison of accessibility audits and VPAT/ACR documentation.
Scope of work
- Buyer requirements, product version, and the appropriate VPAT edition
- Manual accessibility evaluation and review of supporting test evidence
- Criterion-by-criterion conformance ratings and explanatory remarks
- Accessibility questionnaires and technical procurement questions
- Report updates following product changes or remediation
Your proposal identifies the standards, test coverage, deliverables, and exclusions. Reports describe the evaluated product version and the work performed.
When procurement asks for your VPAT
Procurement reviewers may check whether the ACR describes the product they intend to buy, covers their required standards, and provides credible evidence for its ratings. Make the report date, product version, methods, ratings, and limitations easy to find.
An RFP, vendor onboarding request, contract renewal, or customer questionnaire may ask for a completed VPAT. Start with the actual request: the product and version, buyer's criteria, report edition, and submission date. CompliCorp connects those requirements to a defined evaluation and an ACR that explains the results.
SaaS, EdTech, healthcare technology, financial software, and enterprise vendors may encounter these requests when selling to institutions with accessibility review processes. The buyer's requirements determine the reporting scope; an industry label alone does not mean every vendor has the same obligation.
For federal ICT purchasing, Section508.gov describes how agencies can request an updated ACR during market research and review vendor accessibility claims. The requirements of a particular solicitation still govern the response.
Use our guide to what procurement teams look for when reviewing a VPAT/ACR to check product scope, evaluation methods, ratings, and supporting evidence before sharing your report.
- Report date, evaluated product and version, and whether the report still reflects the product offered
- VPAT edition, applicable standards, evaluation methods, and supporting evidence
- Criterion-by-criterion conformance levels, remarks, and explanations
- Known accessibility limitations and their effect on the buyer’s intended use
Source: Section508.gov: accessibility in federal procurement
What buyers actually receive
A useful ACR identifies what was tested and explains both supported functionality and known limitations. We document the evaluation methods, scope, product version, applicable conformance ratings, and remarks. Findings give your team a basis for discussing open issues and planning improvements.
If a buyer questions an existing report, share both the report and the reviewer's comments. We identify whether the gap concerns the edition, unsupported claims, missing coverage, product changes, or actual accessibility barriers, then define the testing and reporting work needed. Independent evaluation provides an additional evidence source; it does not guarantee buyer acceptance.
The proposal defines the testing coverage and deliverables for your engagement. Our Accessibility Conformance Report services can include:
- Accessibility evaluation evidence. Findings from the agreed product scope and testing methodology, with coverage and limitations identified.
- Conformance determinations. Criterion-by-criterion ratings against the requirements in the selected VPAT edition.
- Remarks and explanations. Clear descriptions of supported functionality, known limitations, and relevant product behavior.
- Evaluation-method documentation. A record of how the product was tested, including manual, automated, and assistive-technology methods where applicable.
- Procurement-ready ACR. A completed report that accurately reflects the evaluated product and version, prepared for the buyer’s review.
- Review meeting. A walkthrough of findings, conformance decisions, known limitations, and next steps with your team.
How CompliCorp creates an ACR
Accessibility testing is needed before completing a VPAT: the ACR’s ratings and remarks must be supported by evidence about the product. Existing test results can inform the work when their scope, methods, and product version are suitable; gaps require additional evaluation.
- Confirm the procurement requirement. Identify the buyer, applicable standards, product and version, requested VPAT edition, and submission deadline.
- Evaluate the product. Perform the agreed manual and assistive-technology testing, with supplemental automated checks appropriate to the product and scope.
- Identify remediation opportunities. Explain material accessibility barriers and opportunities to address them before the report is finalized, where timing and scope allow. Implementation and retesting are agreed separately; a planned fix does not change a rating until it is verified.
- Determine conformance. Map evaluation evidence to each applicable criterion and select the conformance level supported by the findings.
- Prepare the ACR. Complete the appropriate VPAT template with the product details, evaluation methods, conformance ratings, and clear remarks.
- Review and maintain. Walk through the completed report and identify product changes that may require an update. Ongoing report maintenance and buyer follow-up are included when specified in the proposal.
Choose the VPAT edition your buyer needs
The VPAT® is ITI’s reporting template; an ACR is the completed report. Choose the edition that covers the buyer’s requirements and the standards applicable to your product. The WCAG, Revised Section 508, EU, and INT editions have different coverage; INT is not automatically the best choice. We confirm the edition and current template before testing.
Federal ICT can involve hardware, software, documentation, and support provisions beyond a web audit. Our Section 508 testing service addresses that broader scope. For an explanation of the documents themselves, see VPAT versus ACR.
ITI’s current VPAT 2.5Rev templates are available in four editions:
| Edition | Coverage | When to discuss it |
|---|---|---|
| WCAG | WCAG 2.0, 2.1, and 2.2 | Reporting against the WCAG version and conformance level the buyer specifies |
| Revised Section 508 (508) | Revised Section 508 Standards, incorporating WCAG 2.0 | U.S. federal ICT procurement and Section 508 reporting, including applicable requirements beyond WCAG |
| EU | EN 301 549, incorporating WCAG 2.1 | European accessibility reporting where the buyer requires EN 301 549 |
| INT | Combined Section 508, EN 301 549, and WCAG coverage, including WCAG 2.2 | Combined reporting when the buyer requires multiple major accessibility standards |
VPAT/ACR support for SaaS companies
A SaaS company can use a VPAT-based ACR to respond to an enterprise procurement request when the report covers the product and standards the buyer needs. Higher-education institutions, government agencies, and other customers may also request accessibility documentation; confirm the actual requirements before commissioning a report.
For SaaS and software products, CompliCorp helps define the evaluation scope, test agreed workflows and user roles, document current conformance, and prepare the appropriate ACR. Our Procurement Readiness Program can coordinate testing, documentation, and remediation planning when the review calls for broader support.
When should an ACR be updated?
Update an ACR when product changes or reporting requirements mean it no longer accurately represents the product being sold. There is no universal expiry date; check any report-age requirements set by the buyer and review the ACR for the changes below.
Retesting after remediation can support updated ratings and remarks. Include report updates and buyer follow-up support in the engagement scope when those deliverables are needed.
- A significant product release changes evaluated functionality or introduces new workflows
- Verified accessibility remediation materially changes conformance
- The product or version named in the report is no longer current
- Buyer or procurement requirements change
- Relevant standards or reporting requirements change
- The report otherwise stops accurately describing the product being sold
Source: Section508.gov: ACR and VPAT questions, including report updates
Learn about CompliCorp and founder David LoPresti, or review our evaluation and delivery process.
Service questions
Frequently asked questions.
Scope, deliverables, and what to expect from your engagement.
What do customers mean when they ask us for a VPAT?
They usually want the completed Accessibility Conformance Report, or ACR. VPAT® is ITI’s standardized template; the ACR is the report that documents a specific product’s evaluated conformance. Ask the customer which product, version, edition, and requirements they need covered. Our VPAT and ACR guide explains the terminology before you commission or share a report.
What does CompliCorp's VPAT testing and reporting service include?
We agree on the product scope and reporting requirements, evaluate accessibility, and prepare an ACR supported by the test evidence. The report identifies the evaluated version, methods, conformance ratings, and remarks explaining limitations. Detailed findings and a review with your team are part of the agreed deliverables. Remediation, retesting, subsequent report revisions, and buyer follow-up support are specified in the proposal when included.
Which VPAT edition should we choose?
Choose the edition that covers the standards the buyer requests. ITI provides WCAG, 508, EU, and INT editions; their coverage differs. For example, a WCAG-only report may omit ICT provisions needed for a Section 508 review. Send the actual request or solicitation so we can confirm the edition and the evaluation behind it. The edition comparison on this page explains the main options.
How is the price of a VPAT audit determined?
Pricing reflects the product's functions, platforms, user roles, and reporting requirements. A public website and a multi-role application with authoring tools require different evaluations. Existing evidence may help, but its scope, age, and relevance need review. We identify testing, ACR preparation, and any follow-up services in a scoped quote so you can see exactly what the price covers.
What affects the time needed to produce an ACR?
The schedule depends on access, product complexity, test coverage, and the review required before delivery. Missing user roles, unstable builds, and incomplete workflows can delay evaluation. If you plan to correct issues before the report is finalized, allow time for implementation and retesting. Share the buyer's deadline early so we can distinguish an initial report of current findings from a later update after fixes.
Can we have an ACR if the product still has accessibility issues?
Yes. An ACR can disclose both supported functionality and known barriers. Ratings and remarks must accurately reflect the evaluated product, including limitations. A planned fix should be described separately from a verified correction. The buyer decides how the findings affect its procurement; a completed report does not guarantee acceptance. Remediation planning helps organize the work behind future report updates.
Does a VPAT certify that a product is accessible?
No. A VPAT is a reporting template, and the completed ACR documents the product’s evaluated level of conformance. An ACR is not a certification and does not itself guarantee full conformance with every applicable requirement. Buyers need accurate ratings, useful explanations, and evidence that relates to the product they are purchasing.
Can our team complete its own VPAT?
Yes, provided it can evaluate the applicable requirements and support the report's conclusions. Completing the template requires more than selecting ratings: someone needs to define coverage, interpret findings, and explain exceptions clearly. Independent assessment can help when the team lacks testing capacity or needs a separate review. The report's usefulness depends on the evidence and accuracy, regardless of who prepares it.
What should we do when a buyer challenges our ACR?
Start with the buyer's specific concern and compare it with the report, tested product version, and supporting evidence. The issue might be missing coverage, unclear remarks, an outdated report, or an actual product barrier. We can scope the additional testing and corrections needed. A wording change is appropriate only when it improves an accurate explanation; it cannot turn an unresolved defect into supported functionality.
Does a SaaS vendor need a separate ACR for every customer?
Not necessarily. One report can support multiple reviews when it accurately describes the same product, version, configuration, and required standards. Customer-specific features, deployments, or integrations can change that scope. Confirm what the buyer will use and whether its requirements differ. Our software accessibility services address the workflows and roles that may need evaluation beyond a vendor's public marketing site.
How often should an Accessibility Conformance Report be updated?
Review the ACR when product changes or verified fixes affect its findings, and check any freshness requirements set by the buyer. There is no universal expiry date that makes every report valid for a fixed period. Keep the report tied to a product version and test date. An update may require targeted retesting or broader evaluation depending on what changed.
Related accessibility services
Industry applications
Planning resources
Discuss your accessibility project
Need an accessibility audit or VPAT?
Tell us what you need tested, which requirements you need to meet, and when you need the results.