How to interpret the result
Missing events can indicate a hardware switch, matrix limitation, firmware mapping, browser shortcut, operating-system interception, or accessibility setting. Repeat outside the browser before concluding.
Test every mapped key, inspect keydown and keyup codes, and measure how many simultaneous keys the browser receives.
Focus this area, then press each key and the combinations you use.
This records only events delivered to this browser. Re-test a concern in another app before deciding whether it is hardware, layout, firmware, wireless, accessibility, or an OS shortcut.
| Event | Code | Repeat |
|---|
Missing events can indicate a hardware switch, matrix limitation, firmware mapping, browser shortcut, operating-system interception, or accessibility setting. Repeat outside the browser before concluding.
The browser cannot distinguish all firmware-level ghosting, debounce quality, scan rate, switch chatter outside the event stream, or keys reserved by the operating system.
Verify pointer movement, primary and auxiliary buttons, wheel direction, double clicks, and browser-reported coordinates.
Open testDraw with one or more contacts to inspect edge coverage, tracking continuity, contact count, and pointer cancellation.
Open testRead connected gamepads, buttons, triggers, stick axes, timestamps, and mapping through the browser Gamepad API.
Open testWhat to verify while return and exchange options are still simple: identity, exterior, display, input, media, battery evidence, ports, updates, and recovery.
Read guideWhat a browser key visualizer can reveal, what the operating system may intercept, and when to confirm with another application.
Read guide