Our commitment to accessibility

What are we doing to ensure a11y accessibility compliance?

At MagicSchool, we believe that our product should empower everyone - regardless of ability - to teach, learn, and create with confidence. We are committed to building inclusive, accessible experiences across our platform, and we view accessibility as an ongoing journey.

We align our work with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA ↗, which help ensure digital experiences are perceivable, operable, understandable, and robust for people with a wide range of abilities.

Our approach to a11y

Accessibility is woven into our product development process. We invest in dedicated team expertise, support cross functional learning through an internal Accessibility Guild, and build with a design system that includes accessible patterns by default. We also test key experiences using assistive technologies (such as screen readers like VoiceOver and keyboard-only navigation) and incorporate findings into ongoing improvements.

Our approach prioritizes sustainable, long-term practices, ensuring that accessibility is not a one-off fix, but a continuous part of how we design, build, and improve MagicSchool.

Across our platform, examples of accessibility features include:

• Keyboard navigation and visible focus states
• Screen reader compatibility for teacher and student workflows
• Clear announcements for key chat updates and status changes
• Color contrast, labeling, interaction patterns, and more!

VPAT® / Accessibility Conformance Report (ACR)

We provide an official Accessibility Conformance Report (ACR) prepared by our vendor accessiBe, using the Voluntary Product Accessibility Template (VPAT®). While organizations often refer to this document simply as a “VPAT,” the ACR represents the completed, product-specific version of the template.

Our ACR summarizes conformance with WCAG 2.2 Level A/AA, documents known limitations, outlines assistive technology compatibility, and includes required reporting for Section 508 and EN 301 549.

View our ACR/VPAT→

Known limitations

Accessibility conformance is an ongoing effort, some areas may not yet be fully accessible. For example:

• Certain third-party integrations or embedded tools may have accessibility limitations outside our direct control.
• Some legacy content or newer experiences may be in progress as we iterate and remediate issues.

If you encounter a barrier, we want to know, your feedback helps us prioritize fixes.

We welcome your feedback

Accessibility is a shared effort, and your feedback helps us improve. If you experience any barriers while using MagicSchool or have questions about accessibility, please contact us:

Email: [email protected]

We review all accessibility feedback and will respond within 10 business days.