Legal

Accessibility

Last updated August 2026

An accessibility statement is useful only when it says what is actually in place. This one is a list: what has been done, what still falls short, and who answers when something is in your way. This statement covers this website. WCAG 2.1 level AA is the standard we use to design and review it; this is not a claim about the macOS 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.
  • Interactive controls are built for keyboard use. The shared navigation, settings panel, forms and disclosure controls are keyboard reachable. The one place we replace a native control — the styled dropdown on the contact form — implements the ARIA listbox keys: 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. Links, buttons, fields, selects and summaries share a two-pixel focus outline.
  • Reduced motion is honoured. If your system asks for it, animations, transitions and smooth scrolling settle immediately. The Settings button also provides a site-specific Reduce motion switch.
  • Contrast is checked. The color tokens for body text, large text and control edges meet measured AA thresholds in both themes.

What falls short

  • Right-to-left layout is functional rather than fully mirrored. Arabic and Hebrew pages read right-to-left and the shared controls use logical layout directions, but some visual details still sit where the left-to-right design put them.
  • Testing coverage is finite. Not every combination of browser, device, zoom level and assistive technology has been tested. A barrier report is evidence that this statement missed something.

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. We aim to answer within two working days. Accessibility barriers take priority over feature work. The date at the top records material updates to this statement.