Accessibility

Built-in accessibility features

• Audio-first design. Every instruction, letter and word can be spoken aloud and replayed — essential for pre-readers and helpful for children with visual or reading difficulties.
• Large touch targets. Buttons and tiles are sized for small, still-learning fingers (well above 44px), with generous spacing to prevent mis-taps.
• Keyboard support. Core navigation, tabs and dialogs work with keyboard focus; visible focus rings show where you are.
• Reduced motion. If your system requests reduced motion, decorative animations are automatically disabled.
• High-contrast, warm palette. Text-on-background combinations are chosen for comfortable reading; dark text on light cards throughout.
• Semantic HTML. Pages use real headings, lists, labels, landmarks and ARIA roles so screen readers can navigate sensibly.
• Alt text. Illustrations and decorative scenes carry descriptive alternative text.
• No color-only meaning. Color is paired with icons, text or position so color-blind children are never excluded.

Current limitations (honesty section)

We believe accessibility pages should admit what is not finished. Today: most game audio is speech-based and there is no closed-captioning of narration beyond the visible highlighted text (stories show the full text, which does serve as a transcript). Complex canvas activities (tracing, drawing) are inherently pointer-based. Some rapid celebratory animations remain on non-reduced-motion systems. Full WCAG 2.2 AA audits are part of our roadmap, not yet a completed claim.

Tips for making Fikrago Kids work better for your child

• Use a tablet with a stand for easier reaching and tracing.
• Increase your device's system text size — the layout adapts.
• Turn off background music in the Parent Dashboard if it distracts; keep the spoken voice on.
• Enable your operating system's reduced-motion setting for a calmer visual experience.

Feedback shapes this

Accessibility is a practice, not a checkbox. If something blocks your child from playing, tell us at hello@fikrago.com or via the contact page — accessibility reports are treated as high-priority bugs.