How to investigate a key that types twice
Keyboard chatter is an unintended series of inputs from one intended actuation. Mechanical contact bounce can cause it, but duplicate characters may also come from macros, remapping tools, remote sessions, accessibility settings, or deliberate rapid tapping.
This test compares browser keydown timestamps for the same code and flags gaps at or below your selected threshold. Events marked as automatic repeat are excluded. The thresholds are adjustable screening settings, not physiological limits or manufacturer pass/fail specifications.
Make a controlled comparison: tap one suspect key slowly twenty times and compare its observed count with your intended taps. Repeat with a nearby key. Reproduce any discrepancy in a plain text editor, then on a second computer if available.
The report covers a rolling window of the latest 600 events. Session presses can keep rising after older samples leave the window; the flagged rate uses only the presses still in that window. No finite clean sample rules out an intermittent problem.
Browser timestamp rounding, delayed event delivery, software-generated input and keyboard firmware affect what arrives. A 0 ms interval does not mean zero switch latency. The test cannot identify whether duplicate inputs originated in a switch or software.
Read how our browser tests work for event handling, measurement limits, and privacy details.