Accessibility Statement

This statement is deliberately worded as "working toward" rather than "conforms". See the note at the end for why that matters and when it may be changed.

Our target

We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) version 2.2, Level AA.

We say "working toward" rather than "conforms" on purpose. A conformance claim should rest on a completed audit including testing with real assistive technology, and ours has not had that yet. What testing has been done is set out below, honestly, including what it does not cover. Sites that claim full conformance without testing for it are common, and the claim is worth nothing.

What has been done

The site has been built with accessibility as a requirement rather than an afterthought:

• Real semantic HTML, with headings in a logical order
• Every form field has a visible, properly associated label
• Form errors are announced to screen readers, not signalled by colour alone
• The whole site can be operated by keyboard, with visible focus indicators
• Colour contrast meets the AA thresholds for text and interface components
• Images that carry meaning have alternative text, and decorative ones are hidden from screen readers
• The site works when zoomed to 200 percent and at narrow widths without loss of content
• Motion respects the reduce motion setting in your operating system
• The cookie banner is keyboard accessible and does not trap focus

What has been tested, and how

Every page on this site is checked automatically on every change, as of 16 August 2026:

• Automated testing with axe, covering WCAG 2.0, 2.1 and 2.2 at Levels A and AA, across a representative page of every kind on this site: the home page, the services list and one page from each half of the catalogue, the request form and its confirmation, the about, contact and service area pages, a town page, and each of the legal pages. Each is checked twice, once with the cookie banner showing and once with it dismissed, plus the cookie settings dialog while open and the request form while showing errors.
• Keyboard-only testing of the service request form, confirming every control can be reached in a sensible order, that focus is always visible, and that the form can be completed and sent without a mouse.
• Colour contrast calculated for every combination of text and background used in the design. Where a band opens with a photograph behind its text, the photograph is composited so that no pixel behind a word can be lighter than the flat colour it sits on, and the image files themselves are measured to confirm it, so those pairings are covered by the same calculation.
• Checks on the page structure itself: one main heading per page, headings in order, landmarks present, every control labelled, and alternative text on every image.

All of these currently pass.

Known limitations

Automated testing is genuinely useful and genuinely limited. Tools like axe reliably catch about a third of accessibility problems: the ones a machine can see, such as a missing label or insufficient contrast. They cannot tell you whether a page actually makes sense when read aloud, whether an error message arrives at a useful moment, or whether a task can be completed without frustration.

So, plainly, the gaps we know about:

• This site has not been tested with a screen reader by a person using one. That is the single most valuable test remaining and it is why this statement says "working toward" rather than "conforms".

• The town pages share a template. Each is checked in the same way, but only one of them is scanned automatically on every change. They differ in their words rather than their structure, so a fault in one would be a fault in all, but this is stated rather than glossed.

• Content provided by other companies is outside what we can test or fix. If you use the online booking window, that window is operated by Workiz and runs inside a frame on our page. We cannot inspect it with our own tools, we cannot correct problems inside it, and we cannot re-test it when Workiz changes it. Nothing on this site depends on it: everything you can do there you can also do by calling us, or by sending a service request, which is entirely on our own site and is covered by everything above. If the booking window is difficult to use, please tell us, and please use the phone number or the request form in the meantime.

• No testing has been done with voice control or screen magnification software.

• Contrast is calculated from the design system and from the image files themselves, rather than sampled from a browser rendering of the finished page, so an unusual combination could in principle be missed.

None of these is a reason to wait before telling us about a problem. If something does not work for you, the section below is the fastest route to getting it fixed.

Telling us about a problem

If any part of this site is difficult or impossible for you to use, please tell us. It is genuinely useful to know.

Call 855-207-8828 or email [email protected]. Tell us the page and what went wrong, and we will get back to you.

If you cannot use this website to reach us, calling works. We can take a service request over the phone exactly as we can through the site, and nothing on the website is the only route to reaching us.

Fixing problems

We treat accessibility problems as defects and fix them accordingly. When something is reported to us we will confirm we have received it, look into it, and tell you what we found.