Accessibility statement
This site is run by me, Mike Tattersall. I want as many people as possible to be able to read it, whether that's on a screen, with a screen reader, by voice, or by keyboard alone.
What I've done
The site is plain HTML, CSS, and a small amount of JavaScript, with no framework in the way. Every page has a "Skip to main content" link, semantic headings, and landmark elements (header, main, footer), so the structure holds up for a screen reader or a keyboard-only user, not just someone looking at the page. Every interactive control is a real button, link, or labelled form field, reachable and usable with a keyboard alone, with a visible focus style. I checked text and control colours against WCAG's contrast minimums (4.5:1 for text, 3:1 for control boundaries like the blog filter pills) rather than assuming they'd pass. The blog's content-type filter announces how many posts are showing to screen readers as well as showing it on screen. Decorative elements, like the quote mark on the homepage, are hidden from assistive technology so they don't get read out as noise. Links that open in a new tab say so, for anyone who wouldn't otherwise know.
What I'm aiming for
I'm holding this site to WCAG 2.2 AA. That's not a legal requirement here, since it's a personal site rather than a public sector service, but it's the standard I'd expect from anyone writing for this audience.
What I haven't done
I've reviewed this manually and with AI-assisted tooling, not with a full professional audit or an automated scanner like axe or Lighthouse, so there will be gaps I haven't found yet. Older content (the career history page and the blog posts themselves) hasn't had the same scrutiny as the homepage.
Reporting a problem
If something on this site doesn't work for you, email me and tell me what happened and what you were using (browser, screen reader, device). I'll fix what I can.
Last reviewed: August 2026.