Skip to main content
John Slater.

Accessibility statement

Last updated

Accessibility is a big part of my day job, so this site should walk the talk. My aim is for every page on slaterjohn.com to meet WCAG 2.2 level AA – and in most places it should do better than that.

What I've done

Accessibility went into this site from the start rather than being patched in later:

  1. Semantic HTML throughout – proper headings, landmarks, lists and labels.
  2. Every page is fully usable with a keyboard, with visible focus states.
  3. Text and interface colours meet contrast requirements in both light and dark mode.
  4. Every image has alt text written by hand, including the images in older articles.
  5. Animations and transitions are disabled when your device asks for reduced motion.
  6. Text can be resized up to 200% without anything breaking or being cut off.

How I test

I use the same combination I recommend in my article on accessibility testing – automated tools alone can't catch everything, so this site gets automated audits (Lighthouse and Axe), manual testing against the WCAG 2.2 success criteria, and real use with a keyboard and screen reader.

Known limitations

I'd rather be honest about the gaps than pretend there are none:

  1. Some older articles embed third-party content – CodePen demos, YouTube videos and a Spotify playlist. I can't vouch for the accessibility of those embedded players, though I've kept them supplementary so no article depends on one.
  2. Screenshots in older posts migrated from the previous version of this site are described in alt text, but the text inside those images isn't available in any other form.

Found a problem?

If anything on this site is hard to use with your setup, I really do want to know – that kind of feedback catches what testing misses. Message me on LinkedIn and I'll fix it.