CompliCorp Procurement Readiness Program

Accessibility Procurement Readiness for Software Vendors

CompliCorp helps software companies prepare the accessibility evidence, documentation, and internal answers buyers may request during RFPs, vendor reviews, renewals, and procurement evaluations.

We connect accessibility testing, VPAT/ACR documentation, remediation planning, and procurement responses so your team can answer buyer questions accurately and consistently across enterprise, education, government, and regulated-sector reviews.

Talk to an accessibility expert Send us your requirements

Short answer: Accessibility procurement readiness means having current, defensible accessibility evidence before a buyer asks for it. That may include product testing, a current VPAT-based ACR, evaluation methodology, known limitations, remediation plans, accessibility statements, and clear responses to buyer questionnaires or RFP requirements.

Key takeaways

Procurement teams may ask for more than a VPAT.
Accessibility claims should match the product currently being sold.
Testing evidence and ACR statements should align.
Known limitations should be explained accurately rather than hidden.
Accessibility documentation should be reviewed as products and buyer requirements change.

The buyer’s perspective

A VPAT is often only the beginning.

Buyers may ask for a VPAT® or Accessibility Conformance Report (ACR). They may also want to understand how your product was evaluated, where limitations exist, how those issues affect users, and what your organization is doing to address them.

CompliCorp brings those pieces together into a credible accessibility package for procurement conversations, RFPs, compliance reviews, and enterprise sales.

A generic or unsupported conformance statement may create more questions than it answers. We help your team develop the evidence, documentation, and remediation strategy needed to respond with confidence.

For European-market requirements, see our EAA accessibility readiness support. Agencies managing a buyer request for a client can explore our digital agency accessibility partnerships.

Questions your buyers are asking

How accessible is the product today?
How was it evaluated, including assistive technologies?
Which requirements are supported?
Where do limitations remain, and what is the user impact?
Is there a credible remediation plan?
Who is responsible for accessibility?
Will the documentation stay current as the product evolves?

What procurement teams may ask for

Accessibility documentation for procurement depends on the buyer, product, and intended use. Potential requests include:

A current VPAT-based Accessibility Conformance Report (ACR)
The product and version covered by the report
Evaluation methods, test coverage, and dates
WCAG or Section 508 conformance information, as applicable
Assistive-technology testing details
Known accessibility limitations and their user impact
Remediation plans or timelines your organization has approved
An accessibility statement or equivalent customer-facing information
An accessibility contact or accountable owner
Demonstrations or test access
Responses to accessibility questionnaires
Accessible-document or content examples, where relevant to the product

For a report-level review, use our VPAT/ACR review checklist for procurement to identify evidence gaps and useful follow-up questions.

For federal ICT purchases, Section 508 evaluation and reporting should address the applicable solicitation requirements. Federal guidance provides examples of supporting evidence; commercial and other institutional buyers set their own review procedures.

Source: Section508.gov’s vendor-information guidance.

Procurement Readiness Checklist

Is your product procurement-ready?

Use these questions to identify preparation gaps, then compare the answers with your buyer’s actual requirements.

Do we know which product and version our accessibility documentation covers?
Has the product been meaningfully tested?
Is our VPAT/ACR current?
Can we explain the evaluation methods behind it?
Do our ACR statements match current product behavior?
Do we know our most important accessibility limitations?
Is there an owner for remediation?
Can sales answer accessibility questions consistently?
Do we have an accessibility statement or equivalent customer-facing information where appropriate?
Can we respond quickly and accurately to an accessibility questionnaire or RFP?
Do we know when our ACR should be refreshed?

Testing. Documentation. Direction.

What you may leave with

Configure the program around your product, target market, and procurement requirements. Your proposal identifies the evaluation coverage, deliverables, consultation, and follow-up support included in the engagement.

Depending on the agreed scope, deliverables may include:

An accessibility evidence-gap review
A procurement-readiness checklist
A recommended testing scope
A current or updated VPAT-based ACR
Accessibility statement guidance
A remediation roadmap
Responses to accessibility questionnaires
RFP accessibility support
A supporting documentation package
Internal guidance for sales and product stakeholders

Product accessibility evaluation

We evaluate representative workflows, screens, components, and functionality against the accessibility requirements applicable to your product and market. The goal is to establish a clear, evidence-based understanding of the product’s current accessibility.

Explore evaluation coverage

Manual accessibility testing and keyboard-only testing
Screen reader testing, focus, and navigation
Forms, interactive controls, dialogs, menus, tables, and complex components
Color, visual presentation, error handling, and status messaging
Product documentation and support content
Applicable WCAG and Section 508 requirements

Assistive technology testing

We evaluate critical workflows with relevant assistive technologies and accessibility configurations, including screen readers. This provides context that automated testing alone cannot provide and helps identify barriers affecting real-world product use.

The product, platforms, user journeys, and agreed scope determine the testing combinations.

VPAT® / Accessibility Conformance Report

Using the appropriate VPAT® edition for your market and procurement requirements, we prepare a professional ACR based on the evaluation findings. Your sales, compliance, legal, product, and procurement teams receive a report they can use to explain the product’s accessibility.

What the ACR documents

Applicable accessibility requirements and conformance levels
Specific supporting remarks and explanations
Evaluation methodology and scope
Product and version information
Identified limitations where applicable

Procurement supporting documentation

Some procurement processes require more than an ACR. We can help develop a coordinated set of supporting materials so your organization can respond to buyer requests with consistent, accurate information.

Supporting materials available by scope

Supplemental Accessibility Reports (SARs)
ACR Issue Detail Supplements describing severity and user impact
Evaluation methods, accessibility features, and known limitations
Product configuration and installation considerations
Remediation commitments and accessibility improvement plans
Accessibility questionnaires and supplemental procurement responses

We align the materials with the specific buyer request and commitments your organization has approved.

Custom accessibility statement

We develop a professional accessibility statement aligned with the evaluated product and its current accessibility posture. It can reflect your commitment, applicable standards, evaluation approach, known limitations, feedback channels, and ongoing improvement efforts.

The statement complements the underlying testing and ACR.

Prioritized remediation roadmap

An evaluation is more valuable when your product and engineering teams know what to do next. We organize findings into a practical product-improvement plan, connecting technical issues with their impact on users.

How we prioritize the next steps

Issues with the greatest user impact and what to address first
Common patterns responsible for multiple findings
Opportunities for design-system improvements
Development and QA considerations
Recommended validation after remediation

Accessibility document delivery meeting

We don’t simply email the reports and disappear. A structured delivery meeting gives stakeholders a clear understanding of the findings, the documentation, and the work behind it.

What we cover together

Key findings and significant user-impact issues
ACR conclusions and documentation prepared for procurement
Remediation priorities, roadmap, and recommended next steps
Product and engineering questions and remediation best practices

Bring the people responsible for product, engineering, design, QA, compliance, legal, sales, and customer success.

Product and engineering consultation

Accessibility questions frequently arise during remediation. Our team can work with product, engineering, design, and QA stakeholders to interpret findings and discuss practical approaches, helping build accessibility into the product-development process.

ACR refresh and ongoing accessibility support

Software changes. Your accessibility documentation should change with it. We can review the product following remediation, significant releases, redesigns, or material changes in functionality, then update the ACR and related documentation where appropriate.

Follow-up validation and refresh work are scoped around the product changes and your reporting needs.

A clear path forward

How CompliCorp prepares your team for procurement review

Your engagement may include some or all of these steps, depending on the buyer’s request and your existing evidence. The proposal defines the work and deliverables.

Review the buyer requirement
Understand the RFP, questionnaire, contract request, target market, and procurement context. Confirm the product, standards, submission requirements, and deadline.
Review existing accessibility evidence
Assess current audits, VPAT/ACRs, accessibility statements, testing records, remediation plans, and prior buyer responses.
Identify evidence gaps
Determine what is missing, outdated, inconsistent, or unsupported, and agree on which gaps the engagement will address.
Perform or update testing where needed
Define an appropriate evaluation scope and carry out the agreed testing. Documentation must reflect evidence about the product, including its known limitations.
Align documentation and product reality
Update ACRs, explanations, remediation information, and customer-facing materials where included in scope. Separate verified fixes from future plans and approved commitments.
Prepare the team to respond
Give sales, product, procurement, and accessibility stakeholders consistent answers and supporting materials. Identify who owns follow-up questions and future documentation updates.

How audits, ACRs, and procurement readiness fit together

Accessibility evaluation. An accessibility audit produces technical evidence about the evaluated product.
Remediation. Implementing fixes improves the product and addresses identified barriers.
Retesting. Verification establishes whether the agreed fixes resolve the findings.
VPAT/ACR. VPAT/ACR preparation turns evaluation evidence into a report of current conformance. The VPAT is the template; the ACR is the completed report.
Procurement readiness. Organize that evidence alongside buyer responses, known limitations, approved plans, and internal ownership.

This is a common sequence, not a requirement to fix every issue before preparing an ACR. A report can accurately disclose current limitations, with remediation and retesting scoped around the product’s needs.

Our guide to VPATs, accessibility audits, and procurement evidence explains how testing and current documentation support that conversation.

What happens when you are not ready

Missing evidence or inconsistent answers can slow a buyer’s review. Questions may return to engineering during a sales conversation, an outdated ACR may be challenged, or sales, product, and legal teams may give different answers.

A buyer may request additional testing, and teams may find themselves making remediation commitments under deadline pressure. These outcomes are possible, not inevitable; identifying evidence gaps early gives the team more time to respond.

Missing evidence and unresolved product questions can add review time even after a buyer has selected the software. Explore the hidden procurement costs of digital inaccessibility to understand where those delays and internal demands can arise.

Who it’s for

Accessibility procurement readiness for SaaS companies

SaaS vendors may receive accessibility requests from enterprise buyers, higher education, government, healthcare, and other organizations during procurement and renewals. CompliCorp helps your team prepare accurate accessibility documentation and consistent answers for those reviews.

Whether a prospect has just asked for your first VPAT or you need a more mature accessibility program, we can meet you where you are.

Explore our SaaS and software accessibility support for the product workflows, roles, and release changes that may need evaluation.

SaaS and enterprise software
GovTech and public-sector vendors
EdTech and education platforms
Healthcare technology
HR and workforce platforms
Financial technology
Software companies entering public-sector markets
Vendors responding to enterprise accessibility reviews

Prepare before the request

When should a software vendor prepare for accessibility procurement?

Ideally, before an active deal, RFP, renewal, or enterprise buyer creates a deadline. Preparing earlier gives your team time to evaluate the product, address important barriers, update documentation, and agree on accurate internal responses.

For an active request, start with the buyer’s requirements, the product and version offered, existing reports, known limitations, and the people who can approve technical answers and remediation commitments. Preparation supports an informed review; the purchasing decision remains with the buyer.

Program questions

Frequently asked questions.

Planning your first ACR, responding to a buyer, or keeping existing documentation current.

Do we need to be fully accessible before creating a VPAT or ACR?

No. An ACR documents the current accessibility conformance of a product. Requirements that are not fully supported should be accurately described, with supporting remarks about the limitations. CompliCorp can then help your organization develop a remediation roadmap for improving the product over time.

We already have a VPAT. Can you review it?

Yes. We can review an existing ACR alongside the current product to determine whether its claims remain supported by the product’s present accessibility and functionality. If needed, we can recommend updates or scope the testing required to prepare a revised ACR.

Can you help us respond to an accessibility questionnaire or RFP?

Yes. We can review the request, identify the information being sought, and help your team develop accurate supporting responses based on the product’s accessibility evaluation. Share the buyer’s requirements and deadline so we can identify the testing and documentation needed.

Which VPAT edition do we need?

The right edition depends on your target markets and the buyer’s requirements. ITI offers editions covering U.S. Section 508, WCAG, European requirements, and an international combination. CompliCorp recommends the appropriate edition and evaluation scope for the intended use of your ACR. Learn more about VPAT editions and ACR reporting.

Can you work with our engineering team after the audit?

Yes. Product, design, engineering, and QA consultation can be included in the engagement to explain findings, discuss remediation priorities, and support follow-up validation. We agree on the consultation, retesting, and report updates needed for your release plans.

How often should our ACR be updated?

There is no universal refresh interval for every software product. Consider an update after significant functionality changes, accessibility remediation, major releases, changes in applicable requirements, or whenever the existing ACR no longer accurately represents the product. Your buyer may also have requirements for the age of a report.

What is accessibility procurement readiness?

It means having current accessibility evidence, documentation, and internal answers ready for a buyer’s review. The work brings together product testing, ACR reporting, known limitations, remediation plans, and responses to the buyer’s actual requirements. It goes beyond preparing a single report.

What accessibility documents do buyers ask for?

Buyers may request a current ACR, evaluation methods, known limitations, remediation information, an accessibility statement, or questionnaire responses. Some also request demonstrations, test access, or accessible-content examples. The documents needed depend on the product, buyer, and solicitation; there is no single package required by every organization.

Is a VPAT enough for procurement?

Not always. A buyer may need supporting evidence or explanations beyond the completed ACR, particularly if the report is outdated or does not cover the intended use. Confirm the requested standards, product version, and submission requirements, then identify any gaps in the documentation or testing.

Do buyers review the testing behind a VPAT?

They may. Reviewers can ask how the product was evaluated, which workflows and assistive technologies were covered, and what evidence supports the ratings. In federal procurement, Section508.gov guidance includes requests for evaluation methods and the possibility of demonstrations or hands-on testing. Commercial buyer procedures vary.

What should we prepare before responding to an accessibility RFP?

Gather the RFP’s accessibility requirements and deadline, the product and version offered, existing audits and ACRs, and any known limitations or remediation plans. Identify the people who can confirm technical answers and approve commitments. CompliCorp’s accessibility RFP support helps your team identify evidence gaps and prepare responses within the agreed scope.