This site should work for everyone who uses it, including people who navigate with a keyboard, use a screen reader, zoom in, or turn off animation. This page explains the standard I aim for, what has been done to meet it, and how to tell me when something falls short.
The standard
The site aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Those guidelines are published by the World Wide Web Consortium and are the standard most UK organisations work to.
Aiming for a standard is not the same as meeting it everywhere, so the section on known limitations below is kept up to date rather than left optimistic.
What has been done
- Colour contrast. Text and interface colours are chosen to meet the AA contrast ratios in both the light and dark versions of the site.
- Keyboard access. Menus, buttons, the free tools and forms can be reached and used without a mouse, with a visible focus outline.
- Reduced motion. If your device is set to reduce motion, animations such as the typing search example, the scrolling client list and the pulsing availability indicator stop.
- Structure. Pages use one main heading and a logical heading order, so screen reader users can move through them by section.
- Text alternatives. Meaningful images carry alt text. Decorative ones are hidden from screen readers.
- Zoom and reflow. Pages reflow to a single column on narrow screens and can be zoomed to 200% without content being cut off.
- Your data stays in your browser. The SEO calculator reads files locally, so nothing about using it depends on uploading anything.
How it has been checked
The site was checked on 23 September 2026, across 19 pages covering every template: the homepage, service and case study pages, the tech stack, the blog index, a blog post, a series page, the free tools, the contact and assessment forms, a policy page and the 404.
Automated checks covered the parts a machine can judge: a declared page language, one main heading per page with no skipped heading levels, alt text on every image, a label on every form control, an accessible name on every link and button, no duplicate element IDs, a skip link, main and navigation landmarks, and a viewport that allows zooming.
Colour contrast was calculated for every colour pair the design uses, in both the light and dark parts of the site. The lowest ratio found was 5.7 to 1, against the 4.5 to 1 that AA asks for on body text.
Built-in behaviour was verified in the code: a visible focus outline on everything focusable, and animations that stop when a device is set to reduce motion.
One issue was found and fixed the same day: the blog index moved from a level one heading straight to level three, because its section labels were styled text rather than real headings.
Known limitations
No screen reader testing has been done yet. The automated checks and the code review cover structure, naming and contrast, but they are not the same as someone using the site with NVDA, JAWS or VoiceOver. That testing is planned, and this section will say what it found, including anything unflattering.
The booking calendar is Google’s, not mine. The appointment scheduler embedded on the contact page is built and controlled by Google, so its accessibility is outside my control. If it causes you a problem, email or WhatsApp reaches me the same way, and I will arrange the call by hand.
Some case study images carry information. A few charts and screenshots show data that is described in the surrounding text rather than fully in the alt text. If you hit one where the text does not carry the point, tell me and I will rewrite it.
Some content comes from outside this site, such as embedded booking tools and links to third-party pages. I can’t guarantee those meet the same standard, though I’ll look for an alternative if one causes you a problem.
Tell me if something doesn’t work
If you can’t use part of this site, or you need information in a different format, please get in touch. Tell me the page and what went wrong, and I’ll reply within five working days with either a fix or another way to get you what you need.
You don’t need to explain why you need something, and you won’t be asked to.
Related
How content on this site is researched, written and corrected is covered in the editorial policy.
This statement was last reviewed in November 2026.