Learning experiences should reach every student — including those using a screen reader, a keyboard, captions, or a translated page. Accessibility isn't a setting in SimChoices; it's built into the way you author.
Validation won't let you publish an image without a text description. Every visual has a spoken equivalent for screen-reader users.
Narration and ambient sound carry a text transcript, so an experience never depends on a student being able to hear it.
Every choice, activity and control is reachable and operable without a mouse — with a visible focus ring that meets contrast guidance.
Themes ship with text and interface contrast that meets WCAG 2.1 AA, and the player respects the reader's reduced-motion preference.
Text is real, selectable content — not baked into images — so browser translation and language tools work straight out of the box.
Timed challenges are optional and extendable, so a countdown is never the thing that stops a student from finishing.
We design and test the player against Web Content Accessibility Guidelines 2.1, level AA.
Accessibility is never "done" — it's something we keep working at. We test with keyboard-only navigation and popular screen readers, we build new features to meet AA from the start, and we treat an accessibility bug as seriously as any other.
If something in SimChoices — or in an experience you're playing — gets in your way, please tell us. We aim to respond to accessibility reports within two business days and to fix confirmed issues as a priority.