Accessibility

Last updated: 2026-08-23

We want this site to be usable by as many people as possible. This page says what we have done, what we know is wrong, and how to tell us about the rest.

What is in place

• Skip to content. The first thing a keyboard or screen reader

encounters is a link that jumps past the navigation.

• Visible focus. Every interactive element shows where the keyboard

is. We do not remove focus outlines.

• Reduced motion. If your system asks for less animation, the site

honours that setting and stops animating.

• Alternative text. Images carry a text alternative describing what

they show.

• Structure. Pages use real headings in order, real lists and real

buttons, so that assistive software can navigate them.

• No timed content. Quizzes have no countdown and no time limit.

What we know is wrong

The site requires JavaScript. With scripts disabled, pages do not render. This is a known defect and it is recorded as such in our own development notes — not an intentional requirement, and not something we are content with.

We are being explicit about it because a page that quietly shows nothing is worse than a page that says why.

Standard we aim for

[DECISION REQUIRED — name the standard and level you are committing to, commonly WCAG 2.2 Level AA, and say whether the claim is "conformant", "partially conformant" or "aiming for". A claim of conformance that has not been audited is worse than no claim: it is checkable, and it will be checked.]

Telling us about a problem

If something on this site is difficult or impossible for you to use, please tell us on the Contact page. Describe what you were trying to do and what happened; you do not need to know why it failed or use any particular terminology.

We treat accessibility reports as defects, not suggestions.