Accessibility
Built to be used by everyone.
We want this site to work whether you use a mouse, a keyboard, a screen reader, or magnification. We aim for WCAG 2.2 AA, and we treat any gap as a bug to fix. Here is where we stand.
What we build in
Everything works from the keyboard
You can reach and operate every link, button, and form field with the keyboard alone. A "Skip to content" link jumps past the menu, and the focus order follows the order you read in.
You can always see where you are
Whatever has keyboard focus gets a clear visible ring, so you never lose your place when tabbing through a page.
Text you can actually read
Body text and interactive elements meet the WCAG 2.2 AA contrast ratios against their background. We do not rely on colour alone to carry meaning.
Motion you can turn off
If your device is set to reduce motion, we honour it. Scroll animations, transitions, and the 3D scenes drop back to a still, calm version. Nothing flashes or jumps.
Forms that explain themselves
Every field has a real label, errors are announced in plain words, and screen readers are told what each control does and when something changes.
Built mobile-first
Touch targets are at least 44 by 44 pixels, layouts reflow to small screens without horizontal scrolling, and text stays readable when you zoom in.
The standard we hold to
WCAG 2.2, level AA.
That is the benchmark we design and test against. This is a work in progress, not a finished claim. We run automated checks on every change and review by hand. Where we know a part falls short, we treat it as a defect and prioritise the fix.
Where it may fall short
- The animated 3D scenes are visual flourish. They carry no information you need, and they stand down under reduced-motion.
- Some third-party embeds we rely on may not yet meet the same bar. We chase the suppliers and look for better options.
Hit a barrier?
Tell us, and we will fix it.
If something on this site stopped you getting what you came for, we want to know. Email us with the page and what went wrong, and we will reply within one working day.
What helps us fix it faster
- The page you were on and what you were trying to do.
- The browser, device, and any assistive technology you use.
- What you expected to happen, and what happened instead.