Start a project
Trust and governance

Accessibility

The site is designed toward WCAG 2.2 AA and treats accessibility as part of the creative and technical standard.

Working standard / July 2026

Interaction

Primary journeys support keyboard operation, visible focus, semantic controls, meaningful headings and skip navigation.

Motion and display

Animation responds to reduced-motion preferences. Layouts are designed to reflow, text remains selectable and contrast is reviewed across light, dark and signal-colour surfaces.

Continuous review

Accessibility is a maintained condition, not a one-time badge. If a page or interaction creates a barrier, tell us which route and task were affected so it can be investigated.

What that looks like in practice.

The same booking card, built two ways. Move between the lenses to see what the difference actually is for someone using it.

Both versions look broadly similar. That is exactly the problem: the failures are invisible until someone needs them not to be.

Common

Book an appointment

“edit text, blank”
“edit text, blank” — the error is not announced
Book now
not reachable by keyboard, announced as nothing
  • Placeholder used instead of a label (WCAG 3.3.2)
  • Colour is the only error indicator (WCAG 1.4.1)
  • Control is not keyboard operable (WCAG 2.1.1)
  • Text contrast below 4.5:1 (WCAG 1.4.3)
How we build it

Book an appointment

“Your name, edit text”
Enter an email address so we can confirm the time“Email address, invalid entry, Enter an email address...”
“Book now, button” — reachable by Tab, visible focus
  • Every field has a persistent, associated label
  • Errors carry text as well as colour
  • Real buttons, operable by keyboard
  • Contrast checked against the ground it sits on