Accessibility

Our goal

We are working toward the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. This is a continuing product goal, not a claim that every workflow already conforms.

Measures we take

• Use semantic headings, labels, landmarks, status messages, and visible keyboard focus.
• Support keyboard navigation and a skip link on every page.
• Respect reduced-motion preferences and maintain readable color contrast.
• Run automated accessibility checks across public, authentication, student, and educator workflows.
• Include accessibility review in changes to core product journeys.

Known limitations

Automated tests cannot find every barrier, and some third-party authentication interfaces are controlled by their providers. We are continuing manual keyboard, screen-reader, zoom, and mobile testing as the pilot evolves.

Get help or report a barrier

Email us with the page or feature involved, what you were trying to do, and—if you are comfortable sharing it—your browser, device, and assistive technology. We will acknowledge the report and work with you on an accessible alternative while we investigate.