Recent regulatory clarity and enforcement regarding ADA Title II for state and local governments have made it compulsory for public-sector buyers to demand clear accessibility evidence from vendors. That demand – combined with federal procurement practices and the practicality of standard forms – has transformed the VPAT (Voluntary Product Accessibility Template) and its completed form, the ACR (Accessibility Conformance Report), from merely marketing documents into essential procurement object.
Read along to learn more!
A quick background on what all changed in ADA Title II
The Americans with Disabilities Act Title II applies to state and local governments and requires all programs and services – including digital properties like websites, mobile apps, and kiosks – to be accessible to people with disabilities. Over the past few years, federal guidance, enforcement activity, and updated procurement expectations have made it clearer that digital accessibility is not optional for public entities. Thus, agencies/organizations are prioritizing procurement rules and requiring demonstrable proof of accessibility in the beginning of the buying process.
VPAT and ACR – what they are, and why both matter
VPAT (Voluntary Product Accessibility Template): a standardized template (maintained by industry/ITI) that maps a product’s technical accessibility features to widely used standards (WCAG, Section 508, etc.). It’s the blanks-and-criteria form that vendors fill out.
ACR (Accessibility Conformance Report): the document produced when a VPAT is completed and tested – in other words, the vendor’s formal statement of how a product conforms to accessibility requirements. Section 508 guidance explicitly positions ACRs as the expected output used in procurement.
For procurement teams, a VPAT without accompanying test evidence, test notes, remediation plan is of no or low value. For vendors, a well-constructed ACR is the single best piece of “proof” they can provide during public-sector bidding.
Why is ADA Title II accelerating adoption now?
Three forces converge:
- Regulatory clarity and enforcement pressure
Recent ADA guidance and enforcement actions have pushed state and local entities to treat digital accessibility seriously; which drives formal procurement requirements. Agencies want to show they performed due diligence in avoiding discrimination under Title II.
- Procurement risk management
Public buyers are risk averse. And awarding contracts to vendors without documented accessibility increases litigation and compliance risk. However, VPAT/ACR up front demand reduces procurement and legal risk and creates an audible trail.
- Federal/state alignment with technical standards
Section 508, WCAG, and updated VPAT versions (recent updates to align with WCAG 2.2/2.1/2.0) refer that there’s a common way to assess digital products and services. The VPAT/ACR is the practical instrument for translating technical testing into procurement decisions.
Micro-level note: Some guidance and practitioner resources are now specifying concrete timelines for public-sector purchases and minimum WCAG conformance levels – driving agencies to bake VPAT/ACR requirements into solicitations and RFP templates.
Explore the WCAG accessibility standards comparison video!
How procurement processes changed (what buyers now request)
- Mandatory VPAT/ACR submission with bids: Many RFPs now require an up-to-date VPAT and evidence (ACR) as part of the technical submission.
- Scored accessibility sections: Accessibility compliance and remediation timelines are becoming scored criteria, not mere pass/fail checkbox items.
- Ongoing conformance clauses: Contracts increasingly include clauses requiring updates to the ACR when a product is updated, and remediation SLAs for accessibility defects.
Benefits for the public sector and vendors
For public agencies
- Quicker risk assessment in procurement.
- Auditable records to show compliance and due diligence.
- Better vendor accountability and clearer remediation paths.
For vendors
- A well-prepared ACR increases competitiveness for public-sector contracts.
- A clearer internal QA focus on accessibility reduces late-stage rework and litigation risk.
- Better market differentiation: agencies increasingly see accessibility as a procurement advantage rather than a formality.
Challenges and common pitfalls for buyers to identify correct VPAT
- Superficial VPATs
Vendors sometimes produce VPATs that are self-serving and lack real test evidence; procurement teams are learning to spot these.
- One-off static ACRs
Digital products change often; an ACR produced once and never updated becomes stale. Contracts should require updates after major releases.
Practical steps – what agencies and vendors should do now?
For public agencies
- Require an ACR (completed VPAT) as part of the RFP and specify which VPAT edition and WCAG level an agency expects.
- Score accessibility and require remediation timelines in contracts.
- Train procurement officers to evaluate ACRs (or use a simple checklist to verify evidence vs. claims).
For vendors
- Maintain a living VPAT + ACR process: test, document, and update on releases.
- Include test evidence and remediation plans; be transparent about exceptions and roadmaps.
- Invest in complete accessibility audit for credibility (automated + manual + assistive tech checks).
Short case examples (how federal/state bodies are using VPAT/ACR)
- Federal agencies depend on Section 508 mechanisms and tools (ACR editor, VPAT templates) to standardize vendor submissions and to assess accessibility risk in procurements.
- State & local governments are increasingly mirroring federal practice – asking for VPATs/ACRs in education and municipal IT procurements and expecting WCAG-based targets. Practitioner resources and compliance guides for Title II are being published to help agencies plan.
The future: normalization and ecosystem effects
Expect VPATs and ACRs to become the standard “accessibility spec sheet” for most public-sector ICT purchases. That normalization will:
- Increase the baseline accessibility quality of commercial products targeted at governments.
- Grow a market for independent ACR auditing and VPAT consultancy.
- Push product teams to bake accessibility into their dev lifecycles rather than bolt it on during procurement.
Read more: AI Automated Accessibility widget vs Manual Accessibility service
Final Recommendations
ADA Title II is increasing the importance of clear accessibility documentation and evidence across public-sector procurement. Public buyers can strengthen accessibility requirements by requesting current VPATs and ACRs, defining the applicable WCAG target, and including accessibility in vendor evaluation. Vendors, meanwhile, should keep their documentation current, support claims with testing evidence, and maintain a clear remediation and update process.
Skynet Technologies supports public-sector organizations with VPAT creation, ACR development, accessibility audits, comprehensive remediation, and ongoing monitoring aligned with WCAG and applicable federal accessibility requirements. Our team also provides dedicated support to help organizations manage their accessibility programs across digital platforms.
Request a Free Accessibility Audit to identify potential accessibility gaps, review your documentation needs, and discuss a practical roadmap for improving digital accessibility.
