Built to WCAG 2.2 AA, and measured against it.

The standard we build to

This site targets WCAG 2.2 Level AA. Accessibility was treated as a build requirement rather than a review step, and several checks run automatically so a regression fails the build rather than reaching you.

An automated audit of the live site currently reports a perfect accessibility score. Automated tools catch perhaps a third of real barriers, so that number is a floor, not a finish line.

What is in place

Colour contrast

Every text and interface colour pair is checked against WCAG 2.2 AA by a script that fails the build on a shortfall. Body text on the page background measures 9.12:1 against a 4.5:1 requirement.

Keyboard focus

Every interactive element shows a visible two-tone focus ring. It uses two concentric colours so it stays visible on light backgrounds, dark backgrounds, white cards, and coloured buttons alike.

Keyboard navigation

The whole site is operable without a mouse, including the mobile menu, which closes on Escape. A skip link is the first thing you reach on every page.

Motion

Scroll animations and the moving hero graphic are disabled entirely when your system is set to reduce motion. Content is never hidden behind an animation, so it is readable even if scripting fails.

Structure

One h1 per page, headings in order with no skipped levels, and proper navigation, main, and footer landmarks. Checked automatically on every page.

Forms

Every field has a visible label tied to it. Errors are announced, described against the field they belong to, and written in plain language.

Text sizing

Type is set in relative units and reflows without loss of content when you zoom or use a larger default font size.

Known limitations

These are the gaps we are aware of. If you hit something not listed, we would rather hear about it than not.

• The site has not yet been tested end to end with a screen reader by a person who uses one daily. Automated checks are not a substitute for that.
• Booking a call sends you to Calendly, a third-party service whose accessibility we do not control. If the booking page is a barrier for you, use the contact form or email us and we will arrange a time directly.
• The wordmark relies on a font served by Adobe. If it fails to load, the name renders in a fallback typeface. This affects appearance only, never legibility or meaning.
• Spanish-language pages are not published yet. Until they are, this site is English only.

If something blocks you

Tell us and we will fix it. Describe the page and what happened, and if it is easy to say, the browser or assistive technology you were using. You will not be asked to justify the request.

If something on this site prevents you getting in touch, that is our failure to solve, not yours. Email is always a working route.

How this is maintained

Contrast, heading order, and page structure are checked automatically on every change, before it reaches the site. Anything those checks cannot catch is handled by review.

This statement is updated when the site changes in a way that affects any of the above.