Skip to content
Arbor

Fix support for your developers

Your team makes the changes, and we stay with them until the fixes ship: code examples for each issue, reviews of their pull requests and one call a week.

Most issues live in shared components such as the header, the product card or the cart drawer. The report groups its fixes by component, so one change to the header fixes every page that uses it.

What fix support covers

We agree where your developers need help and work through those issues with you.

  • Code examples

    For each issue, a short example of the fix. We use plain HTML first and add ARIA only where HTML cannot do the job.

  • Pull request reviews

    When your developers open a pull request, we test the change against the issue it fixes and tell them whether it works.

  • A weekly call

    One office-hours call a week, where your developers bring the issues they are stuck on.

Fix support at a glance

  • Your team

    makes every code change

  • Weekly

    office-hours call

When the fixes are live, book a re-test and we confirm each one.

  • Accessibility audits

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

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

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