Keyboard Test
See physical key events in real time, track coverage across common layouts and investigate rollover, repeats and possible chatter.
Keyboard Layout Settings
Choose the closest physical layout. Detection always uses the browser's physical key code.
Interactive Keyboard
Click Activate, then press and release physical keys. Use Deactivate Keyboard Test to finish.
Events are processed only while this focusable test area is active. No keystrokes are stored or sent anywhere.
Keyboard Test Results
Keys Tested
0 / 104
Coverage
0%
Currently Pressed
0
Max Simultaneous
0
Last Key
None
Key Rollover & Ghosting
Held Now
0
Session Maximum
0
Browser and operating-system handling can hide some combinations. These observations do not prove NKRO or a hardware defect.
Repeat & Possible Chattering
Possible chattering is a timing observation only. Focus loss and missing keyup events are never treated as confirmed failures.
Key Event Inspector
How to use Keyboard Test
- 1
Select the closest Keyboard Size, Physical Layout and Key Labels configuration.
- 2
Click Activate Keyboard Test, then press and release keys while the test area keeps browser-detectable input captured.
- 3
Watch keys turn blue while held and red after testing; inspect coverage and Additional Detected Keys as you proceed.
- 4
Try key combinations for rollover and review repeat, possible chattering and raw event details.
- 5
Click Deactivate Test with the mouse to restore normal browser key behavior, or Reset Session to clear results.
Frequently asked questions
About Keyboard Test
A useful keyboard check must reflect physical positions as well as visible legends. Layouts range from full-size and compact boards to laptops with or without a numpad, with ANSI, ISO and several label schemes. Coverage changes with the chosen layout, and left/right modifiers and numpad keys retain distinct codes.
Beyond simple highlighting, the session records event type, location, modifiers, repeat state and timing. These signals can reveal suspicious repetition or missing combinations, but the interface deliberately labels chattering and ghosting as observations. Browser-reserved and firmware-handled keys remain outside a webpage's control.