Accessibility & Inclusion

Our commitment

Every young person deserves tools that respect how they navigate the world. We are committed to making Blue easier to use, easier to understand, and more equitable—in classrooms and at home. That means caring about inclusion and usability as much as we care about privacy and security, because students cannot thrive in a product they cannot reach.

Standards we work toward

We design and test with WCAG 2.1 Level AA in mind—the benchmark many school districts reference, including expectations common in Colorado and other states during vendor and data-privacy reviews. We aim to meet those guidelines across the product and to document our progress in good faith for your team.

We also take seriously how the Americans with Disabilities Act (ADA) applies to digital experiences for students and educators, and we work to remove barriers as we ship—not only at launch.

How we approach accessibility

Accessibility is part of how we design Blue, not a checklist we bolt on at the end. Our team considers structure, labels, contrast, keyboard use, and screen-reader experience alongside visual design and instructional flow—especially for workflows students and counselors rely on every week.

• Ongoing manual testing and iteration as features evolve
• Internal QA and developer tooling to catch issues early
• Attention to diverse learners—reading level, motor differences, sensory needs, and assistive technology where we can reasonably support them

Continuous improvement

Accessibility is never “finished.” Standards, browsers, and assistive tools change; so does Blue. We treat accessibility as an ongoing responsibility: improvements land regularly through product updates, and when we miss something, we want to hear about it quickly so we can fix it.

How this shows up on our roadmap

Meaningful accessibility work is prioritized alongside other product goals. We do not publish fixed completion dates—software moves too fast for guarantees like that—but teams across Blue treat barrier removal and inclusive design as part of normal planning, not a side project.

Feedback and support

If you run into something that blocks you or a student—an error with a screen reader, a confusing focus order, missing labels, or anything else—please tell us. Describe what you were trying to do, what happened, and the browser or assistive tech if you know it. We read every message and use them to prioritize fixes.

Email privacy@blueapp.ai. For district security, privacy, or procurement reviews, you can use the same address; mention accessibility in the subject line so we can route it quickly. We can also share VPAT or similar summaries when your process requires them—include your timeline and preferred format in your note.