Accessibility
Our target is WCAG 2.2 Level AA. Here is what we have tested, what we have not, and how to tell us about a barrier.
Last updated
Draft pending review. This plain-language draft describes how the site is built to work today. It will be reviewed and finalized before the publication launches with real contributors.
Our target
We aim to meet WCAG 2.2 Level AA. We do not claim full conformance until the site has been evaluated by people using assistive technology.
How the site is built
- Semantic landmarks, one main heading per page, and a skip link as the first focusable element.
- Visible focus rings with at least 3:1 contrast on every interactive element.
- Touch targets of at least 44×44 pixels for primary controls.
- Visible labels on every form field; errors in text, linked to their fields.
- Story text left-aligned with a comfortable line length and spacing.
- Light and dark themes that follow your system, reduced motion when you ask for it, and support for forced-colors mode.
- No accessibility overlay widgets.
What has been tested
On 18 Sep 2026, in Chromium only: automated axe-core checks (WCAG 2.0 to 2.2 A/AA rules) on 20 pages in light and dark themes with no violations found; scripted keyboard checks of the skip link, menu, search dialog, tabs and the story form; and layout checks for horizontal overflow at widths from 280px to 1920px. Automated tools catch only part of what matters, so this is a starting point, not a conformance claim.
Known limitations
- Not yet tested with screen readers (VoiceOver, NVDA, TalkBack) or on physical iOS and Android devices.
- Not yet tested in Firefox or Safari engines.
- The scrolling prompt strip on the home page pauses on hover or focus and is static when reduced motion is on.
Report a barrier
Email [email protected] with the page and what happened. We aim to reply within five working days.