If this site is hard to use, that is our bug.

What we have built in

• Semantic structure: real headings in order, landmarks, and lists, so screen reader navigation by heading or region works as expected.
• Keyboard access throughout: every interactive element is reachable and operable by keyboard, with a visible focus indicator, and a skip link to jump past navigation.
• Contrast: body and heading text is chosen to meet or exceed the WCAG 2.2 AA contrast requirement in both the light and dark presentations.
• Light and dark by preference: the site follows your system setting, and the theme button at the top of every page lets you override it — some eye conditions read light-on-dark far better, others the reverse. Your choice is remembered on this device only.
• Text that scales: sizes are relative, so browser and system text enlargement work without breaking the layout or clipping content.
• Reduced motion respected: if your system asks for reduced motion, animations and transitions are suppressed and content is shown immediately rather than revealed on scroll.
• Text alternatives: images that carry information have real descriptions, including the prototype render, and purely decorative graphics are marked so screen readers skip them.
• No traps: no autoplaying media, no pop-ups, no interstitials, no cookie banner, no advertising or cross-site tracking scripts.

What we have not done yet

We would rather be straight about this than claim a compliance level we have not earned.

• This site has not yet been through a formal independent accessibility audit.
• It has had an independent automated and AI-assisted code review, and the issues that review raised have been fixed — but that is not the same as testing with real users.
• It has been checked with keyboard navigation and automated tooling, but not yet tested end-to-end by a range of screen reader users across JAWS, NVDA and VoiceOver.
• We aim to meet WCAG 2.2 Level AA. We believe we are close; we have not had that independently verified.

These are on the list, and we will update this page when they are done.

Telling us about a problem

Use the details on our contact page. Email reaches the founder directly.

It helps if you can say what you were trying to do, what assistive technology and browser you were using, and what happened instead — but please do not let a lack of technical detail stop you writing. "The contact page is confusing with VoiceOver" is a completely useful report.

If you would prefer any content on this site in another format — plain text, large print, or read to you over the phone — ask, and we will arrange it. Phone and email are both on the contact page, and yes, a human answers.