Accessibility

Accessibility statement

menti is built to WCAG 2.1 Level AA. This page says what that means in practice, what we know is imperfect, and how to ask for an accommodation.

Last reviewed: February 2026

Our commitment

Every page uses semantic HTML with one main landmark and headings in order.
Every control has a visible label or an accessible name, and a visible focus ring.
Body text meets a 4.5:1 contrast ratio, and error states never rely on color alone.
The whole product works from the keyboard, including the lesson player and the event check-in scanner.
Motion respects your reduced-motion setting.
Data-heavy screens show skeletons while loading and a plain explanation when there is nothing yet.

Manual keyboard passes on every flow that a participant, mentor or staff member uses.
Screen reader passes with VoiceOver on macOS and iOS, and NVDA on Windows.
Automated contrast and landmark checks on each release.

Uploaded PDFs come from applicants and may not be tagged for screen readers. Ask us and we will supply the content another way.
Video captions are required before a lesson can publish, but audio description is not yet available on every lesson.

Tell us what you need and we will arrange it. We aim to respond within one business day, and we will never ask you to explain a diagnosis.