Trust layer
Accessibility
Last updated: August 8, 2026.
The standard we aim for
We hold this site to WCAG 2.2 AA, the web accessibility standard and the same bar our own course tells builders to meet, in both the light and dark themes. We do not claim perfect conformance; we claim a standard, a habit of testing against it, and a working way to reach us when something fails you.
What is in place
- A skip link to the main content, proper landmarks, and one heading hierarchy per page, so screen readers and keyboards can move through the site the way sighted readers scan it.
- Navigation, menus, and the theme toggle are labeled, keyboard operable, and show a visible focus ring; nothing on the site traps focus or blocks zoom.
- Every diagram carries a written title and description for screen readers, and every content image requires alt text before it can render.
- Links are underlined rather than distinguished by color alone, and body text is held to the AA contrast ratios in both themes.
- The short films on the course landing and level pages are silent, carry pause and skip controls, start paused when your system asks for reduced motion, and each one links to the written part of the course that tells its full story. Nothing on the site plays sound on its own.
Known limits
- Some sections fade in as you scroll, which needs JavaScript. With JavaScript off, those sections do not appear; with it on, they are fully available to assistive technology.
- We test by hand, with a keyboard and a screen reader, rather than with an automated checker on every release. Hand testing misses things, so if you hit a problem we did not list here, that is a gap in our testing and we want to know about it.
Tell us what is broken
If any part of this site is hard to use with a screen reader, a keyboard, a switch device, or anything else, email ainativeproducts@gmail.com and describe what happened and where. We read every report, and fixes for reported barriers go to the front of the queue.
The law of what you sell in the Builder's Stack teaches why an accessibility statement with a monitored contact belongs beside every privacy page. This page is ours.