The standard we build to

We target WCAG 2.2 Level AA. That is a floor, not a finish line, and we treat a failure against it as a bug rather than a feature request.

What we have done

  • Every text and background pairing in our design system is checked against a 4.5:1 minimum, and the accent colour exists at two values specifically so it can clear that ratio on both light and dark grounds.
  • Interactive elements have a visible focus outline at three pixels with an offset, not a removed one.
  • The site is navigable by keyboard, including the dropdown menus, which respond to Escape and return focus.
  • Every animation on the site resolves to its final state under prefers-reduced-motion — a different complete experience, not a degraded one.
  • Images carry alternative text, and decorative artwork is hidden from assistive technology rather than described.
  • Headings are used in order and describe the section they open, so a screen-reader outline is usable for navigation.

Where we know we fall short

We would rather name these than let you discover them.

  • Some product screenshots convey information visually that is only summarised in surrounding copy.
  • Third-party embeds — most notably the HubSpot booking widget — are outside our direct control, and their accessibility is theirs to maintain.
  • The site has not been through a formal audit by a third party. We intend to change that.

Tell us

If any part of this site is hard to use, we want the specific page and what went wrong. Send it to us and we will fix it and tell you when it is done. If you need information from a page that isn't working for you, ask and we will get it to you another way.

How we build for clients

The systems we build carry the same standard. Contrast, keyboard reach, focus visibility, and reduced-motion behaviour are part of the build, not a pass at the end — because an operations system that part of the team cannot use is not finished.

Questions about this page? Contact us and we'll answer.