Accessibility
Accessibility statement
This site aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, for everyone who reads it, however they read it.
How it is checked
These checks run against the built site before every release, and a release waits until they pass:
- An automated scan (axe-core, WCAG 2.2 A and AA rules) of every page, and of the interactive states: open menus, dialogs, tabs and demos.
- The contrast of every text color against every background it sits on, in both light and dark mode.
- Touch and click targets of at least 24 by 24 pixels.
- Reflow: every page at 320 pixels wide (the same as 400% zoom on a desktop), with no sideways scrolling, including with increased letter, word and line spacing.
- Keyboard use: every control can be reached and used without a mouse; dialogs keep focus inside and return it when they close.
- Reduced motion: when your system asks for it, animations stop and the film waits for you to press Play.
- Without JavaScript, every page still renders and every link and panel still works.
What is known to fall short
- The commit heatmap on the logbook page is wide. On narrow screens it scrolls sideways inside its own box, and a table of monthly totals gives the same information.
- Screenshots are pictures of a real application. Each has a text description, and the numbered notes on them are repeated in text beside the image, but the small text inside a screenshot can't be enlarged on its own.
- The film has no sound. A text description of what it shows is provided with it.
- A full manual pass with screen readers (NVDA and VoiceOver) has not been done yet. It is planned.
Report a problem
If anything on this site is hard to use, I'd like to know. Email me about accessibility, and say which page and what went wrong.
Last reviewed .