Areas of alignment
- Use of semantic HTML where applicable
- Keyboard navigability across primary workflows
- Readable typography and contrast-conscious design
- Logical content structure and labeling
Trust Center
Accessibility Conformance Summary
Blue is committed to making its platform accessible and usable for all students and educators, including people with disabilities. Accessible design supports equitable student development. This page summarizes our current accessibility posture in a concise format for procurement, privacy, and partnership conversations.
Commitment to accessibility
We want students and educators to use Blue without unnecessary barriers. That includes people who rely on assistive technology, keyboard navigation, or clearer visual and structural design.
Accessibility is essential to equitable student development. It is part of how we design the product and how we plan improvements—not an afterthought reserved for a single release.
Accessibility standard
Blue aims to align with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Our goal is to support an accessible experience across core product functionality as the platform grows.
Scope
This summary applies to the Blue web application, including student and educator interfaces and core workflows such as:
- Story capture and reflection
- Content review and editing
- AI-supported summaries
- Navigation and account management
Current accessibility status
Blue is in an active accessibility improvement phase. We are honest about where the product stands today and where we are investing next.
Areas of ongoing improvement
- Enhanced screen reader support across all components
- Expanded keyboard interaction coverage
- Improved labeling and ARIA attributes in complex UI elements
- Accessibility validation across new feature releases
Testing and evaluation
We evaluate accessibility through internal QA testing, manual review of important workflows, and automated accessibility tools. As the platform changes, accessibility review is part of the development lifecycle—not only a point-in-time check.
Third-party components
Blue uses a limited set of third-party services—for example, infrastructure and communications capabilities that support reliable operation. We choose providers with strong security practices and weigh accessibility where we can.
Accessibility of embedded or vendor-hosted experiences may vary and is not always within Blue’s direct control. When gaps surface, we work with product plans and support channels to reduce impact for users.
Continuous improvement
Accessibility is an ongoing effort. We continue to evaluate and improve through product updates, interface refinements, and new features. Considerations for inclusion and usability are part of design and engineering workflows, not a one-time compliance exercise.
Feedback and support
If you encounter a barrier or have an accessibility concern, please contact us. Include what you were trying to do, what happened, and—if you know them—the browser and assistive technology involved. We make reasonable efforts to review reports and improve accessibility over time.
Limitations
While we strive to meet widely recognized accessibility standards, some parts of the platform may not yet fully meet WCAG 2.1 Level AA. We are actively working to identify and address gaps as the product matures.
For broader privacy, security, and student data practices, visit the Trust Center.