Accessibility

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, landmark regions for the header, navigation, main, and footer, and one heading hierarchy per page, so a screen reader or a keyboard can move through a chapter the way a sighted reader scans it.
• Navigation, the mobile menu, and the theme toggle are labeled, keyboard operable, and show a visible focus ring. The toggle also reports which mode is active rather than leaving it to the icon.
• Every diagram in the course is exposed to screen readers as a single image with a written description of what it shows, so a reader who cannot see it still gets the point it makes.
• Links in the prose are underlined rather than distinguished by color alone, and body text, captions, and accents are held to the AA contrast ratios in both themes.
• The hero illustration and the mark stop moving when your system asks for reduced motion, and they settle into a finished, legible frame rather than freezing mid-animation. Nothing on the site plays sound.
• Your Build Plan and your course progress live in your own browser, so nothing here requires an account, a password, or a sign-in flow to get through.

Known limits

• We test by hand, with a keyboard and a screen reader, rather than running an automated checker on every release. Hand testing misses things, so a problem you hit that is not listed here is a gap in our testing, and we want to know about it.
• The course diagrams are described in one sentence each. That sentence carries the point the diagram makes, but not every label inside it, so a reader using a screen reader gets the argument rather than the full contents.
• The design lab and hero lab pages under /design-lab and /hero-lab-2 are internal working pages kept live for our own reference. They are not part of the course and are not held to this standard.

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 [email protected] and describe what happened and where. We read every report, and fixes for reported barriers go to the front of the queue.