Accessibility

The standard

Every page is built to meet WCAG 2.2 level AA. Body text meets level AAA for contrast — a ratio of at least 7:1 against the background, where AA asks for 4.5:1.

What that means in practice

• Every page has one h1, and heading levels never skip.
• Real landmarks on every page — a banner, a navigation region, one main region, and a footer — so you can jump between them rather than reading through.
• A skip link is the first thing you reach by keyboard on every page.
• Everything works by keyboard. Focus is always visible, with a two-tone ring designed to stay obvious against a dark background.
• Colour is never the only way something is communicated. The four section colours always appear alongside a text label.
• Nothing moves unless you allow it. If your system asks for reduced motion, every transition and animation is switched off entirely, not merely shortened.
• Text reflows to 200% zoom and down to a 360-pixel screen without horizontal scrolling.
• Links describe where they go. No bare "click here" or "read more".
• The page language is declared, and every page title is unique and descriptive.

How it's tested

Two automated suites run on every single change, before anything is published. A failure blocks the release — they do not produce warnings that can be ignored.

• axe-core and HTML CodeSniffer render every page and audit it against WCAG 2.2 AA.
• A structural checker covers what automated auditors miss: landmark counts, heading order, the position of the skip link, title uniqueness, the language attribute, and that no page requests anything from a third-party server.

Automated testing catches maybe a third of real accessibility problems, and no tool can tell you whether a page actually makes sense to listen to — so the last word is a human one. I've walked the whole site with NVDA, and had friends and my partner put it through its paces too. It came through with no navigation problems. The automated suites keep it that way on every change.

No tracking, no third parties

This site loads nothing from anyone else's server. Fonts are served from here rather than from a font network. There are no analytics, no trackers, no cookies, and no consent banner to dismiss, because there is nothing to consent to. Nothing you do here is tracked or logged — the only thing that ever leaves your browser is a comment or message you choose to send. There's more on how that is handled in the colophon.

It also runs no JavaScript. Not as a stunt — it just doesn't need any, and a page that needs none can't break in the ways that JavaScript breaks.

Where it falls short

The fiction pages are long. A chapter runs to several thousand words, and while the headings and navigation landmarks are correct, there is no in-page navigation within a chapter itself. If that makes reading harder than it should be, I want to hear about it.

Tell me when it's broken

If something here doesn't work with your screen reader, your magnifier, your keyboard, or your brain, that's a bug and I'd like to fix it.Send me a message about an accessibility problem. Tell me what you were trying to do and what happened instead — and what you're using, if you don't mind sharing.

You will not be the difficult one for asking. You'll be the reason it gets fixed.