Read the block, add one exception, and keep a second typing path ready.

When Your Antivirus Blocks the microphone, the first job is to read the message rather than to disable the tool. Most protection apps show a notification that names the program and the device it tried to use, and that name tells you which layer is being blocked. Open the notification or the app's recent events list and copy the exact wording. Write down the time, the program named, and whether the block was a prompt or a silent denial. A silent denial looks like a broken page, while a prompt waits for your answer. The difference decides the next step. Do not clear the notification before you copy it.
Check whether the block is aimed at the browser or at the page. A protection app usually sees a program, not a website, so its rule may cover every page in that browser rather than the one that failed. That is why a block can appear suddenly on a page that worked yesterday. Look for the program name in the event and compare it with the browser you were using. If they match, the rule is broader than the page. The repair belongs in the app's own list, not in the site settings. Write which one the event names. Copy it before you close the panel.
Look for the protection module that handles device access rather than the main real-time switch. Many apps group microphone and camera controls under a separate section, and that section is where an allow list lives. Read the current state before you change it, because the module may be set to ask, to block, or to allow for known programs. If it is set to block, the useful change is a single exception rather than a global off switch. Write the old state in your notes so you can restore it. The old state is your rollback. Note the module name exactly as shown.
Decide the scope of the change before you touch the app. A single exception for the browser is enough for a first test, and it is reversible. Turning off the whole module removes a layer you may need for other work and makes the result hard to interpret. If the exception does not restore voice input, put the module back as it was and move to the system check. The deliverable for this stage is a written rule: what was blocked, what exception you added, and when. One exception, one test. Keep the exception scoped to one program until a test proves a wider rule is needed.
Open the protection app's own allow list and add the browser as a program rather than the page as a website. Program-level entries are the ones these apps usually support, and a page-level entry may not exist. Use the exact program name from the notification, including any version folder if the list asks for a path. Save the entry, then close and reopen the browser so the rule is read again. A rule that is saved but not reloaded can look like a rule that failed. Reload before you retest. If the list allows a path, point it at the current program folder rather than an old shortcut.
Add only one entry at a time and test after each. If you add the browser, the page helper, and the headset utility together, you will not know which one mattered, and you will keep three exceptions you may not need. Test with the same page and the same sentence. If voice returns, stop adding entries. If it does not, add the next candidate and repeat. A short list of necessary exceptions is easier to review after an update than a long list nobody understands. Keep the list short. Delete any entry you added during an earlier attempt and cannot explain. That keeps the list honest.
Check whether the app has a notification setting that hides blocks. Some tools record a block without showing a message, so the user sees a silent failure and assumes the page is broken. Turn on notifications for blocked device access while you troubleshoot, then decide later whether to keep them. A visible block is easier to diagnose than a quiet one, and the notification usually names the program you need for the allow list. Write the setting change in the same note as the exception. Make the block visible. If notifications cannot be enabled, check the app's history view after each test.
Record the allow-list state as a small table: program, rule, date, reason, and result. Five columns are enough. The table is what lets a colleague repeat the fix and what lets you undo it after a trial. If the exception does not help, remove it rather than leaving it in place out of caution. Extra exceptions accumulate silently and make later troubleshooting harder, because every rule is a possible variable. Keep only the rules that produced a measured result. Remove what did not help. A row without a result is a guess, so leave it out until you have measured it.
Test the microphone at the system level before you return to the page. Open the system sound settings, select the input device, and watch the level meter while you speak. If the meter moves, the system can hear you and the block is above that layer. If it does not move, no page can succeed, and the device or its driver deserves attention first. This one check separates a device fault from a permission fault. It takes less time than resetting a site. Write the meter result. A moving meter is not proof the page will work, but a still one is proof it cannot.
Switch inputs deliberately and test each one. A headset, a built-in microphone, and a monitor microphone are different devices with different names, and a protection rule may treat one differently from another. Select each device in turn, speak the same sentence, and note whether the meter moves. If only one device is blocked, the exception should name that device or its program rather than the whole category. Write the device name exactly as the system shows it. Names must match exactly. If every device is silent, the driver is a better suspect than any page rule. Check it before the next test.
Check the app-level access list in the system settings as well as the protection app. The system keeps its own list of which programs may use the microphone, and a program that is missing from that list produces silence regardless of what the protection app allows. Add the browser if it is absent, then retest. If it is present and enabled, the protection app is the remaining suspect. Return to its allow list with a clearer question. Two lists, one question. If the program appears twice, remove the duplicate so the enabled entry is the one that runs. One entry per program.
Finish with a verdict and an order for the next attempt. The verdict says whether the system hears you, and the order says which list you will check first next time. If the system hears you and the page does not, the page or the protection rule is the fault. If the system does not hear you, no page setting matters yet. Write both lines, then move to the fallback while the repair continues. Verdict first, then fallback. If the system hears you and one page still fails, keep the page out of the typing path and use the desktop tool. That keeps work moving.
Voiskey is a voice typing app for desktop systems, and it works at the system level. You press a shortcut, speak, and text appears at the insertion point in any app or text field. That gives you a second path when a protection rule blocks a page's own control, because the page is not the thing being typed into. The rule may still affect the browser, but your writing does not have to wait for the rule to be resolved. One shortcut, one way in. The page may still show its own warning, and that warning is now about the page rather than about your text.
Use the second path to keep a comparison alive. Click into the same field, press the shortcut, and speak the sentence that failed. If text lands, the device and your delivery are fine and the fault is above them. If no text lands, the block may be aimed at the typing app itself, and the allow list needs an entry for it. Either result narrows the problem, which is more than a failed page test gives you. Every result narrows the field. If text lands but the sentence is wrong, the block is gone and the remaining issue is recognition. That is progress.
Let the tool clean the text while you work around the block. Voiskey removes filler words, stutters, false starts, self-corrections, and grammar slips, and it adapts punctuation, formatting, tone, and word choice to what you are doing. It also learns names, jargon, acronyms, and spelling preferences. That means the workaround does not lower the quality of the writing. It keeps the message at the standard you would have met without the block. The workaround should not read like one. It also adapts to what you are writing, so a formal message and a short reply both come out in the right register.
Set the second path up before the next block appears. Download Voiskey for the desktop, install it, sign in, and test the shortcut in the page field and in a plain notes field. If the protection app prompts you about the new program, note the prompt and the answer in the same table as the other rules. A prompt is information rather than a failure. Test once with the page open and once with it closed. Two conditions, one note. If the prompt offers a choice between allow once and allow always, start with once and change later. Always start narrow.
Review the rule after the next update to the protection app. Updates can reset an allow list, rename a module, or change a default from ask to block. Run one spoken test on the page that failed before, and compare it with the row in your table. If the block is back, reapply the same exception and add a new date. If the page works, mark the row as closed but keep it, because the same update pattern can return. Updates forget exceptions. Keep the closed rows so the next update has a baseline to compare against. History is the baseline.
Review the browser side at the same time. A browser update can change a program name or move an executable, and an allow-list entry that names the old path will stop matching. Check that the entry still points at the current program, and update it if the name changed. Write the new name beside the old one so the history is clear. A stale entry is worse than no entry, because it looks like a rule while doing nothing. Stale rules look healthy. If the name changed, test once after updating the entry rather than assuming the new name works.
Keep the note short enough to review in a minute. The note should list the blocked program, the exception, the date, the test result, and the fallback you used. Five lines. A longer note will not be read during an incident, and an unread note cannot prevent a repeat. Share it with the people who use the same desk or the same page. Give one person the job of reviewing it after major updates. A named reviewer keeps the note alive. If nobody reviews it, the note becomes a story about last year rather than a tool for next week. Review it or drop it.
Close with a plan that does not depend on the protection app behaving. If the page is blocked again, use the desktop tool for that field and reopen the allow list only when you have time to test properly. Write that plan in the note. Keep the tool installed, and download the current build when a machine is replaced so the fallback is ready before the next update. A plan that survives an update is worth more than an exception that does not. Plan beyond the exception. That way the next block costs a minute rather than an afternoon. Put the plan where the next person will see it.
Voiskey types through a system-level shortcut rather than through the page, so the page prompt is not part of its path. Click into the message field, press the shortcut, and speak. The text appears at the insertion point. That gives you a way to keep writing while the page control is repaired.
Test the same sentence in the same field. If Voiskey produces text while the page prompt fails, the fault is above the desktop path. If neither produces text, check the system input choice and the allow list before changing anything else.
It can carry the typing while the block is being resolved, because you press a shortcut and speak wherever the insertion point sits. It removes filler words, stutters, false starts, and self-corrections, so the text still reads cleanly. Keep the page repair separate and retest it after the rule changes.
Updates can restore a block or rename a program, and a record shows what you changed and what the result was. Write the program, the exception, the date, and one spoken test. A fallback covers the work, while the record makes the next repair faster.

Download Voiskey for Mac and Windows and keep dictating while a blocked page control is repaired.
Use it across macOS, Windows, iOS, and Android