Accessibility
We aim for WCAG 2.2 level AA. This page says what that means in practice, what we have actually tested, and what is not done yet.
What is built in
- Semantic HTML with one main heading per page, landmarks, and a “Skip to content” link.
- Everything works with a keyboard alone, with a visible focus ring: deep teal on light pages, bright gold on dark bands.
- Text and background colors are chosen to meet AA contrast; body text is 17px or larger and reflows down to 320px wide without sideways scrolling.
- Every picture has a written description. Decorative graphics are hidden from screen readers.
- Nothing moves on its own, nothing autoplays, nothing flashes. The one animation, the pronunciation highlight, is replaced by a static highlight when your system asks for reduced motion.
- Large tap targets (at least 44 pixels) on every link and button.
- Pronunciation is shown as text and as a highlighted sequence, not only as audio. There is no audio yet.
What we have tested
Automated checks run on every build: heading order, alternative text, link validity, color contrast of the design tokens, and the security and privacy headers. We have done manual keyboard navigation in a Chromium-based browser at 320, 375, 768, 1024 and 1440 pixel widths. We have not yet done a full screen-reader pass with NVDA, JAWS or VoiceOver, and we will update this page when we have.
Known gaps
- No audio pronunciation yet. It is planned, with approved recordings, and will never need a microphone.
- No transcripts or captions yet, because there is no video on the site yet. Every future video page will have both.
Tell us
If something does not work for you, we want to know. Use the contact page. Say which page, what you were trying to do, and what happened; we will fix what we can and say so here.