Skip to content
Arbor

Re-tests after your fixes ship

When your developers have shipped the fixes, we test every issue from the audit again, the same way we found it, and update the report.

Where a re-test fits

  1. Audit

    We find the issues and write the report.

  2. Fix

    Your developers fix them, with our fix support if they want it.

  3. Re-test, this service

    We test every issue again and update the report.

Details

When to book it

Once every fix from the report is live, on your staging site or in production. We test the same templates and user flows as the audit, so the two reports line up issue by issue.

What the updated report is for

It shows which issues are fixed, with the same kind of evidence as the first report. You can use it to:

  • answer buyers and procurement teams who ask for proof of the work;
  • write an Accessibility Conformance Report on the VPAT template, the document US public buyers often ask software vendors for;
  • prepare the accessibility information the European Accessibility Act asks the businesses it covers to publish.

We can write the conformance report or the accessibility information for you after a re-test.

  • 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.

  • Agent readiness

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

  • VPAT and ACR reports

    An Accessibility Conformance Report on the VPAT template, written from the evidence of an audit of your product.

  • EU accessibility statements

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