Skip to content

Accessibility

Accessibility statement.

We want everyone to be able to use ProjectX, whatever assistive technology they rely on. This statement says what we are aiming for, where we are today, and how to tell us when something is in your way.

The standard we target

We target WCAG 2.2 at level AA across this site and the product consoles. That is the level most public bodies and procurement teams ask for, and it is the bar our automated checks are pinned to.

Where we are today

Automated WCAG 2.2 AA checks run over this site and every console on every change, and a colour-contrast gate runs alongside them. These catch the mechanical failures — a missing label, an unnamed control — and they catch them before they ship.

An audit by a person using a screen reader is the pending step: its method and checklist are written down and ready to run, and it has not yet been carried out. Automated tooling catches perhaps a third to a half of accessibility issues; the judgement calls — whether a heading outline reads sensibly, whether an error message helps — need a person, and that work is not done.

A statement, not a certification: This is a statement of intent and current conformance, not a certification. We describe ourselves as partially conformant with WCAG 2.2 AA: conformant on the checks we can automate and verify, with the full human audit still under way. We would rather say that plainly than claim a conformance we have not finished proving.

Accessibility

Report a barrier

If something on this site or in the product stops you using it, tell us. Describe what you were trying to do, the page, and the assistive technology you were using if you can — it helps us reproduce it. We treat an accessibility barrier as a bug, not a feature request.

A contact address is not configured for this site. The contact page carries the general channel, which reaches us too.

Accessibility · ProjectX