Accessibility
Accessibility is part of the product, not an add-on.
We are working toward WCAG 2.2 AA as a design target—for the website and for the product. Known limitations are published here, and feedback is always welcome.
Our approach
What we build for.
A pediatric speech product has accessibility requirements beyond the ordinary: young users, varied abilities, low-sensory needs and caregivers in the loop.
Keyboard support
The website is built for keyboard navigation with visible focus. The product targets the same standard, with large touch targets for young children.
No autoplay audio
No sound plays automatically anywhere. Sound is always user-initiated and controllable.
Color and charts
Status is never communicated by color alone. Charts carry textual equivalents.
Captions and transcripts
Product videos ship with captions and transcripts.
Pediatric considerations
Low-sensory mode, reduced motion, predictable navigation, one primary task per screen, and caregiver controls.
Reduced motion
Animations respect the operating system's reduced-motion preference.
Screen readers & honest limits
Tested approaches, published limitations.
Screen reader approach
This website uses semantic landmarks, heading order and labeled controls, and we are testing it with mainstream screen readers as we iterate. Product screen-reader support is a design requirement and will be documented per feature.
Known limitations
A formal third-party WCAG audit has not yet been completed, so we do not claim full compliance. Known current limitations will be listed here as they are identified.
Last reviewed
October 2026. This page is updated as audits and fixes progress.
Feedback
Found a barrier? Email [email protected] and we will respond and fix what we can.
What we will never say
“Fully compliant” without an audit. Accessibility claims follow the same honesty rules as every other claim on this site.
Feedback channel
[email protected] — for website and product barriers alike.