Accessibility Policy

Last updated 14 November 2026

We build interfaces for complicated machines. Our job is to make hard things easy to use, and that has to start with our own site. It should work for you however you get around it: with a mouse, a keyboard, a screen reader, a magnifier, or with motion and sound turned off.

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Below is what we do today, where we know we fall short, and how to tell us when something gets in your way.

What we do

  • Keyboard first. Every link and control can be reached and used with a keyboard, and shows a clear outline when it has focus. The first stop on every page is a link that skips straight to the content.
  • A menu you can drive without a mouse. In the menu, the arrow keys turn the gallery, Enter opens the page in front of you and Escape closes it. Focus stays inside the menu while it is open, and every page in the gallery is also listed as a plain link.
  • Controls that follow the arrow keys. The service list and the call calendar both move with the arrow keys, the way a screen reader expects them to.
  • Motion you can turn off. If your device is set to reduce motion, we honour it. Camera moves become instant cuts, the film on the services page stops growing as you scroll and just sits in the page, and the animated backgrounds hold still.
  • Silent unless you ask. The interface has sound, and it is off until you switch it on. Your choice is remembered on your device. The studio film has no audio, so there is nothing to caption, and it can be paused.
  • Light and dark. Pick whichever is easier on your eyes from the top bar. It is remembered too.
  • Pictures with words. Team photos carry each person's name, and system diagrams carry a written description of what they show. Drawings that are only decoration are hidden from screen readers, so they do not read out noise.
  • Real structure. Pages use proper headings, landmarks and lists, and declare their language, so assistive technology can find its way around.

Where we fall short

We would rather tell you than have you find out. We know about these and are working on them:

  • The screenshots on our project pages do not have text descriptions yet, so a screen reader passes over them. The writing around each one says what the work is, but not what the screen shows. We are adding them.
  • Our headline typeface is wide and geometric. It is set large, but some readers will find it slower to read than plain text.
  • Parts of the site respond to where your pointer is, such as the 3D drawings on the services page. That is a bonus for mouse users; nothing you need is hidden behind it.

If you hit something that is not on this list, we want to know.

Other people's content

We link out to a few places we do not run, like our social profiles. We cannot vouch for how accessible those are. If one of them blocks you, tell the people who run it, and tell us too.

Tell us

If any part of this site is hard to use, send us a note through the contact form. Say which page, what you were trying to do, and what you use to browse if you are happy to share it. We read every message, and we will fix what we can and tell you when we have.