Accessibility

Accessibility Statement

Last updated: June 1, 2026

TaleTykes is built so more learners can read, write, and practice math comfortably — including users who rely on assistive technology or accessibility preferences.

We target WCAG 2.1 Level AA for core platform experiences and welcome feedback when something does not work for you.

01

Our Commitment

Optiarms, Inc. dba TaleTykes is committed to making TaleTykes accessible to learners, parents, teachers, and administrators with diverse abilities. We aim to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA for the core platform experience over time.

Accessibility is an ongoing effort. New features, AI-generated content, embedded partner apps, and third-party integrations may present uneven accessibility until reviewed and improved.

02

Built-In Accessibility Features

The platform includes user-controlled options designed to support comfortable use:

  • Reduced motion preference (tt-reduced-motion) to limit non-essential animation.
  • High contrast mode (tt-high-contrast) for improved visual contrast.
  • Font preference settings (tt-font) for readable typography choices.
  • Theme preferences (tt-theme) including light and dark modes where supported.
  • Keyboard-navigable authenticated surfaces and marketing pages in core flows.
  • Semantic page structure, labels, and alt text in platform-controlled UI components.
  • Read-aloud and literacy supports in reading features where enabled by parent or school controls.

03

Known Limitations

Some areas may not yet fully meet WCAG 2.1 AA across every route, role, and device:

  • AI-generated stories, illustrations, and writing feedback may not always include complete alternative text or predictable structure.
  • Embedded third-party learning apps under /child/apps may follow partner accessibility practices outside our direct control.
  • Complex data tables in teacher gradebooks, district reports, and admin dashboards may require additional keyboard and screen-reader refinement.
  • PDF or exported portfolio artifacts may inherit accessibility characteristics from export templates.
  • Live oral reading and fluency features depend on audio input quality and ASR accuracy.

04

Third-Party Content and Integrations

When schools or families enable embedded apps, roster integrations, or external LMS launches, accessibility of those experiences may be governed by the third party's own statements and support channels.

We review major platform surfaces and prioritize fixes that affect child learners and essential parent or teacher workflows.

05

Feedback and Accommodation Requests

If you encounter an accessibility barrier on TaleTykes, we want to hear from you so we can investigate and improve.

  • Email accessibility@taletykes.com with the page URL, your role, browser and assistive technology details, and a description of the barrier.
  • General support requests may also be sent to support@taletykes.com.
  • Schools with accessibility requirements under Section 504 or the ADA should coordinate with their administrators and our support team for reasonable accommodations during evaluation or deployment.

06

Testing and Improvement

We use a combination of automated checks, manual review, and user feedback to identify accessibility issues. Priority is given to barriers that prevent sign-in, learning activities, parent controls, and essential school administration tasks.

08

Contact

Accessibility feedback: accessibility@taletykes.com. Support: support@taletykes.com. Legal notices: legal@taletykes.com.