Quick answer
Besides a web test, use OS settings, vendor tools, meeting-app tests and a second device for cross-checking. Keyboard testing checks every key, double presses/stuck keys and the OS layout mapping.
Why it matters
Cross-checking separates a dead device from an app/computer issue.
A dead key can be the switch, ribbon or layout mapping.
Step by step
- Close apps that may lock the Keyboard (meetings, streaming, recording, chat).
- Allow Keyboard permission in the browser address bar and OS privacy settings.
- Select the exact Keyboard in the device list instead of trusting 'system default'.
- Run one input/output test and watch 10-30 seconds for dropouts, clipping or stutter.
- Retest with another browser, port or cable to see whether the issue reproduces.
Common mistakes
- Testing the Keyboard in one app only, without another browser/meeting app.
- Ignoring OS privacy settings while repeatedly clicking Allow on the page.
- Judging with a bad cable or unpowered hub and declaring the device dead.
- Mistaking software gain/beauty filters/noise suppression for hardware quality.
Checklist
- The Keyboard is recognized by the OS.
- Browser and OS permissions are allowed.
- Input/output device selection is correct.
- A 30-second run has no dropouts.
- A second environment reproduces the same result.
Key facts
- A dead key can be the switch, ribbon or layout mapping.
- Double presses are often software; test another browser/OS first.
FAQ
What alternatives exist for Keyboard testing?
Besides a web test, use OS settings, vendor tools, meeting-app tests and a second device for cross-checking. Keyboard testing checks every key, double presses/stuck keys and the OS layout mapping.
How long does it take?
Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.
Is data uploaded?
Runs locally and does not upload video/audio; extensions may still read the page.
Source: MDN KeyboardEvent