Skip to content

Accessibility

Built to be usable by everyone.

I want this site to work well no matter how you browse it, whether that's with a keyboard, a screen reader, magnification, or reduced motion. Here's where things stand, honestly, and how to tell me when something falls short.

Last updated: 31 May 2026

What I aim for

I'm working towards the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA as the target for the whole site. Most of the site meets that today, and I treat anything that doesn't as a bug to fix rather than something to leave alone.

What's in place

  • A “skip to content” link so keyboard users can jump past the header straight to the main content.
  • Full keyboard navigation with visible focus outlines on links, buttons, and form fields.
  • Proper landmarks and a logical heading order, so screen readers can move through the page structure.
  • Form fields with clear labels, and errors that are announced and tied to the field they belong to.
  • Motion that respects your “reduce motion” system setting: animations are dialled back or switched off.
  • A light and dark theme, and layouts that hold up when you zoom in or use a small screen.

Known limitations

I'm being straight with you: a few bits of small, secondary text (things like fine print and meta labels) may not yet hit the AA colour-contrast bar in every theme. I'm improving these as I go. Some embedded or third-party content may also vary. If anything makes the site hard to use, I'd genuinely like to know.

Report a problem

If you hit a barrier, or something just doesn't work the way it should, tell me what happened and I'll do my best to fix it. The more detail the better: the page, your browser, and any assistive tech you were using all help.