Accessibility

Built for every learner.

Accessibility isn’t a compliance checkbox for us — scaffolding every reader and writer is the product. This page describes what Elementari supports today, the standards we work toward, our honest limitations, and how to reach us when something’s in your way.

In the product

Read-aloud everywhere
Lesson readings and instructions can be read aloud, so decoding never blocks understanding.
Any language
Translation support lets ELL students access readings and express understanding in more than one way.
More than one way to express
Text, voice recording, images, music, and code — students show what they know in the medium that works for them.
Scaffolds built in
Sentence frames, word banks, glossaries, and step-by-step milestones reduce overwhelm — designed with partners like Tech Kids Unlimited.
Visual, not syntactic
Node-based coding removes the typing and syntax barriers that block many students in text-based languages.
Paper included
Every handout prints, so lessons work for classrooms and students who need or prefer unplugged work.

Standards we work toward

We design and build to WCAG 2.1 AA for the platform’s interfaces — color contrast, keyboard operability, visible focus, semantic structure, and reduced-motion support. Keyboard navigation, visible focus indicators, and contrast targets are in place today; screen-reader compatibility is on our roadmap and not yet independently verified.

We have not yet completed a full WCAG 2.1 AA conformance audit. We build toward these targets and are working toward documented conformance — accessibility documentation for procurement (VPAT / ACR) is in progress. If you need it for a purchasing review, email support@elementari.com and we'll share where we are and work with your timeline.

Because student projects are creative works, their internal accessibility depends partly on what students make; lessons encourage narration and readable text so published stories stay accessible.

Known limitations

We’d rather be honest about where we are than imply more than we’ve verified. Today:

  • Screen-reader compatibility across the Studio is a work in progress and has not yet been independently verified. If you rely on a screen reader, tell us your setup and we will prioritize testing against it.
  • We have not yet completed a full, documented WCAG 2.1 AA conformance audit of the platform. We design and build toward these targets and are working toward documented conformance.
  • Student projects are creative works — text sizing, color choices, and narration vary by what each student makes, so a published project’s internal accessibility depends partly on the author. Lessons encourage narration and readable text, but we do not fully control the finished work.

We publish updates here as they ship.

Tell us what’s in your way

If you or a student hits an accessibility barrier, we want to know — it gets triaged like a bug, not a suggestion. Write to support@elementari.com with the page or feature and the assistive technology you're using, and we'll get back to you. Every report helps us prioritize what to fix and verify next.

Questions about accessibility? We want to know.

Walk us through your setup and what’s in your way — we’ll tell you honestly where we are.