Accessibility statement

What we are aiming at

We build this website to meet WCAG 2.2 at Level AA. That is the target we design and test against, not a certification we are claiming to hold — no independent audit has been carried out yet, and until one has, saying otherwise would be dishonest.

Accessibility is built in as pages are made rather than added afterwards. Retrofitting it does not work, and every site that has tried has the markup to prove it.

What we have actually done

• Colour contrast is computed rather than estimated. Every foreground and background pairing in the design system has a calculated ratio, and the floors are checked automatically on every build — a token pairing that would fail cannot ship.
• Interactive targets meet the WCAG 2.2 minimum of 24 by 24 CSS pixels, and controls on touch surfaces are sized to 44 pixels.
• Every page is operable by keyboard alone, including the mega menu and the mobile drawer. Focus is visible everywhere and is never removed without a replacement.
• The navigation uses real ARIA patterns — a tablist for the mega menu rail, a modal dialog for the mobile drawer — with focus returned to the trigger on close.
• Headings follow a logical order, landmarks are marked up, and there is a skip link to the main content.
• Forms use real labels tied to their inputs, describe their own errors, and announce them.
• Content that reveals on scroll is fail-safe: with JavaScript unavailable it is visible rather than stranded invisible.
• Motion respects prefers-reduced-motion. Under that setting, reveal animations do not have a hidden initial state at all.
• Data tables that are wider than a small screen scroll inside their own region, so the page itself never scrolls sideways.

How we test

Automated checks run against every page as part of our build and review process: heading order, images without alternative text, controls with no accessible name, unlabelled landmarks, and target sizes below the minimum. Contrast is validated separately against the design tokens.

Automation catches perhaps a third of real accessibility problems, so pages are also operated by keyboard and reviewed at eleven screen widths from 375 to 2560 pixels.

Known limitations

Being specific about what is not yet done is the part that makes the rest of this statement worth reading.

• No independent audit has been carried out. Our testing is our own, and self-assessment has blind spots by definition.
• We have not completed testing with the full range of screen readers and browser combinations. Automated checks and keyboard testing are not a substitute for that.
• The billing and client area runs on separate third-party software. We do not control its markup, and it has not been assessed to the same standard as this site.
• Where a domain registry or payment provider renders part of a flow, its accessibility is outside our control.

If something blocks you

Tell us. A specific report — the page, what you were trying to do, the browser and assistive technology you were using — is worth more than any audit, because it describes a real barrier rather than a theoretical one.

We treat accessibility reports as defects rather than feature requests. If something on this site prevents you doing business with us, we will also do that business with you by phone or email in the meantime, at no disadvantage to you.