Accessibility

Last updated 6 August 2026

Most accessibility statements are a paragraph of good intentions. This one is a list: what has been done, what still falls short, and who answers when something is in your way. The standard we work to is WCAG 2.1 level AA, on this site and in the app.

What has been done

  • Semantic structure. Every page has one heading hierarchy, named landmarks, and a skip link that is the first thing the Tab key reaches.
  • Everything works from the keyboard. The one place we replace a native control — the styled dropdown on the contact form — implements the full ARIA listbox pattern: Enter, Space or an arrow opens it, arrows move, Home and End jump, Escape closes without choosing, and typing a letter jumps to the first match. The native select stays underneath, so without JavaScript the form still works.
  • Focus is visible. Anything that takes keyboard focus shows a two-pixel outline, applied by one shared rule — so a new control cannot ship without it.
  • Reduced motion is honoured. If your system asks for it, every animation, transition and smooth scroll on this site is switched off.
  • Contrast is checked. The palette — light and dark — was checked against the AA contrast thresholds before it shipped, body text and large text alike.
  • The app speaks. The menu bar item, the panel and its controls carry screen-reader labels, so VoiceOver reads what each thing does rather than announcing unnamed buttons.

What falls short

Two things do not meet the standard yet, and pretending otherwise would defeat the point of this page.

  • The app’s setup window is mouse-first in places. VoiceOver reads its controls, but the keyboard does not yet reach every one of them.
  • Right-to-left layout is functional rather than mirrored. Arabic and Hebrew pages read right-to-left and everything on them works, but some visual details still sit where the left-to-right design put them.

Report a barrier

If something here stops you — a control you cannot reach, text you cannot read, a page that fights your screen reader — tell us through the contact form. Say what you were using — VoiceOver, a keyboard alone, a switch — and where it went wrong. A person will answer within two working days. A real barrier goes ahead of new features, and fixing it moves the date at the top of this page.