Accessibility
Accessibility is part of the build, not a retrofit
We aim to meet WCAG 2.2 Level AA on this site and on the websites we build for clients.
The standard we work to
Keyboard access, visible focus, sufficient colour contrast, meaningful alternative text and correct heading structure are treated as part of web design and web development, not as a later pass.
How we test
Automated checks run on every build, and we test manually with a keyboard and a screen reader before anything ships.
Known limitations
Some older embedded third-party content is outside our control. Where we cannot fix it, we look for a replacement or provide an accessible alternative.
Report a barrier
If something on this site blocked you, email [email protected] with the page and what happened. We treat access barriers as bugs and prioritise them accordingly.
Need something this page does not cover? Talk to our team.