AccessRecord

Accessibility Statement

A product that sells accessibility conformance records had better be accessible. This page states where we are, honestly, and how to tell us when we are wrong.

Last updated 11 October 2026

1. Our commitment

We aim to meet WCAG 2.2 Level AA across the application and the public verification pages. We treat an accessibility defect as a defect — it goes in the same queue as everything else, and it is not closed until it is fixed.

There is no accessibility team and no consultant on retainer. This statement is maintained by the developer who built the product, and it is updated when something changes rather than once a year to satisfy a template. The known limitations below are the real ones, not a decorative shortlist.

2. How this application is built

3. Known limitations

We would rather list these than claim full conformance:

4. Conformance status

This statement describes the AccessRecord application. It is not an ACR or a VPAT, and no conformance report has been produced for this product — this page is not a substitute for one, and you should not file it as though it were.

What that means for a procurement process: if you need a formal conformance report from us, ask, and you will get a straight answer about what exists and what does not rather than a document that looks like the ones this product produces for you.

5. Feedback

If you hit a barrier, tell us the page, what you were trying to do, and what happened. Email support@accessrecord.app. We aim to respond within 5 business days and to fix confirmed barriers in the next release where that is possible, or to give you a dated plan where it is not. This reaches the developer who wrote the code, which is why the plan tends to be specific.

6. Compatibility

Tested against current versions of Chrome, Firefox, Safari and Edge on desktop and mobile, and with NVDA, JAWS and VoiceOver. Older browsers are not supported.