VPAT government procurement requirements explained: when federal buyers ask for an ACR, what Section 508 covers, and what vendors prepare before bidding.
If you sell digital products or services to a federal agency, you will almost certainly be asked for a VPAT. Federal procurement rules require agencies to consider accessibility when buying information and communication technology, and the VPAT is the standard document vendors use to disclose how their product conforms to accessibility standards. The completed document, called an Accessibility Conformance Report (ACR), accompanies bids, RFP responses, and contract negotiations. Without one, a procurement officer often cannot move a purchase forward.
| Key Point | What It Means |
|---|---|
| Federal buyers | Section 508 requires agencies to evaluate accessibility before purchasing ICT, so a VPAT is typically requested. |
| VPAT edition | Use the Section 508 edition or the INT edition for federal procurement; the WCAG edition alone is not sufficient. |
| State and local | Many state and local governments reference Section 508 or WCAG 2.1 AA and request VPATs as well. |
| Underlying evaluation | An accurate ACR is based on an accessibility audit, not self-assessment from a scan. |
| Cost range | ACR issuance generally ranges from 300 dollars to 1,000 dollars, plus the cost of the audit (1,000 dollars to 3,000 dollars). |
What Section 508 Requires of Federal Vendors
Section 508 of the Rehabilitation Act requires federal agencies to make their information and communication technology accessible to people with disabilities. The rule applies to the agency, but it shapes what vendors must provide. When an agency buys software, a website service, a SaaS product, or hardware with a digital interface, the contracting officer is expected to confirm the product meets the Revised 508 Standards, which incorporate WCAG 2.0 Level A and AA along with additional hardware and software criteria.
The VPAT exists so vendors can document conformance in a consistent format. Agencies use the ACR during market research, source selection, and contract award. A vendor who cannot produce one is at a competitive disadvantage and may be disqualified from consideration.
Which VPAT Edition to Use for Government Procurement
The VPAT comes in four editions: WCAG, Section 508, EN 301 549, and INT. For federal sales, the Section 508 edition is the standard request. It maps directly to the Revised 508 Standards and includes the chapters federal procurement officers expect to see, including hardware, software, support documentation, and services chapters where applicable.
The INT edition combines Section 508, WCAG, and EN 301 549 into a single document. Vendors who sell internationally or to multiple government markets often choose INT to cover federal U.S. buyers, EU public sector buyers under the European Accessibility Act framework, and private sector buyers in one ACR. The WCAG edition alone covers only the web content criteria and is not sufficient for federal procurement on its own.
State, Local, and Education Buyers
Federal sales are not the only government context where VPATs come up. Many state governments have adopted Section 508 or WCAG 2.1 AA as their procurement standard, and higher education institutions routinely request ACRs before licensing software, learning management systems, library databases, and student services platforms. K-12 districts, hospital systems receiving public funds, and municipal agencies follow similar patterns.
Public entities now also work under the ADA Title II web rule, which references WCAG 2.1 AA for state and local government websites and mobile apps. Vendors selling to those entities are increasingly asked to demonstrate that their product will not put the agency out of conformance.
What Goes Into a Credible ACR
An ACR is only as accurate as the evaluation behind it. A document filled in from a scan or from internal guesswork is a liability, not an asset. Procurement officers review ACRs critically, and discrepancies between the document and actual product behavior surface quickly during user evaluation or post-award audits.
A credible ACR is supported by an accessibility audit that includes screen reader testing, keyboard testing, visual inspection, and code inspection across representative pages or screens. The auditor identifies issues against each applicable success criterion, and the ACR reflects those findings honestly. “Supports,” “Partially Supports,” “Does Not Support,” and “Not Applicable” are used precisely, with remarks that explain the basis for each conclusion.
What Vendors Prepare Before Bidding
Vendors who plan ahead avoid scrambling when an RFP arrives with a 72-hour ACR turnaround request. Preparation generally includes:
- Audit scope decision: identifying the pages, screens, or product areas that represent the offering being sold.
- Accessibility audit: a manual evaluation against WCAG 2.1 AA or the Revised 508 Standards, depending on the edition needed.
- Remediation of high-impact issues: fixing the issues most likely to affect user experience and procurement review.
- ACR drafting: completing the chosen VPAT edition based on the audit findings.
- Update cadence: a plan to refresh the ACR after significant product changes.
Cost and Timeline Expectations
Most accessibility audits start at 1,000 dollars and range to 3,000 dollars depending on the size and complexity of the product. ACR issuance is typically 300 dollars to 1,000 dollars on top of that, with multi-edition ACRs (such as INT) priced higher because of the additional standards covered. Turnaround for the audit and ACR together usually runs a few weeks, which is why vendors who wait until an RFP lands often miss the window. ADA and accessibility requirements for digital products continue to expand, and a current ACR is increasingly part of the baseline documentation buyers expect.
Selling to the government without a VPAT is possible in narrow cases, but it is rarely the path of least resistance. For most vendors, an ACR backed by a real audit is the document that keeps a deal moving.