Accessibility

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across the Meloa web app and marketing site. We consider ourselves partially conformant: most of the product meets the standard, and the known gaps are listed below rather than omitted.

Accessibility is checked as part of our normal development work — colour contrast is measured against the AA thresholds for every theme and colour mode we ship, not only the default one.

• Text resizing that isn’t zoom. The text-size control in the header (the accessibility icon) scales type from 85% to 140% without reflowing layout spacing, so enlarging text doesn’t shrink the usable area of the screen.
• Light and dark mode, independent of the four colour themes, with contrast verified in every combination.
• Four colour themes, so colour can be chosen for comfort rather than being fixed.
• Colour is never the only signal. Event categories, anxiety levels and statuses carry text labels or icons alongside colour.
• Keyboard navigation and screen-reader labelling on interactive controls, with dialogs that trap focus and close on Escape.
• Touch targets sized for imprecise input on primary navigation and action controls.
• No punishment mechanics. There are no timed interactions you can fail, no streaks to lose, and no overdue-in-red — a design choice made for anxiety, which also removes the timing pressure WCAG’s Timing Adjustable criterion exists to address.

We would rather name these than let you discover them. We are working on each:

• Some drag interactions lack a keyboard path. Rescheduling an event by dragging it on the calendar currently has no equivalent keyboard gesture. You can always reschedule by opening the event and editing its time, which is fully keyboard-accessible.
• Charts are visual. Trend graphs and the Dread Gap chart convey their data graphically. The underlying numbers are available in text elsewhere in the app and in the data export, but the charts themselves are not yet fully described to screen readers.
• The Sanctuary and fidget tools are visual and motion-based by nature. They are optional and no part of the core loop depends on them.
• Guided audio sessions are not captioned yet.

Meloa uses animation for transitions and for the Sanctuary. If your device is set to reduce motion, we respect that setting. You can change it in your operating system’s accessibility settings, and it will apply to Meloa without any in-app configuration.

Meloa is a web app and works with the assistive technology built into your browser and operating system — screen readers, voice control, switch access, browser zoom and OS-level text scaling. It can also be installed to your home screen, where it behaves the same way.

If any part of Meloa is difficult or impossible for you to use, we want to hear about it — this is the most useful accessibility feedback we get, and we treat it as a bug, not a feature request.

Email support@meloa.io or use the support page. Please tell us the page, what you were trying to do, and the assistive technology or settings you use, if you’re comfortable sharing that. We aim to respond within five business days.

If we can’t resolve something quickly, we will tell you what the workaround is in the meantime rather than leaving you waiting on a fix.