Skip to content

SheetAccessibility

StandardWCAG 2.2 AA, tested on every route

StatusPartially compliant, one exception

Reportcraig@craighawkes.dev, inside the hour

Accessibility statement · prepared 24 September 2026

What's tested, and where it falls short.

Everything below is something a test or a gate on this site already checks, with the counts read from the last run rather than typed, and the one exception named rather than left for you to find.

  • How far it goes

    This site is tested against WCAG 2.2 at level AA on every route, and it's partially compliant, because of one exception below that's there on purpose. The contrast gate holds 56 colour pairings before every deploy. Of those, 45 are text held at 7:1, the AAA level. Another 4 are held at 4.5:1, the AA level. The last 7 are controls and marks, held at 3:1. Nobody independent has audited it, so read this as what's tested and how, not as a certificate.

  • What's tested, every time

    66 accessibility tests run axe against the WCAG 2.0, 2.1 and 2.2 A and AA rules on every route, at phone, tablet and desktop widths, and report the AAA rules separately rather than leaving them out. Other tests hold what axe can't see: nothing scrolls sideways from 280 pixels wide, which is stricter than 400% zoom asks for, text survives a reader's own letter, word and line spacing, focus is never entirely hidden behind the navigation, and the navigation's controls stay at 44 pixels or more.

  • The settings you change yourself

    Forced colours, which is what Windows High Contrast uses, reduced motion and a request for more contrast are all switched on in the tests, on one page of every kind the site has. In forced colours the violation chart has to keep its bars and focus has to stay visible. With reduced motion nothing is allowed to move on its own. Asking for more contrast firms up the hairlines. The parts that differ between browsers are checked in Chromium, Firefox and WebKit, which is Safari's engine.

  • What isn't right yet

    The inclusive.io case study embeds the first version of that app on purpose, as the before, and axe finds nine problems in it, one of them critical, counted on 24 September 2026. That's why this page says partially. The now-playing strip cuts a long track title to one line, though the strip links to the track, and on the home page the whole title is in the band under Enquiries. Tap targets are held at 44 pixels in the navigation, not yet on every link on every page. And the two apps embedded in that case study draw their own focus rings inside their own frames, where this site's tests can't see.

  • If something doesn't work for you

    Email craig@craighawkes.dev with the page and what happened. A person answers inside the hour in UK working hours, the same promise the contact sheet makes, and anything you report goes on this page until it's fixed.

  • When it was last checked

    Prepared on 24 September 2026. The whole suite last passed on 24 September 2026, all 540 tests, and the gates that hold contrast run before every deploy, so every number on this page is read from those runs rather than typed.