Keyboard Diagnostics Hub
TEST A KEYBOARD METHODICALLY
A key that never appears, a key that looks stuck, a gaming combination that drops one input and a mechanical switch that sometimes types twice are different symptoms. Treating all of them as “the keyboard is broken” makes troubleshooting slower.
This guide connects GearCheck Lab’s three keyboard diagnostics into a repeatable browser-based workflow. It explains what the page can observe, which shortcuts the browser may never receive, how ghosting differs from rollover, and why normal operating-system key repeat must not be confused with switch chatter.
A practical keyboard test sequence
Start with the simplest question—does each key produce an event?—then move to multi-key behavior and finally the timing of a suspect switch. That order prevents a matrix limitation or system shortcut from being mistaken for a dead key.
- Run an individual-key pass.
Open the Keyboard Test and press the keys you actually use. Confirm that ordinary letters, numbers, arrows, modifiers and navigation keys produce the expected browser-visible activity. Do not use Fn as a pass/fail key because it is commonly handled inside the keyboard itself. - Retest a suspicious key deliberately.
If a key appears missing, release all other keys and press it several times on its own. Check whether an operating-system shortcut, function layer, keyboard layout or accessibility feature could be consuming the event. - Test real simultaneous combinations.
Use the Ghosting & Rollover Test with combinations you actually use—such as W + A + Shift + Space—not just the largest number your fingers can reach. Repeat a missing-key combination before treating it as a matrix limitation. - Separate a double-typing symptom from held-key repeat.
If one key produces two characters from a normal tap, use the Keyboard Chatter Test. It measures same-key release-to-retrigger gaps while excluding browser events marked as normal held-key repeat. - Compare connection and software variables.
For detachable keyboards, compare another USB port or wired/Bluetooth mode where available. Close macro/remapping tools if they may alter input. If the same symptom appears on another computer, that increases confidence that the problem follows the keyboard. - Repeat after cleaning, repair or configuration changes.
Use the same key, combination and chatter threshold before and after the change. A repeatable before/after comparison is more useful than a one-off “it feels better” result.
Choose the keyboard diagnostic that matches the symptom
Ghosting and rollover describe different behavior
Rollover is the number of simultaneous keys the keyboard can report correctly for a given situation. A board may advertise 6KRO or NKRO, but practical behavior can depend on the connection mode, firmware and which keys are involved.
Ghosting traditionally describes matrix ambiguity where a combination can create an unintended key or cause a real key to be blocked. Many users loosely call any missing multi-key input “ghosting,” but distinguishing the symptom matters when comparing keyboards.
A high simultaneous count on one combination does not prove every possible combination will work. Test the keys you use together in real games, shortcuts or applications.
Why shortcuts can look like missing keys
Browsers do not own the keyboard. The operating system, browser chrome and accessibility features can intercept combinations before JavaScript receives them. Alt+Tab, Meta/Windows shortcuts, browser tab controls and some media keys are common examples.
If an isolated key works but a system shortcut does not appear in the tester, that may be normal. Try a different combination using the same physical keys before deciding the keyboard matrix is at fault.
Held-key repeat is not switch chatter
When you hold a key, the operating system intentionally starts repeating it after a delay. Modern browsers expose that state through KeyboardEvent.repeat. GearCheck Lab’s chatter diagnostic counts those events separately and excludes them from suspected duplicate-registration timing.
Suspected chatter is different: a key is released and then another non-repeat keydown for the same key arrives unusually soon. Even that is troubleshooting evidence, not direct electrical measurement of contact bounce.
There is no universal browser-visible chatter threshold
Keyboard firmware implements debounce differently, and the browser sees events only after firmware, USB/Bluetooth transport, the operating system and scheduling. A single fast interval does not certify a faulty switch.
Use a conservative threshold, collect at least a useful set of deliberate taps, and look for a repeatable pattern on the suspect key. Then compare a known-good key using the same tapping style and threshold.
Interpret common keyboard symptoms
| Observation | What it may suggest | Useful next step |
|---|
| One ordinary key never appears | Physical switch/key mechanism, keyboard mapping, firmware or connection issue. | Press it alone several times, compare another browser/computer and inspect remapping software. |
| Key works alone but disappears in one combination | Matrix blocking/rollover limit or an intercepted shortcut. | Repeat the combination in the Ghosting & Rollover Test and try alternative keys that avoid OS/browser shortcuts. |
| An unintended key appears while several are held | Possible matrix ghosting behavior or software remapping. | Repeat the exact physical combination and compare on another system if possible. |
| One tap occasionally produces two characters | Possible switch chatter, firmware debounce, macro/remapping or application behavior. | Use the Chatter Test, compare a known-good key, then test another application/computer. |
| Holding a key produces many repeated keydowns | Usually normal OS auto-repeat. | Check whether the browser marks those events as repeat; GearCheck Lab excludes them from chatter suspicion. |
| Several keys fail after a spill | Contamination or damage may affect a shared matrix region. | Power down and follow the manufacturer’s safe service guidance; do not keep stress-testing wet hardware. |
| Wireless keyboard misses input but USB is stable | Battery, radio interference, pairing or wireless stack may be involved. | Charge/replace batteries, re-pair and compare at close range. |
What browser keyboard tests can observe
Strong use caseOrdinary keydown/keyup activity, held keys, repeat flags, simultaneous browser-visible inputs and repeatable same-key re-triggers.
Useful comparisonOne key vs another, wired vs wireless, before/after cleaning or repair, and the same combination across two systems.
Needs cautionFn/media keys, system shortcuts, manufacturer NKRO claims and any conclusion about the internal switch or matrix electronics.
Physical key position and typed character are not always the same
Keyboard events can expose a physical code and a layout-dependent character. The same physical key position can produce a different character under another language/layout. When diagnosing whether the hardware position is responding, physical key codes are often more useful than the printed character alone.
This is especially relevant when comparing AZERTY, QWERTY, QWERTZ, laptop layouts or remapped keyboards. A different character does not necessarily mean the physical key is faulty.
Testing after repair, cleaning or buying used
- Run a full individual-key pass before focusing on one symptom.
- Test modifiers on both sides where your keyboard has them.
- Try several combinations across different keyboard rows.
- Check the real shortcuts or game combinations you depend on.
- For a suspect mechanical switch, collect repeated deliberate taps—not just one press.
- Compare wired/wireless modes if both are supported.
- Document the same test before and after a repair or switch replacement.
Keyboard testing FAQ
Why does the Fn key not show up?
Fn is commonly processed inside the keyboard firmware and may never be sent to the operating system as a normal web-visible key event. Its absence from a browser tester is not automatically a fault.
Does six simultaneous keys prove 6KRO?
It proves that the tested six-key combination reached the browser. A formal rollover claim is broader and may depend on which keys are used or which USB mode the keyboard exposes.
Can I test a laptop keyboard?
Yes for ordinary browser-visible keys. Laptop-specific function-layer, brightness and media commands may be handled by firmware or the operating system and may not reach the page.
Can an on-screen mobile keyboard be tested?
These diagnostics are intended for physical keyboards. Software keyboards on phones and tablets do not expose physical-key behavior in the same way.
Does a chatter warning mean I should replace the switch?
Not by itself. Repeat the test, compare another key and another computer/application if possible, and check firmware/debounce/remapping settings before deciding on repair.