Skip to content
Arbor

VPAT and Accessibility Conformance Reports

Public buyers ask software vendors for an Accessibility Conformance Report before they sign. We write yours on the ITI VPAT template, from the evidence of a real audit of your product.

How we write it

  1. Audit

    We test your product with a Starter or Full audit and report every issue with evidence.

  2. Fixes and re-test

    Most teams fix the serious issues first. We test them again, so the report shows your product as it is now.

  3. The report

    We fill in every criterion of the template from the audit evidence, with remarks a buyer can check.

  4. Your review

    You read the draft and ask questions before we hand over the final report.

Details

What a VPAT and an ACR are

The VPAT is a free template from the Information Technology Industry Council (ITI). Once it is filled in for one product, it becomes that product’s Accessibility Conformance Report, or ACR.

For each requirement, the report says whether the product supports it, partially supports it or does not support it, with remarks that explain the answer. Buyers compare these reports between vendors.

Which edition we write

The template comes in editions for different rules. We write one of two:

  • the WCAG edition, against WCAG 2.2 levels A and AA, for buyers who ask about WCAG;
  • the International edition, which covers WCAG, Section 508 for US federal agencies and the EU standard EN 301 549 in one document.

We agree on the edition with you before we start, based on who your buyers are.

When we write the report

We prepare the report free of charge after auditing the same product, using evidence from that audit.

What the report is, and is not

It describes what we found on the date we tested. It is not a certificate and it does not say your product is compliant with any law, because no report can. Update it after major releases, so it keeps matching the product your buyers use.

  • Accessibility audits

    We test your key templates and user flows against WCAG 2.2 AA, and report every issue with evidence and a fix.

  • Fix support

    Code examples, reviews of your pull requests and a weekly call while your developers work through the report.

  • Re-tests

    When the fixes are live, we test every reported issue again and update the report.

  • Agent readiness

    How well AI agents can read and use your site, scored with our Agent Readiness Index and backed by evidence.

  • EU accessibility statements

    The accessibility information the European Accessibility Act asks you to publish, written from a real audit.