Accessibility

We want everyone to be able to use this site, whatever device, browser or assistive technology they use. We build against the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, and we treat that as ongoing work rather than a box ticked.

What is in place today

The site is built with semantic HTML and a heading structure that runs in order on every page. Every meaningful image carries alternative text written for the picture rather than lifted from the file name, and purely decorative artwork is hidden from screen readers so it never gets in the way.

Navigation and interactive controls are labelled for assistive technology, and everything that can be clicked can be reached and operated with a keyboard. The first thing in the tab order is a skip link straight to the main content.

Animation respects your system's reduced-motion setting: turn that on and the movement on this site stops rather than merely slowing down. Text resizes with your browser settings, the layout adapts from a 320px phone to a large desktop screen, and no page scrolls sideways at any width in between.

Text contrast has been measured against the actual painted background rather than assumed, including where text sits over a photograph. The lowest reading anywhere on the site is 4.7:1, against a requirement of 4.5:1.

Two things fixed on 2 September 2026

Tap targets. Several links were drawn smaller than the 24 by 24 pixels WCAG 2.2 asks for - the main navigation, the footer columns and legal row, the small Google marks on reviews, and the cookie controls. Each one already met the criterion, because it allows a smaller target where nothing else sits within 24 pixels of it, and every one of ours had that clearance. Passing on an exception is not the same as being comfortable to hit on a phone, so the area that accepts your tap is now at least 24 by 24 on all of them. Nothing moved: the text is exactly where it was, and no two targets overlap.

Keyboard focus. Menus, buttons and form fields already drew a clear outline. Ordinary links fell back to whatever ring the browser draws, which is acceptable but is faint in some of them and different in all of them. Every link on the site now draws the same two pixel outline. We walked all 294 keyboard stops across the seven main pages to check it, comparing what is painted on screen before and after focus rather than trusting the stylesheet.

What we know is not right yet

Nothing specific today. That is not the same as nothing at all: this is a new site, the section below sets out honestly where our testing does not reach, and we expect there are things we have simply missed. Anything you find goes on this list.

Testing, honestly described

Pages are checked in current versions of Chrome and Firefox on Windows and on Android hardware we own, alongside automated checks for heading order, alternative text, contrast and console errors. We do not own an iPhone, so testing on iOS is done through online tools and on the devices of clients and friends. If something is wrong specifically in Safari, there is a good chance we have not seen it - please tell us.

Tell us

If a page is awkward with a keyboard, a screen reader announces something oddly, contrast is hard on your eyes, or anything else here gets in your way, that is a bug to us and we want to know. Report it through the contact form and it goes to a person who can fix it, not into a queue.

If the form itself is the thing that is difficult, write to us at 29 Broomfield Avenue, Leigh on Sea, Essex, SS9 4BL and we will find another way to help.

The sites we build

The same intent applies to the websites we build for clients: proper headings, real alternative text, keyboard-reachable menus and readable contrast are part of every build rather than an extra. We say what has been done and what has been tested. We do not sell accessibility certification, and we will not claim conformance on a client's behalf either.