Accessibility

Last updated: July 3, 2026

Prism is a learning tool, and learning should be open to everyone. We are committed to making Prism usable by as many people as possible, including people who rely on screen readers, keyboard navigation, magnification, reduced motion, or larger text. This statement describes where we are today, honestly, and how to reach us if something gets in your way.

Our target

We are working to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG 2.2 AA is the standard that underpins the U.S. Section 508, the European EN 301 549, and Ontario's AODA requirements, so meeting it is how we aim to satisfy those obligations for schools and organizations.

Conformance status

Prism is partially conformant with WCAG 2.2 Level AA. “Partially conformant” means that some parts of the experience do not yet fully meet the standard. We are actively closing the gaps below, and we publish a detailed, per-criterion Accessibility Conformance Report (ACR / VPAT) on request.

What we’ve done

Known limitations

We want to be candid about what is not done yet:

These items are on our roadmap, and an independent third-party audit is planned to validate our conformance.

Compatibility

Prism is designed to work with current versions of major browsers (Chrome, Edge, Safari, Firefox) and their built-in assistive technologies. If you use an older browser or a specific assistive technology and hit a problem, please tell us.

How we assess

We evaluate Prism using a combination of automated tooling (contrast checking and automated accessibility scans of our web build) and manual testing, including keyboard-only and screen-reader testing. We plan to complement this with a formal independent audit.

Feedback and contact

We welcome your feedback on the accessibility of Prism. If you encounter a barrier, or need information in a different format, please contact us and we will respond as quickly as we can, and work with you on a fix:

We aim to acknowledge accessibility reports within five business days and to give a remediation timeline for confirmed issues.