Accessibility is part of the product, not an add-on
ACCESSIBILITY

Different children should have more than one way in.

Kid Mission Lab is being built toward WCAG 2.2 AA practices where applicable, with additional attention to child-friendly readability and interaction.

Keyboard and focus

Interactive controls should be reachable without a mouse, with visible focus and logical tab order.

Touch targets

Core buttons and controls use large targets suitable for phones, tablets and younger users.

Reduced motion

KML respects the device’s reduced-motion preference and should not require animation to understand or complete a task.

Reading support

Child onboarding includes reading-comfort preferences. Younger-child experiences are designed for shorter instructions and minimal required typing. Read-aloud support is available where the mission experience provides it and remains an area for continued testing.

Color and meaning

Important instructions and status should not rely on color alone. Text labels, icons and state words are used together.

Responsive use

The core experience is designed for mobile, tablet and desktop. Accessibility is not considered verified until those journeys are tested on the deployed site.

Found a barrier?

Tell us what page, device and action caused trouble. In private beta, accessibility reports help determine what must be fixed before wider launch.

Report an accessibility problem →