Accessibility

Built to be used by everyone.

We target WCAG 2.2 Level AA. Here is what this site does, where it falls short, and how to tell us when we have got it wrong.

Last updated 29 July 2026.

We build to WCAG 2.2 Level AA as our standard, and we hold this site to it too. This page sets out what we have actually done, what we know is imperfect, and how to tell us when we have got it wrong.

What this site does

  • A skip to content link is the first thing a keyboard or screen-reader user reaches on every page.
  • Pages use real landmarks — nav, main, footer — with a single h1 and headings in order, so the structure can be navigated rather than just read.
  • Every page declares its language (lang="en").
  • Keyboard focus is always visible: a three-pixel outline with an offset, never removed.
  • The site respects prefers-reduced-motion. If your system asks for reduced motion, the scroll animations and smooth scrolling switch off.
  • Contact-form fields have real label elements, errors are marked with aria-invalid and announced through a live region, and the form can be completed with a keyboard alone.
  • These legal pages work with JavaScript disabled. Nothing here depends on a script to become visible.
  • Layout and text reflow down to small screens and stand up to zooming.
  • Decorative graphics are hidden from assistive technology with aria-hidden so they are not read out as noise.

Where it falls short

An accessibility statement that claims perfection is not worth much, so here is the honest list:

  • No independent audit has been carried out. Our conformance claim is self-assessed, based on our own testing with a keyboard and a screen reader. It is not a certification.
  • The embedded Google map on the contact page is third-party and we do not control its accessibility. That is why our service area and hours are written out as text beside it — you never have to use the map to get the information.
  • Colour contrast has been checked by eye and by design intent rather than measured across every possible combination of text and background.
  • Fonts load from Google Fonts. If that request fails, the page falls back to Georgia and your system sans-serif, which changes the appearance but not the content.

We would rather list these than pretend they are not there. If any of them is getting in your way, tell us and it moves up the queue.

Telling us about a problem

Use our contact form. It helps if you can include the page address, what you were trying to do, and what happened instead — along with your browser or assistive technology if you know it. We aim to reply within one business day.

If something on this site is unusable for you, ask and we will supply the same information another way — by email, in a call we arrange with you, or in a different format. That applies to anything on the site, not only these legal pages.

How we assessed this

Self-assessment against WCAG 2.2 Level AA, last reviewed 29 July 2026, using keyboard-only navigation, a screen reader, browser zoom and reduced-motion testing. We review this page when the site changes.