Accessibility

Draft for review, 17 October 2026. Source for what a statement contains: W3C WAI, w3.org/WAI/planning/statements (docs/w14_research/legal_and_accessibility.md, section 5e).

I want everyone who writes to be able to use this site, including people who use a screen reader, a keyboard, a magnifier or larger text.

The standard

This site is built to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. There is one version of the site, and it's the accessible one. There's no separate version to switch to and no accessibility widget. The site itself is built to work with the tools you already use.

What that means in practice

• Every page works with a keyboard alone, and you can always see where you are.
• The text follows the text size you set on your phone or in your browser, up to twice the normal size, without anything running off the screen.
• Text and background meet or beat the contrast WCAG asks for.
• Headings, lists and links are marked up so a screen reader can move through them.
• Buttons and links outside sentences are at least 44 pixels tall.
• If your device is set to dark mode or reduced motion, the site follows it.

What isn't perfect yet

• The sample notes PDF is a print-style document. It may not read as well with a screen reader as the pages do. If you need it in another form, write to me and I'll send the text.

If something doesn't work for you

Write to me at notes at thanksfortheread dot com and say what happened and on which page. I'll reply and fix what I can.

This statement was last reviewed on 17 October 2026. It was checked in Chrome, at desktop and phone widths, with the keyboard, at 200% text, in light and dark mode, and with the axe automated checker. It has not yet been tested with a screen reader or on an iPhone; that is next.