Accessibility Conformance Reports

The deal is moving — then procurement asks for your VPAT.

If you sell software to federal, state, or education buyers, accessibility documentation is a gate, not a formality. Section 508 makes conformance a contractual deliverable, agencies request a current VPAT or ACR during evaluation, and primes — who carry compliance risk for their subs — increasingly refuse to onboard vendors without one. A missing VPAT stalls deals at the moment they should be closing; an overstated one becomes a contract-breach problem after award.

Documentation that survives the reviewer.

  • Completed ACR on the current ITI VPAT template, edition matched to your buyer
  • Test evidence — methodology, tooling, findings log — so your claims are defensible
  • Prioritized remediation backlog, ranked by severity against effort
  • Retest and ACR reissue after fixes
  • Optional: website accessibility statement and sales-team talking points

Priced so it does not need a budget cycle.

  • ACR/VPAT, single product
    Evaluation, report, and evidence log
    ~2 weeks
  • ACR + remediation support
    We work the backlog with your team, then reissue
    4–8 weeks
  • Annual re-certification
    Keeps the report current as the product changes
    Yearly

Pricing. Fixed price, quoted before we start. Most engagements are sized to fit small-purchase and three-quote authority. Rush turnaround is available when a live deal is waiting on documentation.

What is the difference between a VPAT and an ACR?

The VPAT is the blank template published by the Information Technology Industry Council. The ACR is what you have once it is filled in for your product with real evaluation behind it. Buyers ask for a VPAT and mean an ACR. We produce the completed report on the current template, in the 508, WCAG, or INT edition your buyer expects.

How fast can you turn one around?

About two weeks for a single product, and faster when a live deal is waiting on the documentation — say so on the first call and we will tell you honestly whether the date is achievable.

What if the product has real accessibility gaps?

Then the ACR says Partially Supports or Does Not Support, with specific remarks, and you get a prioritized remediation backlog your developers can work through. An overstated ACR is worse than an honest one: it becomes a contract-breach problem after award instead of a scoping conversation before it.

Who does the testing?

AI-accelerated tooling handles the mechanical pass — automated rules across every template screen at desktop and mobile widths, version-pinned so results are reproducible — and a person tests the criteria that require judgment, including with assistive technology. Human-judgment criteria are never marked as supported on automated evidence alone.

What do you need from us to start?

A URL or a demo build, credentials for a test account if the product is behind a login, and the buyer's actual requirement language if you have it. That is enough to scope the same day.

Do you re-issue the report after we fix things?

Yes. We retest the findings you remediate and reissue the ACR, and annual re-certification keeps it current as the product changes. A three-year-old ACR reads to a reviewer as no ACR at all.

A live deal waiting on paperwork? Send it over.

Send your product URL and the buyer's requirement — the RFP language or the prime's request. We will scope it the same day and quote a fixed price.

Same-day scope · Rush turnaround available