Accessibility statement

Every page, in both the dark and the light theme, on 7 October 2026, the day the site moved to its new design, again on 11 October 2026 after the results became a row of slides and the charts gained explanations, on 12 and 13 October 2026 after the results started to move on their own and the header began to stay at the top, on 15 October 2026 after the row of results lost its buttons and gained a case study, on 18 October 2026 after two more case studies were added, both of which also open from /services, and on 22 October 2026, when the moving row was also checked by hand against the requirements no automated test can see:

• Automated - axe-core against WCAG 2.0, 2.1 and 2.2 at A and AA, with every accordion and panel opened so nothing was skipped, and with the cookie banner both open and closed.
• Contrast - measured on every piece of text against the colour actually behind it, not against the page background. Borders of form fields and checkboxes, and the bars in the charts, were measured too.
• Keyboard - every control reached and operated without a mouse, with a visible focus ring, and never hidden behind the header, the cookie banner or the button fixed to the foot of the screen on phones.
• Screen sizes - widths from 320 to 3440 pixels, phones and tablets held both ways, which covers 400% browser zoom on a laptop.
• Your settings - reduced motion, increased contrast, Windows High Contrast, overridden text spacing, text at 200% on phones and laptops, and JavaScript switched off.

What I have not done is have the site used by people who rely on a screen reader every day. Automated and manual checks catch a lot; they do not replace that. These checks also ran in Chromium, the engine behind Chrome and Edge; Safari and Firefox were not part of this round. If you use assistive technology, or another browser, and something is awkward, I would genuinely like to know.

• If your device asks for less motion, nothing moves on its own: the row of results stays still, the bars in the charts are simply there, and only the header settles and its reading line fills as you scroll.
• If your device asks for more contrast, the quieter greys and hairlines get stronger.
• In Windows High Contrast, buttons, form fields, tags and the cookie checkboxes keep visible edges, and the bars in the charts stay visible.
• The results from client accounts run past slowly on their own. They come to a stop while your mouse is over them and stay still while your keyboard is in them. You can move them with the arrow keys, a swipe or by dragging. A screen reader meets each result once.
• Three results open a case study, and two of the case studies open from /services as well. Each is a dialog: focus moves into it, Escape or the close button closes it, and focus comes back to the link you opened it from; its “Get your free review” link takes the focus to the contact form. Without JavaScript the same link shows it over the page, with a link back. The clients’ logos beside their names are decorative, so a screen reader reads only the name.
• Every chart has its numbers written next to the bars, so nothing depends on reading a length or a colour. On the services page, the name of each measure opens one plain sentence on what it means; with JavaScript off, the sentences are simply there.
• The contact form says in words what is missing and moves you to it, instead of relying on the browser’s pop-up.
• There are no time limits anywhere, and every page can be read with JavaScript turned off.
• A skip link at the top of every page goes straight to the content.
• The header stays at the top while you scroll, with a thin line under it that shows how far down the page you are. In a window less than about 480 pixels tall, or at very high zoom, it scrolls away with the page so it never covers much of the screen.