Belonging includes access.

This site exists for people who've been told — directly or by a hundred small frictions — that AI isn't for them. It would be a strange thing to build that site and then put barriers at the door. So accessibility here isn't a compliance page. It's the brand promise, applied to the building itself.

What we hold ourselves to

We target WCAG 2.2 AA. In practice that means readable contrast, keyboard navigation, useful labels and status messages, zoom and reflow support, and respect for your motion preferences. Automated checks help, but we do not treat them as a substitute for manual review.

What we've done so far

• ✓Default body and course reading text is 16px or larger; supporting labels are no smaller than 14px
• ✓Contrast checked on every navy section; low-opacity light text removed site-wide
• ✓Visible keyboard focus on every link, button, and form field
• ✓The flying butterflies honor prefers-reduced-motion — they perch quietly instead
• ✓Touch targets on interactive elements sized for real thumbs
• ✓Course progress saves automatically — losing your place is an accessibility issue too
• ✓Every downloadable worksheet is also available as an HTML page
• ✓PDF accessibility is reported only after tags, headings, reading order, fields, and visual output are manually verified

Downloadable files

A PDF is not accessible just because its text can be read or its fields can be filled. Until a file has passed structural, keyboard, screen-reader, and page-by-page visual checks, we call its accessibility status unknown. We provide both HTML and PDF formats so readers can choose what works for them.

When we miss

We will, somewhere — and we'd rather hear it than not. If anything on this site is hard to read, hard to reach, or hard to use with your setup, tell us through the contact form. Accessibility reports go to the top of the fix list — ahead of new features, every time.