Accessibility Statement

Accessibility makes things better for everyone. In all of my work, even the bits other people will never see, I strive to make things easier to use and as accessible as possible. That isn’t always easy, especially in a visual-heavy career!

For my website and my digital work, I comply with the Web Content Accessibility Guidelines (WCAG 2.2) at AA level at minimum. This is the global standard of web accessibility and is largely the basis of digital accessibility.

I also use excellent accessibility standards and advice from GOV.UK, BBC, Mozilla, RNIB, The A11y Project, and others. Even my primary typeface is provably more accessible than most.

It helps me set a baseline around the following:

• Visual accessibility
  • Colours meet minimum contrast ratios for better legibility
  • Zooming in doesn’t break the website or make the content overflow
  • Code allows screen readers (JAWS, NVDA, TalkBack and others) to narrate the whole site and describe images clearly
• Audible accessibility
  • Closed captions and a transcript are available for any audio content
• Motor accessibility
  • Native keyboard-only or specialist pointer control and navigation
• Cognitive accessibility
  • Reduced motion to reduce overload
  • Clean, clear writing style
  • Minimal distractions or unnecessary decoration (for example, emojis)
  • No autoplay
  • No pop-ups or modal windows
• Technological accessibility
  • Modern, compliant HTML, CSS, and JavaScript
  • ARIA tags to help assistive tools
  • Clean code with DRY (Don’t Repeat Yourself) methodology
  • Locally hosted content and tools to avoid calling external scripts

Also, I avoid PDFs wherever possible. Even the most accessible PDFs aren’t great.

I hold myself to a high standard; practice what you preach. Thankfully I love testing how accessible things are and making the little tweaks necessary, all to give people the best and most equitable experience possible no matter how they engage with content.

Multiple tools help me test, including but not limited to:

• WAVE (WCAG 2.2 checks)
• aXe Tools (general digital accessibility)
• Vispero Colour Contrast Analyser, Sim Daltonism (colour vision deficiency simulation)
• Lighthouse (performance, ARIA)
• JAWS, TalkBack, VoiceOver (screen reading)
• NoCoffee (vision impairment simulation)
• GTMetrix (performance, connection simulation)
• Firefox DevTools (technical checks)

I also navigate my site using just my keyboard, or just my mouse and on-screen keyboard to see how things perform and feel.

All of the above tools are tested on a mix of Firefox, Chrome, and Edge (various 2026 builds) on Windows 10 and 11, Android (stock and GrapheneOS), and macOS Tahoe.

None of this testing is a replacement for actual user testing. I try to include user testing in my projects, ideally with people who have lived experience with assistive technologies.

No known issues. This site fully conforms to WCAG 2.2 AA and partially conforms to AAA. No known issues remain as of 1 September 2026.

If standards, technologies, or best practices change I try to update the site accordingly but that doesn’t mean everything is fully accessible. I also cannot guarantee the accessibility of external websites that I link to.

However, if you have any feedback, run into any problems, or think something can be better, please let me know via email. I’d love to chat about what can be improved!