How it works
Device tests use WebRTC getUserMedia or DOM keyboard events entirely client-side.
How to use Keyboard Test
- Allow browser permissions when prompted for mic or camera.
- Select the correct device from dropdown if multiple exist.
- Perform the action (speak, press keys, click) while watching indicators.
- Fix OS settings if no signal appears, then refresh and retest.
Worked examples
Concrete numbers and cases you can check against the tool above.
Quick check
Run once before your meeting; fix issues instead of apologizing on call.
When to use Keyboard Test
Return windows close fast; documenting dead keys with an on-screen map helps RMA claims.
Common use cases
- Test new mechanical keyboard for chatter.
- Verify UK vs US layout after laptop swap.
- Check function keys on compact 60% boards.
Inputs and outputs
- Physical key events
- QWERTY layout visualization
Privacy
This tool runs entirely in your browser. Your data never leaves your device — nothing is uploaded to our servers.
Frequently asked questions
- Why is permission denied?
- Check OS privacy toggles and browser site settings, then reload.
- Is AV recorded?
- Mic and webcam tests stream locally unless you explicitly record elsewhere.
- Can I use on phone?
- Yes for many tests; CPS and keyboard tests suit desktop best.