Skip to main content

VPAT / ACR Services

VPAT / ACR Preparation and Review Services

Protect awards, contracts, and re-competes with VPAT and ACR documentation that stands up to buyer scrutiny. 508Audit prepares, reviews, and refines Voluntary Product Accessibility Templates and Accessibility Conformance Reports for software vendors, federal agencies, higher education, healthcare, and prime contractors — grounded in real testing, signed by a credentialed evaluator of record, and written for the procurement teams who actually read them.

  • VPAT drafting and review support
  • Accessibility Conformance Report review and refinement
  • OpenACR support where appropriate
  • Accessibility risk identification before procurement or contract delivery
Public-sector accessibility focusProcurement-aware documentationFounder-led deliveryDHS Trusted Tester credentialed evaluatorsSAM.gov registered

Who this service is for

Built for the teams who write — and the teams who evaluate — VPATs.

Software vendors selling into government

Commercial and SaaS vendors who need defensible VPATs/ACRs for federal, state, local, or higher-ed procurements.

Agencies reviewing vendor claims

Section 508 program offices and acquisition teams that need a procurement-side review of vendor VPATs and conformance claims.

Higher education procurement teams

Accessibility offices and procurement leads evaluating LMS, student-system, and ed-tech vendor conformance documentation.

Prime contractors

Primes evaluating subcontractor or platform accessibility, or producing VPAT documentation on awarded contracts.

Digital teams after remediation

Product and engineering teams that need a VPAT updated to reflect validated fixes after a remediation cycle.

What 508Audit helps with

VPAT and ACR work scoped to the actual procurement or delivery need.

VPAT drafting support

From a clean slate or an outline — we draft conformance claims, remarks, and notes grounded in actual product behavior and testing.

VPAT review & QC

Independent review of an existing VPAT for accuracy, evidence sufficiency, and procurement readiness — with a written feedback memo.

ACR refinement & cleanup

Restructuring vague remarks, replacing unsupported claims, and tightening language so the ACR holds up under buyer scrutiny.

OpenACR support

OpenACR YAML twins for buyers and platforms that expect machine-readable conformance alongside the Word document.

Documentation/claim review

Cross-checking VPAT claims against product behavior, known limitations, and the underlying WCAG/508 evidence.

Post-remediation validation

Validating fixes and refreshing the VPAT/ACR so the document reflects the current, tested baseline — not last year's product.

Why VPAT quality matters

VPATs are read by procurement, not just engineering.

In public-sector procurement, the VPAT is often the first artifact a buyer reads. Incomplete or overly optimistic VPATs create procurement risk for buyers and delivery risk for vendors. Unsupported 'Supports' claims become award-protest exposure. Vague remarks reduce buyer confidence and slow evaluations. The document should reflect real testing, known limitations, and a clear remediation plan where it matters.

Buyer-side risk

Buyers who accept weak VPATs inherit accessibility risk after award — and the program office has to defend the decision. Procurement reviewers are increasingly asked to scrutinize VPAT quality, not just check a box.

Vendor-side risk

Vendors who submit aspirational VPATs face delivery risk, retesting demands, and potential disqualification on re-competes. A defensible VPAT protects the award and the renewal.

VPAT due before a procurement deadline?

We turn around pre-submission review and revision quickly when the product and existing documentation are ready.

Common problems we identify

What we find in VPATs — and what we fix.

  • Unsupported 'Supports' claims with no testing evidence behind them
  • Missing or empty remarks columns on consequential criteria
  • Vague conformance language that reads like marketing copy
  • Untested workflows or product modes silently excluded from scope
  • Misalignment between observed product behavior and VPAT entries
  • Outdated VPAT versions or incomplete tables (Chapter 4, 5, 6, 7)
  • No remediation follow-up plan for Partially Supports rows
  • Missing OpenACR YAML twin when the buyer expects machine-readable conformance

Deliverables

What you receive.

Reviewed or revised VPAT / ACR

Word document with conformance claims and remarks aligned to actual product behavior and supporting evidence.

Feedback memo

A written memo explaining changes, flagged risks, and recommended next steps for engineering, product, and procurement teams.

Issue & risk summary

A summary of accessibility-risk items surfaced during the review — including procurement, delivery, and re-compete exposure.

Recommendations for additional testing

Where existing evidence is thin, a scoped recommendation for the additional testing required to support specific claims.

OpenACR YAML twin (optional)

Machine-readable conformance document for buyers and platforms that expect or prefer it alongside the Word VPAT.

Post-remediation validation (optional)

Validation of fixes and a refreshed VPAT/ACR after a remediation cycle — closing the loop on Partially Supports rows.

Pricing options

Premium VPAT and ACR engagements, scoped to the work.

Pricing reflects the actual review and documentation effort, product complexity, and the procurement or delivery stakes. We do not run a flat-rate VPAT mill. All engagements begin at a $5,000 minimum and scale with scope.

VPAT / ACR Review

Starting at $5,000

For existing VPATs or ACRs that need quality review, cleanup, and accessibility-risk feedback — typically before a procurement submission or vendor due-diligence cycle.

VPAT / ACR Development Support

Starting at $8,500

For teams that need testing-informed documentation support for a product, application, or procurement submission.

Complex procurement or multi-product support

Custom quoteScoped to engagement

For vendors, agencies, or prime contractors with multiple products, procurement deadlines, or high-stakes documentation requirements.

Why 508Audit for VPAT / ACR work

Documentation that holds up where it actually gets read.

Procurement-aware review

We review VPATs the way buyers do — looking for evidence sufficiency, claim accuracy, and the exposure that creates protest and delivery risk.

Practical documentation support

Claims and remarks are grounded in product behavior and tested evidence — not aspirational copy.

Public-sector and contractor focus

We work with the agencies who buy, the primes who deliver, and the vendors who sell — and we know how each reads a VPAT.

Founder-led quality control

Every VPAT/ACR engagement is reviewed by a principal before it leaves. No junior-only sign-off.

VPAT / ACR FAQ

  • What is the difference between a VPAT and an ACR?
    A VPAT (Voluntary Product Accessibility Template) is the empty document framework published by ITI. An Accessibility Conformance Report (ACR) is a completed VPAT — the same template populated with actual conformance claims, remarks, and testing notes for a specific product version. Procurement teams typically ask for a current ACR even when they say 'VPAT.'
  • Can 508Audit help review an existing VPAT?
    Yes. VPAT/ACR review is one of our core engagements. We evaluate claim accuracy, surface unsupported 'Supports' rows, flag vague remarks, identify untested workflows, and produce a feedback memo plus a revised document where appropriate.
  • Do you prepare VPATs for vendors selling to government agencies?
    Yes. We support software vendors and prime contractors preparing VPATs for federal, state and local, and higher-education procurements — including OpenACR YAML twins where the buyer expects machine-readable conformance.
  • Can you review a VPAT before a procurement submission?
    Yes. Pre-submission review is a common engagement, especially when a buyer's evaluation rubric includes a documentation-quality screen. We turn around procurement-deadline reviews quickly when the product and existing VPAT are ready for testing.
  • Do you test the product as part of VPAT support?
    When the engagement calls for it. Defensible VPATs should be backed by audit-grade testing. We can scope a paired Section 508 audit, or work from an existing audit's evidence base if testing already happened.
  • Can you help update a VPAT after remediation work?
    Yes. We validate fixes, capture evidence on closure, and refresh the VPAT/ACR to reflect the validated baseline. This is the typical close-out path for vendors and primes after a remediation milestone.

Need VPAT or ACR support for a procurement, vendor review, or accessibility documentation project?

Send the current VPAT, the procurement deadline, and a contact. We'll come back with scope, timeline, and the testing required to make the document defensible.