A client emails back: "The voice thing isn't working for me." Nine times out of ten they are on Firefox. That is the one browser where the built-in speech recognition does not run, so the microphone button either does nothing or is missing. Everything else about the review works exactly the same. They can still capture the screen, add comments, drop pins, and publish a link you can act on.
You do not get to pick your client's browser. They open whatever is already on their machine, and a good chunk of the time that is Firefox. So it helps to know precisely what changes and, more usefully, what does not.
Can someone on Firefox still capture and publish a review?
Yes. The capture flow does not depend on the browser having speech recognition. Your reviewer clicks Capture screen, Firefox prompts them to share a window or the whole screen, and the current frame gets drawn to a canvas. They drag a rectangle to crop the still, or keep the full frame. Each screenshot becomes an item they can comment on.
When they hit Publish, the review saves and gets a short public URL like /r/your-slug. That link works the same whether it was made in Firefox, Chrome, or Edge. So does the PDF, the Word document, and the plain markdown at /r/your-slug/markdown. The only thing missing on Firefox is the option to talk instead of type. Nothing about the output is different.
This matters most for collecting client feedback, because the client chooses the browser and you find out about it only after they have started. The tool is built to handle that gracefully rather than block them.
Why doesn't dictation work in Firefox?
Dictation uses the browser's built-in Web Speech API. Chrome and Edge implement it, so the microphone button transcribes speech into the comment field there. Firefox does not implement it, so there is nothing to call. It is a gap in the browser, not a setting your reviewer can flip on.
There is no workaround inside Firefox to enable it, and no extension is involved anyway, since the whole point is that nothing installs. If your reviewer really wants to speak their notes, the only path is to open the review in Chrome or Edge instead. Most people would rather just type.
Is typing comments actually worse than dictating?
No, and in some cases it is better. Dictation is fast for people who think out loud, but typed comments tend to be tighter. When someone types "The Save button on the billing form does nothing on click," they have already edited out the ums and the restarts. The receiver gets a clean sentence.
If your reviewer is used to talking through problems and finds typing slower, point them to the habits in dictating review comments when your browser supports it for context on why speaking helps, then have them apply the same discipline by keyboard: one specific problem per comment, name the element, say what you expected. The structure that makes feedback fixable is the same either way.
Do pins and cropping still work?
Both work in Firefox with no difference. Your reviewer can drop numbered pins on a screenshot to point at the exact spot they mean, which removes the guesswork that vague comments create. "The third icon" becomes pin 2 sitting directly on that icon. If you want your client to use pins well, pinning the exact spot a reviewer means covers how they read on the receiving end.
Cropping is the same too. Drag a rectangle to keep just the relevant part of the still, or leave the full frame. Cropping is the only image edit in the tool, so there is no drawing of arrows or boxes to worry about being browser-specific. A Firefox reviewer and a Chrome reviewer produce identical-looking screenshots.
How do I set expectations before the client starts?
Send one line ahead of the link. Something like: "You can type your notes or, if you are in Chrome or Edge, click the mic to talk. Either way, hit Publish when you're done and send me the link back." That prevents the confused email about the mic button and lets the client on Firefox skip straight to typing without feeling like they broke something.
If your worry is the client stumbling over the tool at all, the better fix is a workflow that asks nothing of them. Read collecting client feedback without making the client learn a tool for how to keep the whole thing to capture, type, publish. No install and no signup means a Firefox user is not being asked to switch browsers just to leave a note.
Does the client need an account to publish from Firefox?
No. A review publishes with no account at all, in any supported browser. An anonymous review is kept for 30 days, and if the client later signs in with Google or a magic link, that review claims permanently. So a client on Firefox can capture, type, pin, publish, and send you the link without ever creating anything.
Once you have that link, you handle it however you work. Read the public page, export the PDF for a stakeholder, or pull the markdown version an agent can read if a developer or coding tool is doing the fixes. The browser your client used to make it never touches your side of the process.
Next time a client says the voice thing is broken, do not troubleshoot the microphone. Ask which browser they are in, and if it is Firefox, tell them to type. Start a review and hand them the link.