A layered checklist for the page that never shows a microphone icon.

When the Microphone Indicator never appears, the first question is whether the page ever asked for the microphone at all. Open the page, click into the field, and start the dictation control while watching the area near the address bar. If no icon, prompt, or banner appears, the page may not be requesting access, or a control may be hidden behind another element. Note whether the field responds in any way, such as a focus ring or a disabled button. Then test in a second tab. A missing indicator is a symptom, and the surrounding behavior tells you which layer to check first.
Distinguish a missing indicator from a hidden one. Some pages show the icon only while the microphone is active, and some show it only when the window has focus. Click directly into the field, wait two seconds, and look again. If the icon appears after the click, the page needed a user gesture before it could request access. If it never appears, the request may be blocked before it starts. Write down the action you took and whether the icon appeared. That sequence is the part most people forget when they describe the problem later to a colleague for help.
Check whether the page has a custom control that replaces the indicator. A voice feature built into a page may use its own icon inside the field, and the browser indicator may never show. Look for a microphone symbol in the editor toolbar, a menu item, or a keyboard hint. Read the page help if the control is not obvious. If the page has its own control, test it once and note whether it responds. A custom control that stays grey is a different fault from a page that never asks for access. They lead to different fixes, so record which one you see.
Write a short description of what you expected to see and what you actually saw. Include the page, the field, the control you pressed, and the moment the indicator should have appeared. Add a screenshot if you can take one. A precise description helps a colleague reproduce the condition and helps a support team decide whether the page or the browser is responsible. The goal of this stage is not a fix but a clean statement of the symptom, with enough detail that someone else can confirm it. Keep it to three lines so it is quick and easy to scan.
Grant permission at the prompt if one appears, and make sure the prompt is for the page you are using. A prompt can appear for an embedded frame from a different address, and accepting it may not help the visible field. Read the address shown in the prompt before you choose. Accept the request, then test the control again. If the indicator appears and the text arrives, the cause was a dismissed prompt. Write down the address you approved, because embedded frames are a common source of confusion. If no prompt appears, move to the site controls in the next step.
Open the site controls near the address bar and read the microphone entry. If it says block, the page cannot ask, and no prompt will ever appear. Set it to ask or allow, reload, and test again. If it says ask, the page may require a click before it requests access, so press the control rather than typing first. Note the state before and after. A blocked entry explains a missing indicator completely, and it is the first thing to check when a page that used to work suddenly goes silent. Record the exact label on the entry so the note is unambiguous.
Check the system permission list for the app or browser you are using. A blocked system entry prevents any page from showing a working indicator, even when the site setting says allow. Open the permission list, find the app, and confirm the switch. If it is off, turn it on and restart the app once. Then test the page again. Keep the sequence in your notes, because a system block and a site block look the same from inside the field but need different fixes. Name the list and the app in your note so a colleague can find the same switch and the state.
Test the prompt path with a page you know works. If the known page shows an indicator and the failing page does not, the difference is in the page or its permissions. If neither page shows an indicator, the browser or the system is blocking the request. This comparison prevents you from changing page settings when the cause is above them. Record both results with the page addresses and the time. A two-page comparison is quick, and it makes the next step obvious. Repeat it once after a full restart to confirm the result is stable. Keep both notes together in the same file.
Check the site and device defaults after permission is confirmed. Some browsers remember a choice per site and per profile, so a second profile can behave differently while the first works. Test the failing page in the profile you use daily, then in a fresh profile if one is available. Note whether the indicator appears in either. A difference between profiles points to a stored site choice rather than the microphone. Record the profile name so the result is reproducible on another machine. If both profiles fail, the cause is clearly shared and the device checks come next in the sequence.
Review the input device before you conclude the page is broken. A muted device, a disconnected headset, or a wrong default can stop the signal before any indicator appears. Open the sound settings, speak, and watch the level. If the level is flat, fix the device first. If the level moves, return to the page and test again. Write down the device and the level. The indicator depends on a working input, so a flat level makes every page look broken at once. A device that works in the sound panel but not in the page is a strong clue. Follow that clue before you change browser settings.
Check for a browser setting that blocks all microphone requests. Some setups disable the feature globally, and every site fails without a prompt. Look for the microphone section in the browser settings and read the default. If the default is set to block, change it to ask and test one page. Restart the browser if the change does not apply immediately. Record the default before and after. A global block is easy to miss because it produces no error inside the page. Write the setting name exactly as the browser shows it. Keep it in the same short shared note.
Check whether an extension is intercepting the request. A tool that manages prompts or blocks scripts can suppress the indicator and leave the page waiting. Disable extensions in groups, then test the page after each group. If the indicator returns, narrow the group until you find the responsible one. Note the extension name and the page result. This belongs in the checklist because it is a common cause of a missing prompt that no permission screen explains. Keep the useful extensions, remove the one that clearly conflicts, and test the same page once more after a full restart of the browser.
Confirm the working path with a system-level tool when the page indicator stays hidden. Voiskey is a voice typing app for macOS and Windows: press a shortcut, speak, and text appears at the insertion point in any app or text field. Open a plain document and dictate the same sentence. If the text appears, the microphone and the device settings are working, and the missing indicator belongs to the page. Keep the sample. That result is the evidence you need before you spend more time on site settings. Write it down beside the page result so the two are quick and easy to compare side by side.
Check the inserted text for the details that matter. Voiskey removes filler words, stutters, false starts, self-corrections, and grammar slips, and it adapts punctuation, formatting, tone, and vocabulary choice. Dictate a sentence with a name and an acronym, then read the result. If the names are correct, the app is learning your terms. Keep the sample with the page notes. A clean sample proves that the input path is healthy, which is exactly what a missing indicator makes hard to believe. Record both the text and the time in one line. Read it against the sentence you spoke before you save it.
Set up the tool before the next session. Download Voiskey from the official site, complete the setup, and confirm the shortcut starts a listening state. Because it works at the system level, it needs no indicator inside the page and no site prompt. Place the insertion point in the field you use and dictate one sentence. Note the shortcut and the microphone. Then repeat the test once to confirm the result is stable. A tested path is a reliable answer when a page stays silent. Keep the exact version number beside the note for later comparisons. Update it after each release.
Decide how to handle the page. If the page's own control works but the indicator is hidden, use the control and note that the indicator is cosmetic for that page. If the page never asks for access, use the system-level path and record the page as a known exception. If both paths fail, return to the device checks. State the decision in one sentence. A clear rule keeps you working while the page issue is reported, and it prevents the same investigation every morning. Review the rule after the page is updated, and retest the hidden indicator once more after the update and note whether it appears.
Keep the indicator working with a short monthly check. Open the page you use most, click into the field, and confirm that the indicator appears when you start dictation. If it does not, run the three checks in order: site permission, system permission, and device level. Write the date and the result beside the checklist. A monthly check catches changes after updates and profile switches, and it takes less time than a full investigation. The indicator is a useful early warning even when it is not required. Put the check on a shared calendar with a named owner and a fixed date.
Write the checklist with exact labels and exact steps. Include the site entry state, the system entry state, the input device, the level, and the browser profile. Add the date and the version. Keep it where the team stores operating notes. A colleague should be able to follow it without asking which panel you meant. If a step depends on a hidden icon or a custom control, describe where it sits on the page. A checklist that names locations is easier to follow than one that names concepts. Test it once by asking someone else to run it and report any gap.
Share the vocabulary that matters to the team. Add names, acronyms, and product terms to the app so they are recognized, and keep a written list beside the checklist. Voiskey learns names, jargon, acronyms, and spelling preferences, and the team plan offers shared vocabulary and workflows for groups using the same terms. Review the list when a new product name appears. A shared list reduces corrections and makes results easier to compare. Keep it short enough to scan during a call and update it at the start of each month. Remove any terms the team no longer uses. Keep it current.
Finish by making the reliable path the default while you watch the page. Download Voiskey for your desktop, set the shortcut, and dictate one real message each morning. Follow Speak, Polish, Type, Edit: speak the draft, let the app polish it, accept the text, then edit what needs judgment. Check the indicator once a week rather than every day. When the page is fixed, compare the two paths and keep the one that needs fewer steps. A routine built on evidence is easier to defend and easier to hand to a colleague who takes over the whole work. Then review it.
Voiskey works at the system level, so it does not need a page button or a site indicator to start. Press the shortcut, speak, and text appears at the insertion point in any app or text field. It removes filler words, stutters, false starts, self-corrections, and grammar slips and adapts punctuation and tone to the task.
Confirm that the system hears you by watching the input level in the sound settings, then test Voiskey in a plain field. Press the shortcut, speak, and text appears at the insertion point. If clean text arrives, the device path works and the missing page indicator is a site behavior, not an input failure.
Yes. Voiskey does not wait for a site prompt because it works at the system level. Place the insertion point in the field, press the shortcut, and speak; the text appears there. It supports 100+ languages and translation and removes filler words, stutters, false starts, self-corrections, and grammar slips. You can edit the result in the field.
Record the working field, the shortcut, the selected microphone, and the level you used, then test one sentence in a plain field. Voiskey learns names, jargon, acronyms, and spelling preferences, and the team plan offers shared vocabulary and workflows, so list the terms you add. Keep the note to one page and review it after updates.

Download Voiskey for Mac and Windows and type into any field without waiting for an icon.
Use it across macOS, Windows, iOS, and Android