Choose the test that matches your device or symptom. If others can’t hear you, start with the mic; if you can’t hear them, check your headphones or speakers. Use the webcam test for your picture, or the keyboard, mouse, and dead pixel tests for input and screen checks. Record your first result, change one condition, and repeat the same task to document what changed.
Which device do you want to check?
Keyboard test — Press and release individual keys, then try a combination that gives you trouble. Compare your physical presses with the events shown. For unexpected extra input, start with separate short taps before trying a held key.
Mouse test — Check buttons and the scroll wheel inside the test area. For suspected double-clicking, make deliberate single presses and compare them with the completed-press entries and click intervals. Repeat an unexpected result before drawing a conclusion.
Dead pixel test — Inspect the same screen area against black, white, red, green, and blue backgrounds. Note any suspicious point’s location and appearance on each color. Use full screen when available; inspect the display yourself and account for any area covered by controls.
Webcam test — Start a preview and check that you see the intended camera view. Look at framing, lighting, and movement. If you selected the wrong camera, choose another available input and check again.
Headphone and speaker test — Select your intended output in your system’s sound settings and start at low volume. Play the left and right channels separately, then both together. Record where you actually hear sound and whether either side is missing.
Microphone test — Start the mic, speak normally, and watch for input activity. Use short recording and playback when available to hear whether your words are audible and clear to you. If the result is unexpected, check the selected input and the mic’s mute control, then repeat.
Check your setup before a call
Yes. Check mic input, headphone or speaker output, and webcam preview separately, using the equipment you plan to use for the call.
Say a short sentence into the mic and observe the input response. If recording is available, play it back and listen for missing words or an unexpectedly quiet voice. Next, check the output channels at low volume. Finally, start the webcam preview, move naturally, and check your framing and lighting. Stop each test when you finish.
Browser access to camera and microphone inputs requires your permission. Allow access when prompted if you want to run that media test. If the page is waiting, look for an unanswered browser prompt before changing settings. [MediaDevices: getUserMedia() method - Web APIs | MDN]
Finish in your meeting app’s own setup screen. Select the intended mic, speakers, and camera there, then use its test-call option if available. Record the browser result specifically—for example, “Mic activity appeared while I spoke, and the webcam preview showed my picture”—then check the call itself.
What the results can tell you
An online keyboard test can show whether the browser receives a key event, but it cannot identify every hardware or software fault by itself. Browser and operating-system shortcuts can reserve some keys. For a missing response, release all keys, refocus the test area, and try again; then compare the key’s behavior in another application. [Keyboard Test – Free Online Keyboard Tester] [Keyboard Test – Free Online Keyboard Tester]
A browser mouse test observes the events the page receives; it cannot inspect the physical switch or rule out every driver and operating-system factor. Describe a repeatable observation, such as “five deliberate presses produced six completed-press entries,” and check whether the pattern recurs. [双击测试 - 在线测试鼠标按钮 - Test My Mouse]
Separate page status from what you see or hear. For audio output, note the target channel and where you heard it. For the screen, note the background color and the point’s location. For the webcam, describe the preview’s appearance and movement. Use those observations to choose the next check without treating them as a complete hardware diagnosis.
A camera or mic access failure can reflect a permission restriction or the absence of a matching input device. Follow the displayed status: review permissions for a denied request, check connections and input selection for a missing device, or retry a failed start after closing other media apps. Keep the access status in your notes. [MediaDevices: getUserMedia() method - Web APIs | MDN]
Compare a first run with a retest
Start with a small, repeatable task: tap one key five times, make ten deliberate mouse presses, inspect the same point on all five colors, say the same sentence, or play the same channel sequence. Perform the task, add what you saw or heard, and save your first run as a baseline.
Change one condition and describe it precisely, such as “moved the receiver to another USB port” or “selected the headset mic instead of the laptop mic.” Reset the current observations, repeat the task, and save a retest. Keep your pace, speaking distance, listening volume, and other relevant conditions as consistent as practical.
Compare the observations alongside the changed condition. Example: “The first run showed no mic activity. After selecting the headset mic, activity appeared while I spoke.” This records the difference under the new selection; next, repeat the check in the app you intend to use.
If you change devices, tasks, or several settings at once, include those differences in your notes. If an intermittent issue does not recur, write “not observed during this run.” Repeat the same task later before describing the issue as resolved.