Keyboard test results explained

The four key states

In the keyboard test each key on the map has one of four states:

• White, not pressed yet: no press from this key has arrived.
• Orange, held down now: a press arrived and the release has not arrived yet.
• Green, pressed and released: both events arrived. The key works for this test.
• Dashed border, release not seen: the page lost focus while the key was down, for example because a shortcut opened another window, so the release could not be observed. This is not a fault; press the key again.

Keys tested counts the green keys, and List keys not tested yet names the rest, which is useful on large keyboards.

Pattern: a key stays white

Illustrative example: on a full-size keyboard every key turns green except the letter E.

The press never reached the browser. Press firmly and from different angles; if it stays white, the likely causes are the switch, dirt or a stuck membrane under that key, or a damaged circuit. Before blaming the hardware, check that it is not a key browsers never receive (next section). The step-by-step checks are in keyboard keys not working.

If several neighbouring keys or a whole row stay white, think of the circuit rather than individual switches, especially after a spill.

Keys that never light up in any browser

• Fn: handled inside the keyboard on almost every model and never sent to the computer.
• Media, brightness and some laptop keys: often handled by the keyboard or the operating system.
• System shortcuts: Ctrl+Alt+Del, sometimes the Windows key, Cmd+Tab on a Mac and similar combinations are taken by the operating system first.
• Print Screen: some systems handle it before the browser, so its press or release may be missing.

Press Start full capture to test keys the browser normally uses itself, such as Tab, Space, the arrows and F-keys. Keys from the list above can still stay white: that is a limit of browser testing, not a fault.

Pattern: a key stays orange

Illustrative example: you press and release Space, and it remains orange.

The release was not received. Press the key again. If it happens every time, the key is physically sticking or the switch is not opening properly; on long keys check the stabiliser. On a Mac, keys pressed while Command is held are a special case: the browser does not report their release, and the test marks them released, with a note, when Command is let go.

Pattern: the wrong key lights up, or a key outside the map

• A different key lights up: the keyboard reports a different physical code from the one at that position. This happens with damaged circuits, with remapping in keyboard software or firmware, and with keyboards whose physical layout differs from the map. Check the exact code in the event log or the keycode tester.
• Keys outside this map: extra keys such as macro keys or language keys are listed separately. Seeing them there means they work.
• No physical key code reported: some devices, on-screen keyboards and input methods send a character without a physical code. A real keyboard key normally has one.
• The map switched to ISO: you pressed the extra key next to left Shift, so the test changed layout to show it.

Wrong symbols with the right key lighting up are a layout setting: see keyboard typing wrong symbols.

Results from the other keyboard tests

• Chatter test: flagged presses with very short gaps during slow tapping mean the switch reports two presses for one tap. Compare with healthy keys on the same keyboard rather than relying on one threshold. See keyboard typing double letters.
• Ghosting test: a key that stays dark while you hold a combination was blocked by the keys already held. It shows this combination on this computer, not a certified rollover figure.
• Numpad test: the Num Lock indicator tells you whether the pad sends numbers or navigation keys.

Recording a result for a return or warranty

The test runs only in your browser and does not save or send anything. To document a fault:

1. Test on a direct connection, then on a second port or computer, so you can say the fault is repeatable.
2. Take a screenshot of the keyboard map and of the List keys not tested yet message after pressing every key.
3. For chatter, take a screenshot of the flagged count and gaps for the faulty key next to a healthy key.
4. Note the keyboard model, connection type and date.

A browser test is evidence of what the computer received, not a manufacturer diagnosis. Sellers may run their own checks.