Accessibility

Everything here should work for everyone

• The standard. This site aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2, level AA.
• Reading. Text is dark enough to read on the cream background and on the tinted labels, at a contrast of at least 4.5 to 1.
• Keyboard. Every guide page can be used with the Tab key alone. The first stop is a link that skips straight to the content, and menus and panels that are closed are skipped. The scrolling boxes in the demos can be reached too.
• Video. The overview video has captions you can switch on and a written transcript under it.
• Motion. If your device is set to reduce motion, the scroll animations switch off and the content shows at once.

Checked by tool and by hand on October 14, 2026

• Automated scan. Every guide page, and the Codex entry screen, was scanned with the axe tool against the WCAG 2.2 level A and AA rules, after scrolling through every scene, at desktop and phone width. The onboarding demo was scanned at each of its steps, and the FAQ and Lexicon with every answer open. It reported no failures.
• Keyboard pass. A script pressed Tab through every guide page from the top. The first stop was the skip link, and no stop landed on a hidden control. The same script found no hidden stop on the Codex entry screen.
• Phone widths. Every guide page, and the Codex entry screen, was loaded at 390 and 320 pixels wide and does not scroll sideways.
• Captions. The captions were made by speech recognition running on a local computer, then corrected by hand against the narration.

What has not been checked yet

• No person using a screen reader has tested this site yet. Automated tools cannot catch everything, so some problems may remain.
• The Codex has no skip link yet. It is a separate app at /codex/ and it opens on its own Enter button. The entry screen passed the scan and the hidden-stop check, but the skip link is still to do.
• The Codex workspace view has not been scanned. After you press Enter, the floating Ask Aster label partly covers the Reset button and is too small to meet the target size rule. Both fixes are still to do.
• Editor mock-ups. The pictures of code editor windows on the teaching pages are illustrations. A screen reader reads their text, but they do not behave like a real editor.
• Browser video controls. The play, volume and caption buttons come from your own browser, so how they look and sound depends on it.

If something here does not work for you, say so

• How. Press the button below, or the Reach out button on any page, and tell Gabriel which page it was and what happened. A short note is enough.
• What happens next. Gabriel reads every note and aims to reply within 5 business days. If a fix is needed, the reply says when it will be done, or offers the same content another way.

Report a barrier

Last updated October 14, 2026. For how a note is stored, see the Privacy page.