Our approach
We aim to follow WCAG 2.2 AA principles and platform accessibility guidance. Accessibility is treated as an ongoing product requirement rather than a one-time checklist.
What the website supports
- Semantic headings, landmarks, labels, and keyboard-accessible controls.
- Visible focus states and sufficient touch targets.
- Responsive text and layouts across common screen sizes.
- Reduced-motion preferences and restrained animation.
- High-contrast typography and meaningful alternative text.
- Right-to-left layout support for Arabic.
- An installable experience with a basic offline fallback.
Language-learning accessibility
Audio should be paired with readable text and meaning. Important learning activities should not rely on color alone. Future speaking activities should explain microphone use and provide alternatives when speech input is unavailable.
Children and older family members
Controls should remain clear, consistent, and comfortably sized. Parent and educator views should explain insights in plain language. We avoid designs that depend on hidden gestures or unnecessarily fast interactions.
Known work
Before broad launch, the complete application should receive keyboard, screen-reader, dynamic type, contrast, captions, localization expansion, and device testing with people who use assistive technology.
Report a barrier
Use the Contact page and select “Technical support.” Include the page, device, browser, assistive technology, expected result, and what happened.