// accessibility

Accessibility statement

We build this site to WCAG 2.2 level AA and test it on every push. We are not claiming we have got there. Below is what we do, and what we know is still wrong.

Last updated
Target
WCAG 2.2 level AA
Status
Partly conformant, gaps listed below

01 What we are aiming at

The target is WCAG 2.2 level AA across every page and every template, on a phone and on a desktop, with a mouse, a keyboard, a screen reader or a touch screen.

We say "partly conformant" because that is what an untested-by-humans site is. A full conformance claim needs manual testing with assistive technology on every template, and we have not finished that work. When we have, this page says so and names who did it.

02 How this site is tested

Automated tools find a minority of accessibility problems. They are good at missing labels and bad contrast, and blind to whether a heading makes sense or a control says what it does. That is why the list below exists instead of a green badge.

03 What is built in

04 Known gaps

Everything here is a real defect we have found and not yet fixed.

  1. The sticky header can cover a focused link. Tab to something near the top of a section and the bar can sit over it. WCAG 2.2 added a rule for exactly this case and we do not pass it everywhere yet.
  2. No screen reader pass yet. Nobody has been through every template with NVDA, JAWS or VoiceOver, and no outside auditor has looked at the site.
  3. The interactive parts are the newest. The multi-step contact form and the instant audit tool have had the least manual testing of anything here.
  4. Wide tables on a small screen. The policy tables scroll sideways on a phone. That is usable, and it is still work.
  5. Dark only. There is no light or high-contrast theme yet. The tokens for one exist, the switch does not.

05 Telling us about a problem

If something here blocks you, we want to hear it, and a one-line message is enough. Tell us the page, what you were using (browser, screen reader, phone) and what happened. If it is easier, send a recording.

Email ben@synapsereality.io. You will hear back within 24 hours.

The contact page reaches us too. If something on that form is itself the problem, say so in any channel you can use and we will come back another way.

06 The formal bits