Accessibility

This site should work for you whatever you’re using to read it: keyboard, screen reader, phone, or a browser with motion turned down. Here’s what’s built in, and how to tell me when something doesn’t work.

What’s built in

• Keyboard: everything is reachable by keyboard, with visible focus. Press ? anywhere for the shortcuts: / opens search, j and k jump between headings, and g then m, t or c goes to the menu, the content or the table of contents.
• Skip links to navigation, content and (on resource pages) the table of contents.
• Focus that follows you: after you follow a menu link, focus lands in the right place on the new page instead of back at the top.
• Screen readers: semantic HTML with landmarks and a proper heading outline, labelled controls, and a live region that announces where you’ve moved to. Collapsed menus are inert, so hidden items aren’t tabbed through or read out.
• Motion: if your system asks for reduced motion, animations and smooth scrolling are off.
• Light and dark: follows your system setting.

Under the hood

A Hugo static site with plain CSS, OKLCH colour variables, no framework and no CDN: the font (Barlow), the icons (SVG via CSS masks) and the search (Pagefind, indexed at build time) are all served from here. The only third-party script is Microsoft Clarity analytics. Assets are content-hashed and the site deploys to GitHub Pages from GitHub Actions on every push.

Something not working?

I haven’t had the site formally audited, so there will be gaps. If something doesn’t work with your setup, email me with what you were trying to do, what happened, and which browser and assistive tech you’re using. I’ll fix what I can.