Navigation and reading
The public site uses semantic headings, page landmarks, readable text, labelled controls and a skip-to-content link. Shared public navigation and the mobile menu are intended to work with a keyboard, visible focus, Escape and focus return.
Content is available as readable HTML rather than only as text inside an illustration. Informative images have descriptions; purely decorative art should not distract assistive technology. Public pages do not require a permanently running 3D scene.
Motion is optional
The site respects the device’s reduced-motion setting and offers a decorative-motion choice. Mobile storytelling uses ordinary scrolling instead of forced desktop pinning. Meaningful text and mathematical facts remain available without animation.
Decorative movement is not a requirement to use the learning controls. No sound or microphone starts because a visitor scrolls. If an animation or layout makes a page hard to use, report the barrier and describe the page and action rather than sending sensitive student content.
Mathematics you can control
Public demonstrations use labelled inputs, computed numerical outputs and readable mathematical relationships. Sliders support keyboard changes and the essential explanation is not supplied by colour alone. A deterministic preview is labelled as such instead of pretending to be a live AI conversation.
In Study Lab, the board and text provide an alternative when optional audio is unavailable. Where narration is authorised, captions and playback controls are provided in the existing player. Voice is optional and its production/device testing is not complete.
Forms and error messages
Contact categories, labels, bounded text fields and status messages help explain what to provide and whether a request was stored. The form accepts no attachments and should not be used to send private documents or recordings.
If support storage/review operations are not configured, the site reports unavailability instead of showing a false success. An accessibility report does not require disclosing a diagnosis. Please describe the practical barrier, browser or assistive technology if useful, and the outcome you need.
Known limitations and verification
Automated checks can identify some contrast, structure and label problems, but cannot prove complete accessibility. The technical audit tested selected routes, reduced motion and keyboard interactions; full manual screen-reader, speech-input, zoom, device and live-voice checks remain necessary.
Some authenticated mathematical visuals and 3D teacher behaviour may need additional alternatives for particular assistive technology. Actual low-end-device performance and complete WCAG 2.2 AA conformance have not been established. Current public-release test results and unresolved barriers must be reviewed before a conformance claim is made.
Tell us about a barrier
Use the Accessibility category on Contact when the secure support queue is operational. A stored receipt means the request was received by the application, not that it has been assessed or resolved. Staff review and a verified operational contact are release requirements.
You may ask for help accessing information in another format. The operator should work with you on a reasonable, appropriate alternative rather than assuming one interface works for everyone.
A question or a concern?
Ask about this information, request support, or report something that needs attention.
Contact Zuvopa →