Accessibility Statement

What we have done

• Colour contrast. Our brand palette uses four bright accent colours. Several of them fail contrast requirements as body text on white, so we do not use them that way — the raw accents appear only as fills, icons, and large display type, and darkened variants are used wherever coloured text sits at body size.
• Keyboard navigation. Every interactive element is reachable and operable by keyboard, with a visible focus ring. A skip link at the top of each page jumps past the navigation.
• Tap targets. Buttons and links meet a 48px minimum on touch devices.
• Structure. One h1 per page, headings in order, landmark regions, and labelled form fields. Screen readers get a sensible reading order.
• Motion. We respect prefers-reduced-motion and disable transitions for anyone who has asked their system to reduce animation.
• Text. Body text scales with browser settings and the layout reflows to 320px without horizontal scrolling.

Known gaps

Being honest about this is more useful than claiming full compliance:

• Third-party embeds. The booking calendar is supplied by an external provider and we do not control its markup. If it presents a barrier, call or use the contact form and we will book you manually.
• Older content. As we add pages, some images may temporarily lack descriptive alternative text. We audit for this, and reports help us find it faster.
• No formal third-party audit. Our testing is internal — automated checks plus manual keyboard and screen-reader passes. We have not commissioned an independent accessibility audit, and we will say so rather than imply certification we do not hold.

Tell us about a barrier

If something on this site stops you doing what you came to do, we want to know. Reports are treated as bugs, not complaints. Use the contact form or call, and tell us the page and what happened. We aim to respond within two business days.

If you cannot use a part of the site, we will complete the task for you directly — booking a call, sending a quote, whatever it was — while we fix the underlying problem.

How we build for clients

Accessibility is part of every build we deliver, not an add-on. Contrast, keyboard operability, form labelling, and heading structure are checked before launch. It is also good business: the same work that makes a site usable with a screen reader tends to make it faster and easier for everyone.