Fix microphone and speech problems

Read the exact message

ADAR checks microphone access before starting recognition. No microphone was found means the device/browser has no usable audio input. Microphone access is blocked means site or device permission needs attention. Microphone is busy can mean another app is using it. A speech-service error can occur even when the microphone itself is allowed.

Allow the website microphone

1. Open the browser’s site controls beside the address.
2. Allow microphone access for the actual website you are visiting.
3. Check the operating system’s permission for the browser as well.
4. Connect or select a working microphone if needed.
5. Return to the page and press Speak again. A fresh page load may be necessary after a permission change.

Check microphone access

Expand Type / examples and choose Check microphone access. This checks access and releases the microphone afterward; it does not start a recording for ADAR. A browser running in a remote/cloud environment may have no microphone even when your own computer does.

Microphone works but speech fails

The browser’s recognition service may be unavailable, unsupported, blocked by a network policy, or unable to connect. Try a supported up-to-date browser with its speech features enabled. ADAR cannot override browser or operating-system permission decisions.

Keep working

Use the typed Ask / Apply box for the same supported requests. Audio Reader uses installed device voices and does not prove that microphone recognition is working. When reporting a problem, include the URL, device/browser, exact message, and whether typed requests work; do not send recordings or private information unless support has arranged an appropriate channel.

Continue learning

• Use Speak & Ask anything
• Listen with the audio reader
• Resolve a connection problem