A received down/up sequence proves the complete keyboard-to-browser path delivered that event.
IP-KEY-01 / KEY / CODE / LOCATION
Keyboard NKRO Challenge
Run guided gaming and modifier chords while measuring concurrent browser-delivered keys.
Several keys work alone but fail when held together.
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.
01
Match the visible layout, focus the test surface and close shortcut-heavy apps.
02
Press deliberate full chords; repeat the same chord before calling a key missing.
03
Test repeat and chatter with one key at a time so OS repeat is not confused with switch bounce.
Run one repeatable protocol.
- 01
Choose the FPS, MOBA, modifier, racing or rhythm challenge.
- 02
Hold the complete chord at the same time.
- 03
Compare expected and received physical codes.
Evidence the result should expose.
DIRECT / INFERREDMaximum held keys
DIRECT / INFERREDExpected chord
DIRECT / INFERREDReceived chord
DIRECT / INFERREDChallenge result
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.
01
Keyboard rollover matrix
02
OS shortcut capture
03
Incomplete simultaneous press