Readflexes is committed to making its learning tools and games usable by as many students and teachers as possible, including people with disabilities. We design with the Web Content Accessibility Guidelines (WCAG) 2.1 as our target and improve our accessibility over time.
Accessibility features in Readflexes today
- Read-aloud (text-to-speech). Words, prompts, and questions can be spoken aloud, supporting emerging readers and students who benefit from audio.
- Keyboard and touch input. Core activities can be operated with the keyboard (including arrow keys) or by touch, so students can use the input method that works best for them on Chromebooks, tablets, phones, and desktops.
- Cues that don't rely on color alone. Where the experience signals status (for example, "getting warmer/colder" indicators in games), we use symbols and text in addition to color so the information is available to colorblind users.
- Light and dark themes. Several areas of the Service offer light/dark display options for visual comfort.
- Responsive, device-friendly design. The Service is built to work across common school devices and screen sizes.
Current status and areas we are improving
Readflexes is an actively developed product with a wide range of activities, including interactive and game-based experiences. Some parts of the Service already align well with WCAG 2.1 AA guidance; other interactive components are still being reviewed and improved — for example, expanding screen-reader support and keyboard operability in certain games, and completing formal conformance testing. We treat accessibility as ongoing work and prioritize fixes that remove barriers for students.
Good-faith accessibility remediation roadmap
Because some parts of the Service are still being brought into full conformance, Readflexes maintains this good-faith remediation roadmap, consistent with Colorado HB 21-1110 and 8 CCR 1501-11. It identifies known gaps, our plan and target timelines to address them, who is responsible, and interim workarounds available in the meantime. We review and update this roadmap at least annually and provide an update report on request.
Known nonconformances (current)
- A formal Accessibility Conformance Report (VPAT 2.5) has not yet been completed across all modules.
- Some interactive and game-based components — including canvas/WebGL games — have limited screen-reader support and incomplete keyboard operability.
- Certain game interfaces may not yet meet all WCAG 2.1 AA contrast or visible-focus requirements.
Target remediation timelines
- Complete and publish a VPAT 2.5 / Accessibility Conformance Report covering the core (non-game) flows — on a good-faith target of within 12 months.
- Prioritize keyboard operability and visible focus indicators across core navigation and account/class flows first, then extend to interactive activities.
- Provide accessible alternatives or teacher-mediated paths for game-based activities that cannot yet be made fully conformant.
- Review and update this roadmap at least annually and provide an annual update report on request, in accordance with 8 CCR 1501-11.
Responsible role
David Green (owner / developer) is responsible for accessibility at Readflexes. Accessibility questions, status requests, and accommodation requests: readflexes@gmail.com.
Interim workarounds (available now)
- Read-aloud (text-to-speech) for words, prompts, and questions.
- Keyboard and touch input options across core activities.
- Status cues that use symbols and text, not color alone.
- Light and dark display options.
- On request, a demonstration or test account, and help identifying the activities that best fit a given student's needs.
Conformance reporting
On request, Readflexes will provide an up-to-date Accessibility Conformance Report using the current VPAT format, a description of the methods used to evaluate accessibility, and, where applicable, a remediation plan with timelines. Schools may also request a demonstration or test account to verify accessibility features.
Feedback
If you encounter an accessibility barrier in Readflexes, please tell us what happened, the page or activity involved, and the device and assistive technology you were using, so we can reproduce and address it. Contact:
Email: readflexes@gmail.com