Accessibility statement

Statement prepared 6 September 2026. Last tested 6 September 2026. Next review September 2027.

Our commitment

This site is built to conform to the Web Content Accessibility Guidelines version 2.2, level AA. We treat that as a floor rather than a finish line: a practice that argues design should work for the person using it cannot ship a website that does not.

What that means in practice

• Every page works with a keyboard alone, and the focused element is always visible and never hidden behind the header.
• Text contrast meets or exceeds 4.5 to 1, and interface borders meet 3 to 1. All eighteen colour pairs in the palette were calculated rather than eyeballed.
• Content reflows to a 320 pixel viewport with no horizontal scrolling.
• Every image carries alternative text, and tables that scroll sideways can be reached and scrolled with a keyboard.
• Form fields have visible labels, errors are announced and explained in words, and no error is signalled by colour alone.
• Interactive targets are at least 24 by 24 pixels.
• Animation is minimal and is switched off for anyone whose system asks for reduced motion.
• The site works with JavaScript disabled, and in your browser's high contrast or forced colours mode.

How we tested

Automated testing with axe-core across every page, which currently reports no violations, alongside manual keyboard walkthroughs and calculated contrast for each colour pair in use.

Automated tools catch perhaps a third of real barriers. We have not yet commissioned independent testing with people who use assistive technology day to day. When we do, we will publish what it found here, including anything it found that we had missed.

Known limitations

We would rather name these than claim perfection.

• Imagery on the site is currently abstract illustration while commissioned photography is produced. When photographs replace it, alt text will be written per image, describing what the photograph shows rather than repeating the caption.
• If a video is added to the home page it will be muted, will carry a visible pause control, and will not play automatically for anyone who has asked for reduced motion.
• Case studies are not yet published. When they are, each will be checked against this standard before it goes live.

Telling us about a barrier

If something on this site blocks you, please tell us through the interest queue form, choosing the accessibility option. Describe the page and what happened, in whatever words are easiest for you. There is no wrong way to report it.

That form is also the route for a barrier in the form itself. If you cannot complete it at all, that is exactly the kind of failure we want to hear about, and we will find another way to receive it.

We aim to reply within five working days. If a fix will take longer than that, we will tell you what we are doing and offer the content another way in the meantime.