A short microphone check before a long screen recording
Choose the input you intend
A connected headset does not prove the browser is recording its microphone. Check the selected input where the app or operating system exposes it. If microphones have similar names, make a short test rather than guessing. Use harmless material during the check.
Review site and system permissions
Chrome allows or blocks microphone access per site, and computer settings may also restrict it. Work or school devices may have administrator-controlled settings. Check the intended site permission, not an unrelated page. Do not disable wider security settings just to make recording work.
Record speech and a pause
Say a sentence from the distance you will use, pause, then speak again. Include one screen action to judge timing. Stop and save using the supported app controls. A moving sound meter is encouraging, but listening to the saved file is the decisive check.
Listen before the full session
Open the saved sample at a sensible volume. Check that speech is present, clear and not overwhelmed by background noise. A headset mute switch or low system input level can matter. Change one setting at a time and repeat the short test instead of recording another full session.
Separate microphone and system audio
Screen capture does not prove every application sound is included. Audio sources depend on the browser, device and capture surface. Check the actual Solivid controls and saved sample, not an assumed universal mix. This checklist does not promise system-audio support on every device. Chrome guidance: https://support.google.com/chrome/answer/2693767