Accessibility statement

We aim for the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. That is a target, not a certificate: no outside body has audited the site, and we treat the standard as a yardstick we check against rather than a finished result.

In practice the target shapes everyday choices on every page:

• text colour set against its background with enough contrast to read
• one H1 per page and headings in order, so a screen reader user can jump from section to section
• links and buttons with names that make sense out of context
• form fields with visible labels, and error messages that say what to fix
• every control reachable and usable from the keyboard, with a visible focus outline
• text that stays readable when the browser is zoomed or the phone is turned sideways

Three kinds of checking are carried out on the pages, and repeated when a page changes in a significant way.

Automated scans with axe

We run the axe accessibility engine over pages to catch the faults a machine can find: missing form labels, low colour contrast, empty links, broken heading order and missing language attributes. Axe finds only part of the possible problems, so a clean scan is a starting point.

Keyboard-only checks

We move through pages using the Tab key, Shift and Tab, Enter and Space alone, with the mouse put aside. We look for a visible focus marker, a sensible order, no trap that holds focus, and a way to open and close the menu, the checklist sections and the enquiry form.

Screen reader spot checks

We spot check key pages with a screen reader, listening for the page title, the heading list, the landmark regions, the form labels and how the checklist sections announce themselves. These are spot checks on selected pages, not a full test of every page with every screen reader and browser.

We would rather you heard about problems from us than found them alone. These are the places most likely to cause difficulty.

• Embedded Google content. Where a page shows our Google Business Profile, the content comes from Google and sits outside our control. A link to the profile is the alternative.
• Photos of roofs. Photos carry short text descriptions of what they show, but some detail, such as the state of a ridge or a lead flashing, cannot be fully put into words. The surrounding text describes the same condition.
• Long pages. Some guides are long. Each has a heading structure and, where there are several sections, a list of them near the top.
• Documents. A written quote or survey report is something we send to you directly, and we can set it out in a format that suits you if you ask.

If you find a barrier that is not listed here, please tell us, because that is how it gets fixed.

If something on the site stops you reading it, using the form or finding what you need, you can reach us on 01823 297042, by WhatsApp, through the enquiry form or by email to the address printed at the foot of this page.

Tell us the page, what you were trying to do and, if you know it, the device and any assistive technology you use. We will reply with a fix, a workaround or the information in another form, such as a phone call, a plain email or large print.

You do not need to use the website to arrange a roof survey. A phone call works equally well, and we will describe the survey photos to you over the phone if that helps.

If we cannot resolve an accessibility concern, you can use our complaints procedure, which sets out each step and who can advise you outside the business. Our complaints procedure applies to the website in the same way as it does to a roofing job.

We review this statement when pages are added or changed in a significant way, and after any accessibility complaint that leads to a fix. When we repair a fault, we re-test the page with the same method: axe first, then the keyboard, then a screen reader on the pages visitors reach first.