I want this website to be usable by as many people as possible, whatever technology they use and whatever their needs. This page explains how I try to achieve that, where the site currently falls short, and how you can get in touch if something does not work for you.

What I aim for

I aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AAA. In practice, that means the site is built to:

  • work with keyboard navigation, so you do not need a mouse, with a visible focus indicator and a skip-to-content link;
  • offer a light and dark theme toggle, with text colours in both themes tuned to the enhanced (AAA, 7:1) contrast ratio;
  • allow you to resize the text in your browser without content breaking or overlapping;
  • use semantic HTML, so screen readers and other assistive technologies can make sense of the structure;
  • respect your operating system’s reduced-motion preference, disabling animations and smooth scrolling when you ask for that;
  • provide touch and click targets of at least 44×44 pixels for standalone controls;
  • describe images with alternative text, including in the older parts of the blog archive.

This is my personal academic site, which I maintain in my own time, so I cannot promise the polish of a large institution. I do, though, take accessibility seriously and try to improve things steadily.

Known limitations

I want to be honest about the areas where the site is not yet fully accessible:

  • The blog archive goes back to around 2008. I have been back through the archive to add alternative text to images, but some descriptions of very old images are reconstructed from context and may be imperfect. If one misleads you, please tell me.
  • Some linked PDFs, particularly older copies of academic papers and documents from the 2010s, are not tagged, so they may not read well in a screen reader. (My CV, which is generated automatically, is a tagged PDF.)
  • Some older embedded media (videos and audio players from third-party services) do not yet have captions or transcripts. WCAG 2.2 at level AAA also asks for sign-language interpretation of pre-recorded audio content, which I am not currently able to provide.
  • A few directories preserve old conference micro-sites and project pages exactly as they were published, for the historical record. These archives pre-date the current site and are not remediated.
  • Third-party services that some pages link out to or embed (for example, video and audio players) have their own accessibility characteristics that I cannot control.

I am working through these as time allows, and newer content is written with accessibility in mind from the start.

Fixing problems

I review the site’s accessibility periodically, at least once a year. When someone reports a specific problem, I aim to address it within 30 working days. Where a fix is not straightforward or my personal circumstances require a longer window, I will tell you what I plan to do and roughly when.

Giving feedback

If you find anything on this site difficult or impossible to use, please tell me. Email me at martin@eve.gd with the page address and a short description of the problem, and I will do my best to help. I aim to respond within 10 working days.

Your feedback genuinely helps, and I am grateful for it.

This statement was last reviewed in July 2026.