Keyboard Key Not Working?
If a key does not type, determine whether the browser receives its keydown and keyup events. A missing event may come from focus, keyboard layout, operating-system shortcuts, accessibility settings, connection problems, or the physical switch.
Open the Keyboard Test →Common causes
Wrong input language, Num Lock or Fn layers, remapping software, browser shortcuts, wireless battery issues, debris, and damaged switches can all change a key’s behavior. Some system and media keys are intentionally intercepted before a web page can observe them.
One-key example you can repeat
Read these labels in plain language
- key — what the key means now
- For A on a US English layout, this is usually
a; with Shift it can beA. - code — which key position was pressed
- The same A-position key reports
KeyAeven when Shift changes the character. Another keyboard layout can produce a different character at that position. - Held now — how many keys are still down
- Hold only A: 1. Release it: 0. This is not your total number of key presses.
- Tested keys — different positions seen so far
- Press and release A twice: this stays 1. It does not count the second press as a new key.
key is the character or action Chrome reports for the current layout; code identifies the physical-key position, such as KeyA. They are not interchangeable. A non-US layout or Shift can change key without changing code.
- Open Keyboard Test. Click a non-editable part of the page, not the language selector. Inputs, text areas and selectors are intentionally excluded from the test's key handler.
- Choose Reset so this session starts with zero tested and held keys. On a US English layout with Shift off, press and hold A: expect
key=a,code=KeyA, a highlighted key and Held now: 1. - Release A. Expect a keyup event and Held now: 0; the tested-key count remains 1. Press A again: it is still one distinct tested key, not a count of keystrokes.
- Repeat with the particular key that fails in your application. Record the exact key/code and whether both down and up arrive. Use a normal text editor as a separate check, then compare another port or known working keyboard if needed.
- Choose Reset before comparing another keyboard or layout. Do not enter passwords or personal text into a diagnostic page.
Interpret the observation
- A different character appears: inspect input language, Shift, Caps Lock or remapping first. Temporarily disable a remapping tool only if you use one, then repeat. A different key value alone does not prove switch failure.
- No event appears: focus the page again. System shortcuts and some media keys may never reach the browser. Compare normal typing and another application; reconnect the keyboard and check wireless batteries before comparing ports or devices.
- The key stays held: release all keys and refocus/reset. Changing windows can interrupt a release event; reproduce it before suspecting hardware.
- Only a multi-key combination fails: use the rollover guide. A single-key test cannot establish the keyboard's combination limit.
FAQ
Does Tested keys count every press?
No. It counts distinct observed key positions during this session. Holding a key can generate repeated events without adding distinct keys.
Can a browser certify a broken switch?
No. This reports events that reached this page. Firmware, layout, OS interception, focus and connection must be considered separately. Automated key events verify this display path, not the physical switch.
What the browser test can confirm
The test can show browser key events, highlight tested keys, and expose repeated or missing releases. It cannot observe keys reserved by the operating system, certify a switch, measure electrical bounce directly, or distinguish every firmware issue.
Limits and privacy
Keyboard events stay in the page and are not uploaded by the Device Check test engine.
A successful browser result means the expected event or stream reached this page during the test. It is useful evidence, but it is not a repair, calibration, warranty, or manufacturer certification.
Related guides
Ready to verify the result?
Run the relevant Device Check tool after completing the steps above.
Open the Keyboard Test →