Private browser event check
Keyboard Tester
Confirm that the browser receives key-down and key-up events from common physical keyboard keys. Tested and currently held keys are shown without building or saving typed text.
Privacy: do not type passwords or sensitive information into keyboard testing pages. This tool keeps only key-state details in memory for the current tab; it does not store, transmit, analyze, or log a typed sequence.
Test area: click Activate or focus this region, then press physical keys. Green means tested; blue means currently held.
- Last key
- —
- Code
- —
- State
- —
- Modifiers
- None
- Active keys
- None
- Unique tested
- 0
- Events observed
- 0
Loading local keyboard tester…
Event model, privacy, and limitations
The visual board maps KeyboardEvent.code, which represents the physical key position where the browser exposes it. The status panel also shows KeyboardEvent.key, which reflects the current layout and modifier result. Key-down adds a held state; key-up releases it; focus loss clears all held states so the board cannot remain visually stuck.
The listener runs only while the dedicated test area has focus. It does not call preventDefault(), so Tab, refresh, address-bar, browser, and system shortcuts remain under normal browser/OS control. Some shortcuts may leave the test area or never reach the page.
Fn, brightness/media keys, vendor keys, OS-reserved shortcuts, and some international-layout keys may not appear or may not map to the US ANSI visual board. A missing browser event does not conclusively prove hardware failure. This tool does not measure polling rate or latency, diagnose firmware/drivers, remap keys, or record macros.