Accessibility

Last reviewed: 2026-07-25

What we aim for

The target is WCAG 2.2 Level AA. This page describes what has actually been verified, not what we hope is true, and it distinguishes the website from the application, which is not yet released.

The website — verified

These have been checked directly on this site:

Contrast. Every text and background pair used on the landing page and these content pages was measured. All meet the AA threshold of 4.5:1 for normal text, and most exceed 7:1. The lowest measured pair is 4.86:1.
Keyboard. Everything interactive is a native link, button, or input, so it is reachable and operable by keyboard in document order. A “Skip to content” link is the first focusable element on every page.
Focus. Focus is always visible: a 4px outline offset from the element, never removed.
Forms. The waitlist field has a real associated <label>, the correct type and autocomplete, and a status message region that announces success and errors to screen readers without moving focus.
Structure. Each page has one <h1>, headings descend in order, and content sits inside header / main / footer landmarks.
Motion. The two entrance animations and smooth scrolling are all disabled when your system asks for reduced motion. Nothing on the site flashes, auto-plays, or moves on a loop.
Zoom and reflow. Text is sized in relative units and the layout reflows to 320px without horizontal scrolling or loss of content.
Language. Each page declares its language, so a screen reader pronounces the English and Spanish versions correctly.

What has not been tested

Being straight about this, because an untested claim is worse than no claim:

No screen-reader pass has been run with JAWS, NVDA, VoiceOver, or TalkBack. The markup follows the right patterns and has not been verified by ear.
No independent audit has been carried out, so no formal conformance claim is made.
Voice control and switch access have not been tested.
The application has not been assessed at all. It is unreleased. When it ships, this page will be updated with what was actually tested on it, and the same honesty will apply.

Known limitations

The graduation dialog on the landing page is a picture of the app, not a working control. It is exposed to assistive technology as an image with a text alternative carrying its wording, and its buttons are deliberately not focusable, because they do nothing.
The handwritten typeface used for one or two lines per page is decorative and lower in legibility than the body text by design. Nothing is said only in that typeface; every handwritten line is a remark, never information you need.
The landing page is long, and its content is a single column with no in-page navigation beyond one skip link to the main section.

Report a barrier

Write to [email protected] and put “accessibility” in the subject. It goes to a person, and you will get a reply.

You do not need to explain your disability, name a diagnosis, or justify the request. What helps is anything you can easily say: the page, what you were trying to do, what happened, and the browser, operating system, or assistive technology involved. If any of that is a nuisance to collect, send what you have.

If something on this site is blocking you from joining the waitlist, say so and your address will be added by hand.