Accessibility Statement

What we aim for

The target is the Web Content Accessibility Guidelines 2.2 at Level AA. In practice that means every part of the site can be used with a keyboard alone, every control shows where focus is, text meets contrast minimums in both light and dark themes, and nothing depends on colour alone to make sense.

How it is tested

Accessibility checks run as part of the build rather than as an occasional audit:

• Automated axe checks on every page, at three screen widths and in both light and dark themes
• Colour contrast checked against the palette itself, so a colour change that would break contrast fails the build
• Keyboard-only navigation checked on every page, including the mobile menu and the contact form
• Animation suppressed for anyone whose system asks for reduced motion

Automated testing catches a good share of problems but not all of them. If something is awkward to use and our tests have not noticed, we would genuinely like to hear about it.

What we know is not perfect

Being straightforward about the gaps:

• Some sections of the site are still awaiting final content and are hidden until it arrives.
• The site uses a modern CSS colour feature for theming. On browsers released before 2024 the layout and content work normally, but colours may fall back to browser defaults.
• If the contact form cannot reach our server, it hands the message to your own email application. That application’s accessibility is outside our control.

Telling us about a problem

If you hit a barrier anywhere on this site, email us and say what happened and, if you can, what you were using at the time. We will reply within five working days and tell you what we are going to do about it.