Built for everyone

Accessibility

Last updated: August 15, 2026  ·  App: Maitora (iOS, iPadOS, watchOS, Android)

Developer: ARVEAM GLOBAL PRIVATE LIMITED  ·  Contact: hello@maitora.com

The short version. Maitora is built to be used with the accessibility features already on your device — VoiceOver or TalkBack, Voice Control, larger text, reduced motion and the rest. Every practice can be started, followed and finished using them.

This page says plainly what is supported, what isn't, and why. If something here doesn't match what you experience, that's a bug worth telling us about — hello@maitora.com.

What Maitora supports

Feature iPhone & iPad Apple Watch Android
Screen reader (VoiceOver / TalkBack)YesYesYes*
Voice Control (Voice Access)Yes—Untested
Larger TextYesYesYes
Dark InterfaceYesYesYes
Differentiate Without Colour AloneYesYesYes
Sufficient ContrastYesYesYes
Reduced Motion (Remove animations)YesYesYes
CaptionsYes—Yes
Audio DescriptionsNoNoNo

A dash means the feature does not apply on that device. Voice Control is not offered on watchOS. The watch app plays no audio or video content of its own, so Captions and Audio Descriptions don't apply there.

* What the asterisk means, and why it isn't a "Yes" like the others. Everything described below is implemented on Android and has been checked against the accessibility tree that TalkBack reads — labels, focus order, the breathing phase announced as it changes, the practice-rhythm map read as one sentence rather than 180 silent squares, session controls that never fade away while a screen reader is running. What has not happened yet is a hands-on pass with TalkBack switched on, on a real phone, because the automated harness we use cannot enable it.

One known gap that pass will address: a selected row — a soundscape, a bell, a saved voice — announces its tick as a separate item rather than as the row's selection state, so TalkBack reads "selected" as a thing on the row instead of saying the row is selected. It is understandable, but it isn't right, and it will be fixed rather than described away.

VoiceOver and TalkBack

Every screen, control and piece of information can be reached and used with a screen reader, including the parts that are normally only pictures. The breathing orb announces the phase and count you would otherwise be watching. The practice-rhythm heatmap reads as a single sentence rather than six months of silent squares. The week dots read day by day, so you know which days you practised rather than just how many. Each bar in the rhythm chart names its day, practice and minutes.

A running session keeps its Pause, Finish and Discard controls on screen for as long as a screen reader is running — they do not fade away, on either platform. Actions that are otherwise hidden behind a long press, such as unpinning a shortcut or deleting a journal entry, are available in the VoiceOver rotor and, on Android, from a context menu. Purely decorative things — background washes, the kaleidoscope, the typing indicator — are skipped.

Voice Control

Every control has a name you can say, and that name matches the words you can see on screen. Where a spoken label would be unreasonable — a whole affirmation, or a button that reads "Listening… tap to stop" — a short alternative is provided, so "Tap Stop dictation" works. Actions behind a long press or a swipe are also available from a context menu, because Voice Control cannot reach the VoiceOver rotor.

Android's Voice Access works from the same labels, and those labels are there — but we have not run a Voice Access pass ourselves, so the table above says "untested" rather than "yes".

Larger Text

Text scales with your system setting all the way through the largest accessibility sizes, on both platforms. Layouts adapt rather than shrink: the practices catalogue becomes a single column, segmented controls become menus, a settings row stacks its summary beneath its title, and a session's countdown grows together with the ring around it. Nothing that carries meaning is truncated or scaled down to fit.

One deliberate exception: the shareable "Year in practice" card and PDF report render at a fixed size, so a keepsake you send to someone else looks the same whatever your own text size is set to.

Dark Interface

Maitora is dark throughout, by design — it is used in the evening, in bed, and with the lights low. It stays dark regardless of your system appearance setting.

Differentiate Without Colour Alone

Nothing in the app is told apart by colour alone. A day you met your goal is a checkmark seal, not a warmer dot. The rhythm heatmap's squares grow with the amount you practised as well as deepening in colour. Stacked practices in a chart are separated by a visible gap. Selected states carry a checkmark, not just a tint.

Sufficient Contrast

Text and essential graphics meet the standard contrast minimums. The palette is checked by an automated test that computes the contrast ratios from the same colour values the app draws with, so it cannot quietly drift.

Reduced Motion

With Reduce Motion — or "Remove animations" on Android — switched on, the decorative animation stops: the kaleidoscope becomes a still piece of art, photo montages hold each photo steady while still cross-fading, drifting background glows hold their position, and screen transitions simplify.

The breathing orb is the exception, on purpose — its movement is the pacing you are following, so it keeps moving. On Apple Watch it uses a gentler swing, and the phase label says "Breathe in" or "Breathe out" in words either way.

Captions

Everything Maitora speaks is also written on screen at the same moment, on both platforms — guided meditations, sleep stories, affirmations, breath cues and the guided step of a routine. The narrator-voice preview quotes its sentence next to the play button. With a paired Apple Watch, spoken lines appear on the wrist too.

Audio Descriptions — not supported

Maitora ships no video content of its own. Your mind movie is built from photos and video that you import yourself, so there is nothing for us to describe. We would rather say this plainly than declare support we cannot honestly provide.

Known limits

Telling us about a problem

If something is unreachable, unreadable, unlabelled, or simply harder to use than it should be, please write to ARVEAM GLOBAL PRIVATE LIMITED — hello@maitora.com. Accessibility problems are treated as bugs, not as feature requests. Saying which assistive feature you were using and which screen you were on helps a great deal.