Accessibility
A product about being heard should not itself exclude anyone. This page states what we do, what we are still improving, and how to tell us when something fails you. We hold to the plain-statement rule throughout: no claims of formal conformance we have not independently verified.
What we build to
We work toward WCAG 2.2 AA as our reference standard. In practice: text contrast reviewed against our dark interface, touch targets sized for real hands on real phones, a reading experience designed mobile-first, keyboard operability for core tasks, and plain English everywhere, because comprehension is an accessibility issue too.
Where we are honest about gaps
Some interactive views, particularly data visualisations, are harder to make fully equivalent for screen readers, and we are still improving them. Our priority order is deliberate: the consultation, your reading, the check-in and account controls come first, because those are the tasks that matter most.
Report a barrier
If something does not work for you, tell us at hello@meialab.com: the page or feature, your device and browser, and any assistive technology in use. Accessibility reports go into the same queue as functional bugs, not a slower one.