Accessibility statement

Built for every child to read, and every grown-up to run.

We design and test to WCAG 2.2 AA on the website, the reader and the iPhone and iPad app. Where we fall short, this page says so.

In the reader

For dyslexic, low-vision and new readers

Fonts made for early readers
Reader text is set in Lexend or Andika, with the simple a and g that new readers find easier. You can switch a child to Atkinson Hyperlegible from Settings.
Big targets, big type
Pre-K and kindergarten pages use 32-pixel text, 64-pixel tap targets and one idea per page. Type and spacing follow the stage, never one fixed size.
Wider spacing
You can widen letter, word and line spacing for a child from Settings, and we remember it on every device they read on.
Read aloud and tap to hear
Any book can read itself out loud, lighting each word as it goes, and any word can be tapped to hear it sounded out, at every stage.
Keyboard and switch access
Every control in the reader and the grown-up pages works from a keyboard, with a focus ring you can see. Arrow keys and the space bar turn pages.
Reduced motion
If a device asks for reduced motion, page turns and celebrations happen instantly. Nothing in TaleTykes flashes.
Contrast and themes
Text meets 4.5:1 contrast on the grown-up pages and 7:1 in the reader. Light, dark and high-contrast themes follow your device setting.
Screen readers
Pages use landmarks, headings and labels. Pictures in books carry the description they were drawn from. The progress chart comes with a text summary.

How we test

By machine on every change, by hand before every release

An automated accessibility check (axe) runs on every page with every code change. A failing page blocks the release.
A keyboard-only pass of the sign-up, consent, reader and settings flows before each release.
A screen-reader pass with VoiceOver on Safari and iPad for the reader and the parent pages.
We check color contrast at the design-token level, so a color that fails contrast can’t be published.
The iPad app is tested with VoiceOver, Larger Text and Reduce Motion.

Known gaps

What’s still missing

Read-aloud audio is generated speech, not a human voice. It mispronounces some names and made-up words; tapping the word sounds it out correctly.
Books are illustrated by AI from a description. That description is the picture’s text alternative, so it says what we asked for, which can differ from what got drawn.
The printable version of a book is a PDF of the pages. It isn’t tagged for screen readers yet.
Read-it-to-us recording needs a microphone and speech. There’s no alternative for that feature yet, and progress works fully without it.
There’s no Android app yet. The website works in Android browsers.

Tell us

If something doesn’t work for you

Email accessibility@taletykes.com with the page or book, what you were using (browser, screen reader, device) and what happened. We reply within two business days, tell you what we will change, and when. Schools can request a Voluntary Product Accessibility Template (VPAT) from schools@taletykes.com.

This statement was last reviewed on November 2, 2026. Conformance claims cover the website at www.taletykes.com and the TaleTykes app for iPhone and iPad. See also the legal documents.