Broken Key Detector

If repeatedly pressing a physical key fails to produce any keydown events on the virtual keyboard or event log, the key is not communicating with your browser. This could be due to a faulty switch, oxidized contacts, or software suppression.

A single dead key is often caused by dust or liquid residue inside the mechanical switch, a cold solder joint, a bent switch pin in hot-swap sockets, or background software assigning that key as a global hotkey.

Yes. It tests alphanumeric keys, numbers, function keys, navigation keys, arrows, and modifiers. Specialized OEM keys (e.g. Fn, volume knobs) may be handled entirely by hardware firmware.

Intermittent registration usually indicates switch chatter, oxidized contact leaves, or loose solder joints. Use the Consistency Test with 5 or 10 strikes to measure intermittent failure rates.

Yes. Certain browser keyboard shortcuts (such as Ctrl+W, F5, or Alt+Left) may trigger browser navigation before the web page can process the event. Fullscreen mode helps capture more inputs.

No. Web applications can only observe events passed by the operating system. Background macro tools, accessibility utilities, or tab blur can prevent events from reaching the browser without switch damage.

Press each laptop key normally. Laptop scissor switches are sensitive to dust and crumbs under the membrane scissor mechanism. If multiple adjacent keys fail, inspect ribbon cables.

Yes. Mechanical switches with MX stems, optical switches, and magnetic Hall-effect switches all work identically with this browser-level test.

Yes. 2.4GHz wireless and Bluetooth keyboards work seamlessly, helping you identify wireless packet drops or interference.

On many laptop and compact keyboards, F1–F12 act as media controls (volume, brightness) by default unless the Fn Lock key is toggled.

Yes. Left and right modifiers have individual detection. The Modifier Check panel displays real-time PASS status when pressed.

When a key is skipped or appears missing during guided testing, the tool prompts you to press it again. This eliminates false alarms caused by accidental typing skips.

No. All keyboard events and diagnostics run strictly client-side inside your browser. No keystrokes or diagnostic logs are ever transmitted to any server.