A received down/up sequence proves the complete keyboard-to-browser path delivered that event.
Keyboard Key Test
Verify physical codes, labels, locations, down/up state and full-layout coverage.
A key is dead, stuck, mislabeled or missing only in some applications.
This focused entry uses the shared Keyboard protocol. The measurement logic and Evidence version remain identical to the complete lab.
Remove the easiest false alarms first.
Match the visible layout, focus the test surface and close shortcut-heavy apps.
Press deliberate full chords; repeat the same chord before calling a key missing.
Test repeat and chatter with one key at a time so OS repeat is not confused with switch bounce.
Run one repeatable protocol.
- 01
Select the matching keyboard layout.
- 02
Focus the test and press each key once.
- 03
Review untested keys and reserved browser shortcuts.
Evidence the result should expose.
Separate observed, review and inconclusive.
Repeat missing keys or rapid reactivations and compare the same chord in a plain text field or system tester.
Reserved shortcuts, OS repeat settings and browser focus can hide or reshape events without a keyboard fault.
Start with the likely path, then retest.
Switch failure
Layout mismatch
Browser or OS reserved shortcut