Skip to content

Accessibility

I want this site to work for everyone who lands on it, including people using a screen reader, a keyboard only, magnification, or their operating system's high contrast mode.

This statement says what has been built, what has been checked, and what has not. It will be wrong the moment any of that changes, so it carries a date.

The standard I am aiming at

WCAG 2.2 level AA.

I am not claiming it yet. The last section says why.

What has been tested, and what the test found

On 13 September 2026 I drove a real browser through the site and measured these rather than eyeballing them.

Keyboard, every stop. I tabbed through the whole site at both a phone width and a desktop width, recording every place focus landed. Thirty-two stops on a desktop screen, twenty-six on a phone. Every one of them showed a visible focus ring, none of them was an invisible trap, and the order followed the page. Focus wraps back to the top rather than escaping into nothing.

The skip link works properly. It moves focus into the main content, not just the scroll position. That distinction matters if you are using a keyboard or a screen reader, and it is the part most sites get wrong.

Reflow at 320 pixels. Every page, at the narrowest common screen size: no horizontal scrolling anywhere, on any page. That is the harder version of the zoom requirement, so magnifying the text does not break the layout either.

Target sizes. Some links in body text are smaller than the 24-pixel minimum, which is allowed when nothing else sits close enough to mis-tap. I measured that rather than assuming it: on every page, a 24-pixel circle centred on each small link touches nothing else. No page fails.

Motion. Zero animations running, on any page. No carousels, no video backgrounds, no parallax, no scroll-triggered movement. Nothing on this site moves unless you move it.

Speed. The main heading appears 476 milliseconds after the request, and it is the largest thing on screen, which is the number that matters for how fast a page feels. Nothing shifts around while it loads.

What else has been done

Colour and contrast. Every text and background pairing was measured rather than eyeballed, and the palette was changed where it failed. Three combinations were rejected during the build and replaced: a green at 3.30:1 on the dark band, a button hover state at 2.30:1 against the page, and a white focus ring at 2.59:1 against the button behind it. The site is pinned to one light theme, because its dark variant made two different surfaces the same colour and the page stopped reading as designed.

Headings. Every page has exactly one h1 and no skipped levels. This was wrong at one point during the build, on the template that carries most of the writing, and was fixed.

Controls. The diagnostic's options are real radio buttons inside a labelled group, so arrow keys move between them the way your browser already expects. Advancing a question moves focus to the new question rather than leaving you at the bottom of the previous one.

Text. Body text is 16 pixels or larger and set in a measured column. The typeface is served from this site rather than from a font network, so no third party learns your IP address because you read a page here.

What has not been checked

These are real gaps, not caveats.

  • A screen reader pass. No testing with NVDA, JAWS or VoiceOver has been done. The structure is right on paper and that is not the same thing.
  • Windows high contrast and forced-colours mode. The site was built for it, with focus rings that fall back to a real outline and selected states carried on shape rather than only on colour. I have not been able to test it in it.
  • Any testing with disabled users. The most useful check of all, and the one not done.

Until those are done I am not claiming conformance, and I would rather say so than publish a badge.

Known limitations

  • The site needs JavaScript. It is built on a platform that renders in the browser, so with scripting turned off you get nothing. That is a real limitation and I am not going to dress it up as a preference.
  • There are no images carrying meaning on the site, so there is nothing to describe. If that changes, alternative text is a required field on the image record rather than an optional one, so an image cannot be added without it.

If something does not work

Tell me and I will fix it. Say what page you were on, what you were trying to do, and what happened. If you use assistive technology, telling me which one helps.

Email me at hello@scaleruleconsulting.com. I have deliberately put an address here rather than only a form, because a form is no use to you if the form is the problem.

I will reply within 2 business days and tell you honestly whether it is something I can fix quickly or something that needs more work.

If I do not sort it

You can contact the Equality Advisory and Support Service, which handles complaints about accessibility in the United Kingdom.

About this statement

It applies to this website only.

Tested on 13 September 2026 by driving a real browser through every page and measuring, plus manual inspection and reading the code. The gaps listed above are the honest boundary of that.