Accessibility

Accessibility Statement

Last reviewed August 30, 2026

A large share of the people this site is built for are disabled. Building it inaccessibly would contradict the entire point of it, so this page says what we have actually done, what we know is still wrong, and how to tell us when we have missed something.

The standard we work to

We aim to meet WCAG 2.2 Level AA. We are not claiming full conformance. We are claiming that it is the target and that we measure against it.

What we have done

Specific decisions, not intentions:

  • Contrast beyond the minimum. Body text measures 16.66:1 against the background, where AA requires 4.5:1. Secondary text measures 6.71:1.
  • No pure black, no pure white. White on black causes halation, where letters appear to glow and smear. It affects readers with astigmatism and triggers migraine for many with light sensitivity. Both are common in this audience. We use a near-black and a warm off-white instead, which keeps the contrast without the glare.
  • Our brand purple is never used for small text. It measures 3.14:1, which fails. It appears only in rules, borders, and filled shapes. Links use a lighter purple that clears AA.
  • Reduced motion is honoured. If your system requests reduced motion, transitions and animations are disabled. Vestibular symptoms are common here and this setting is widely ignored.
  • Visible keyboard focus. Every interactive element shows a clear focus ring. We have not removed default outlines without replacing them.
  • Generous line height and text size. Set for reading with fatigue and cognitive fog, which shaped the typography more than aesthetics did.
  • Semantic structure. Real headings, real lists, real landmarks, so screen readers and reader modes can navigate.
  • Text that resizes. Zoom to 200% without loss of content or function.

Known gaps

Listing these because a statement without them is not a real statement.

  • [AUDIT FIRST, THEN LIST WHAT IS ACTUALLY OUTSTANDING. Delete any item below that does not apply.]
  • Some older articles may have images with missing or inadequate alt text. We are working backwards through the archive.
  • Third-party embeds — video players, forms, social widgets — are not fully under our control and may not meet the same standard.
  • Some PDFs may not be fully tagged for screen readers. Ask and we will provide an accessible version.
  • We have not yet completed a full audit with assistive technology across every page.

Tell us when we get it wrong

If any part of this site is difficult or impossible for you to use, email [email protected] with "Accessibility" in the subject line.

We respond within [5] business days. Tell us the page, what happened, and what you were using if you know. If something is blocking you from information you need right now, say so and we will send it to you in whatever format works while we fix the underlying problem.

You do not need to know the technical vocabulary. "The text is too small on my phone" is a useful report.

How we test

  • Automated scanning with [WAVE / Lighthouse / axe — name what you actually use]
  • Manual keyboard-only navigation
  • Contrast verified numerically at design time, not estimated by eye
  • [ADD screen reader testing once you have done it. Do not list it before then.]

Ongoing

Accessibility is not a project that finishes. New articles introduce new problems and we will not catch all of them. We review this page at least annually and after any significant redesign, and we update the gaps section honestly rather than quietly deleting things.

Last reviewed August 30, 2026.