1. Start with one known-good field
Open a new TextEdit document, click in the document until the insertion point is visible, trigger your configured Dictation shortcut, and speak one short sentence. This separates the Mac’s basic Dictation path from a browser, terminal, rich editor, or app-specific voice feature.
If the sentence appears in TextEdit, the system recognized your shortcut, selected a working microphone, and produced text. Continue with the target-app checks below. If nothing appears, stay with the system checks.
- Use a quiet room and one short sentence.
- Watch for the highlighted or pulsing cursor Apple describes.
- Record whether nothing happened, listening began without text, or text appeared incorrectly.
2. If the shortcut does nothing
Open System Settings → Keyboard, make sure Dictation is on, confirm the selected language, and read the current Shortcut value instead of assuming Fn or Globe still has its default action. Apple lets you select a listed shortcut or create a custom combination.
If your keyboard has a Microphone key, Apple distinguishes a press and release—which starts Dictation—from holding the key, which can activate Siri. Apple also states that standard macOS Dictation is unavailable while Voice Control is on; in that mode, Voice Control handles text entry.
- Confirm Dictation is enabled.
- Use the exact shortcut shown in Keyboard → Dictation.
- Check Accessibility → Voice Control before treating the shortcut as broken.
3. If listening starts but no useful text appears
In Keyboard → Dictation, select the intended Microphone source. If the Mac does not respond to your voice, Apple recommends checking Sound → Input and increasing the selected microphone’s input volume.
Confirm the correct language and region, remove physical obstructions from the microphone, and reduce background noise or echo. Apple suggests a headset microphone when the room is noisy.
- Verify that the input meter responds in Sound settings.
- Match the Dictation language to the language you are speaking.
- Test the built-in microphone separately from an external or Bluetooth device.
4. If TextEdit works but Google Docs, Chrome, or Terminal does not
A successful TextEdit test shows that the basic system Dictation path works; it does not prove every custom editor exposes the same text-entry surface. Click directly into the failing field, confirm a visible insertion point, and compare it with a simple text field in the same app or browser.
If macOS Dictation works in a plain field but not in Google Docs, Chrome, Terminal, or another rich or custom surface, document the exact field and app version. Also check whether that app has its own dictation feature or shortcut that you are triggering instead of macOS Dictation.
Do not repeatedly change microphone or language settings after the TextEdit control succeeds. The useful next step is isolating the target surface, not restarting the entire diagnosis.
5. If the failure changes with the network or a pause
Apple says the processing and network requirement can vary by language and configuration. Read the text beneath Keyboard → Dictation on the Mac you are testing; it states whether general Dictation voice inputs and transcripts are processed on-device for that setup.
Apple also documents that Dictation stops automatically after 30 seconds with no detected speech. A session ending after a long pause is therefore different from the shortcut never starting.
6. Decide whether you need a fix or a different workflow
If Apple Dictation is broken in TextEdit, finish the system diagnosis before buying another app. A replacement cannot repair a disconnected microphone or an operating-system setting.
If Dictation works but you want a held-key habit, local speech recognition, supported on-device formatting, or a structured Markdown brief, IraVoice 0.7.1 is a different workflow for macOS 26+ on Apple-silicon Macs. Its model downloads and Gumroad license verification remain disclosed.