Accessibility
How we try to make this site usable for everyone, what we have checked, and how to tell us when something gets in your way.
Our aim
We want this site to be usable by as many people as possible, including people who use a keyboard, a screen reader, screen magnification, or who prefer reduced motion. We are working towards the WCAG 2.2 AA standard as our target. This is a statement of intent, not a claim that the whole site already conforms.
What we have tested
We check the site ourselves as we build and change it. So far that has included:
- Automated checks with axe-core against our main pages.
- Keyboard navigation: reaching and operating links, buttons and forms without a mouse.
- Zoom and reflow: using the site at larger text and zoom levels.
- Reduced motion: honouring the system “reduce motion” setting.
These are our own checks. We have not commissioned a formal third-party audit, and we do not publish an audit date, vendor or conformance score, because we do not have one to report honestly.
What is supported
- Keyboard navigation across the site.
- A “skip to content” link at the top of each page.
- Visible focus so you can see where you are.
- Respect for the reduced-motion setting.
- Text that can be resized without breaking the layout.
- Forms with clear labels and plain-language error messages.
Known limitations
Two parts of the site rely on third-party tools that are not fully under our control, so we cannot guarantee their accessibility:
- The ALTCHA spam-check widget on our forms.
- The Cal.com booking embed used to schedule calls.
If either of these blocks you, please contact us using the details below and we will help you another way, such as arranging a call or taking your enquiry by email.
How to report a barrier
If something on this site is hard or impossible to use, please tell us using the contact email in our site settings, shown on our contact page. Describe what you were trying to do and what got in the way. We aim to reply within one business day.
Keeping this up to date
We review this page whenever the site changes, and we update what is supported and what is still a known limitation as we go.
Hit a barrier? Tell us and we will help.