[lana-20]

docs/ACCESSIBILITY.md is the plan for what Mobium can do with the tools disabled people use: screen readers, speech that drives the screen, and voice assistants. For each, it records what was measured, what it found, and the build order. Every step names the control that shows it can fail.

Framing

It's organized by what a person can't do, using EN 301 549's functional performance statements (clause 4.2). Each kind of tool is held to the WCAG 2.2 success criteria it depends on.

Voice assistants (Siri, Gemini, Alexa) count as assistive technology when the test is a task: ask for an outcome, read the app to confirm it happened, and check the reply says what was done. Two limits are stated with it:

• Mobium sends typed text, not speech, so it tests the assistant's understanding and the app's response, not speech recognition.
• No task may need speech (4.2.6).

Measured, and where it stands

• VoiceOver on iOS 27, on the iPhone and a simulator: it can be turned on, walked and heard, once the runner is built by Xcode 27. With it on, a tap used to move the cursor and report done. That's step 1, built in With VoiceOver on, a tap is a touch and a double tap, and other touches are refused naming VoiceOver (CHALLENGES 348) #243 (CHALLENGES 348).
• TalkBack: every step-1 path lands with it on, on the emulator and the Pixel.
• Apple's audit: already a tool (mobium audit: Apple's own accessibility audit of the screen, on a simulator and an iPhone #80). Step 3 is now Android's audit.
• Siri: measured, not built.
• Gemini, Alexa, Voice Control and Voice Access: not measured.

The plan

1. A tap with VoiceOver on lands, or is refused (With VoiceOver on, a tap is a touch and a double tap, and other touches are refused naming VoiceOver (CHALLENGES 348) #243).
2. app_speech: what the screen reader says.
3. The platform's audit on Android.
4. Label in Name, checked from map.
5. A screen reader as a setting.
6. app_assistant: Siri, Gemini, Alexa.
7. Voice Control and Voice Access.

Docs only. make docs-check passes.