Accessibility statement
Last updated
Our commitment
We build this site, and the sites we build for clients, so that people using a keyboard, a screen reader, magnification or reduced-motion settings can use them. That is a design and engineering commitment rather than a plugin, and it is worked into how pages are built rather than added afterwards.
Accessibility is never finished. This page says what we target, what we know is imperfect, and how to tell us when something is wrong.
The standard we build to
We target WCAG 2.1 level AA for this site. We do not claim full conformance, because a claim of full conformance without an independent audit is not worth much. What we claim is that the criteria below are deliberately designed for, checked during the build, and fixed when a gap is reported.
What that means in the build
- Keyboard operation. Every interactive control is reachable and usable with a keyboard, focus order follows the visual order, and focus is never trapped anywhere it cannot be escaped.
- Visible focus. A clear focus outline is drawn on every focusable element, against every surface it can appear on, in both light and dark mode.
- Contrast. Text and interface colours are chosen as pairs and checked against the surface behind them, in both colour schemes, rather than picked in isolation.
- Semantic structure. One main heading per page, headings in order, real lists, real tables with header cells, real buttons and links rather than clickable boxes.
- Text alternatives. Every meaningful image carries descriptive alt text written for the place it is used. Decorative diagrams and background motifs are hidden from assistive technology rather than described pointlessly.
- Motion. Every animation honours the operating system reduced-motion setting, and anything that moves on its own carries a visible control to stop it.
- Zoom and reflow. Pages work at 200 percent zoom and at 320 pixels wide without horizontal scrolling or loss of content.
- Forms. Every field has a real label, errors are described in text rather than by colour alone, and inputs are large enough not to trigger zoom on a phone.
- Colour is never the only signal. State and meaning are always carried by a label, an icon or a shape as well as a colour.
The accessibility controls on this site
The control in the corner of every page lets you scale the text, raise contrast, reduce motion and highlight links. Your choice is remembered in your own browser and is never sent to us. It sits alongside, not instead of, the underlying build: a settings panel does not make an inaccessible page accessible.
Known limitations
Stated plainly rather than omitted:
- Some pages embed third-party content, such as a booking calendar or a chat widget. We do not control the accessibility of that embedded content, and where it falls short we will provide the same service by email or phone.
- Several pages carry technical diagrams drawn as inline graphics. Where a diagram carries information, the same information is written in the surrounding text. If you find one where it is not, that is a bug and we want to hear about it.
- This site has not had an independent accessibility audit. If you need one before working with us, say so and we will discuss arranging it.
Sites we build for clients
Every site we build for a roofing company is built with WCAG 2.1 level AA in mind, using the same practices listed above, and ships with its own accessibility statement in the client business name. We say "built with in mind" deliberately: we are a website studio, not an accessibility auditor or a law firm, and we do not certify that any site meets a legal standard or guarantee compliance with any statute. Where accessibility is a contractual or regulatory requirement for a client, we recommend an independent audit and we will work to its findings.
If content a client supplies creates an accessibility problem, for example an image of text or a video without captions, we will tell them and suggest the fix.
How to report a problem
Email with the page address and a description of what went wrong, including the browser and assistive technology you were using if you know them. A person reads it. We aim to acknowledge within one working day and to tell you what we are going to do about it and when.
If something on this site is blocking you from getting information you need, say so in the message and we will send you what you need in another format rather than waiting for the fix to ship.