I'm building a Siri-first document workflow in Shortcuts for my completely blind aunt. We've encountered a reproducible Voice Control/Siri conflict that prevents her from using it independently.
Configuration
- iPad eighth generation, A2428, Wi-Fi + Cellular
- iPadOS 26.7.2
- VoiceOver enabled
- Original Orbit Reader 20 connected via Bluetooth
What we're trying to accomplish
Our working “Open Doc” shortcut asks for a document name, finds the existing note in her “Rici Documents” folder, and opens it using Open Note.
Opening the note doesn't activate its editing field. A custom Voice Control command running “Tap Note” → “Go to End” successfully prepares it for editing—but afterward, Siri no longer recognizes speech.
Simplest reproduction we've tested
- Start with Siri working normally.
- Open an existing note.
- Ask Siri to turn on Voice Control.
- Wait for Siri's interface to close.
- Say “Command mode.”
- Ask “Hey Siri, what time is it?”
Siri fails at step 6. This happens before “Tap Note,” cursor movement, or our custom command is executed.
Symptoms and other findings
- Holding Home opens Siri's interface, but spoken requests aren't recognized.
- Voice Control can recognize “Open Siri” and bring up Siri, but Siri still doesn't recognize subsequent speech.
- Spoken responses to shortcut prompts also fail.
- Turning Voice Control off afterward hasn't restored Siri.
- Turning Siri off/on doesn't help: it cannot hear the voice-training phrases during setup.
- Restarting with Voice Control off restores normal operation.
- Asking Siri to turn Voice Control on/off without issuing VC commands has worked without disrupting Siri.
- “Tap Note” alone has also reproduced the failure. The custom command isn't required.
I haven't established whether every VC command triggers this, or whether VoiceOver or the Bluetooth connection contributes.
Questions
Is this a known issue, and is there a way to recover Siri's speech input without restarting?
Alternatively, is there a supported way to open an existing Apple Note with its editing field active and insertion point at the end, without Voice Control?
I've already emailed Apple Accessibility. I'd appreciate guidance on collecting diagnostics and filing this under the correct Feedback Assistant category so the relevant team can investigate.
