Repeat slowly and compare another connection or computer. Macros and remapping software can also create extra events.
Part of the Keyboard test. Run the full keyboard test first for a complete device check.
Two presses after one tap No events appear Only held repeats appear
Keyboard chatter test
Log key presses and releases, then separate held-key repeats from unusually short second presses.
Also known as: keyboard chatter test. Free, online, and no download required.
No permission neededNothing uploaded
Focus the keyboard stage and tap one physical key repeatedly.
01
What the keyboard chatter test checks
| Check | How it is measured | Fails when |
|---|---|---|
| Physical press events | Non-repeat keydown events by KeyboardEvent.code. | Two separate press events appear after one intended tap. |
| Held-key repeat | Keydown events marked repeat by the browser. | Repeat events are mistaken for separate physical taps. |
| Short second press | A new non-repeat keydown less than 80 ms after a keyup on the same code. | A repeatable short pair needs further comparison, not automatic fault classification. |
How to run the keyboard chatter test
- Click or tab into the keyboard stage.
- Tap one suspect key deliberately at least twenty times and watch the recent events.
- Hold the key once to see repeat events counted separately.
- Reset, compare another key, then repeat in a plain text editor.
If something failed
Focus the stage and check whether the key is reserved by the operating system or browser.
Release the key fully between taps. Held-key repeats are deliberately excluded from the separate-press count.
02
How to read the result
How to interpret a short gap
The 80 ms marker calls attention to a second non-repeat keydown shortly after a keyup. It is a review threshold, not a hardware specification. Deliberate fast tapping can produce short gaps, so compare the log with your actual finger motion and a text editor.
Held-key auto-repeat is counted separately. A stream of repeat events while the key stays down is normal operating-system behavior and does not count as a second physical press in this tool.
Measurement limits
Browser keyboard events are delivered after the keyboard firmware, operating system, active layout, shortcuts, and remapping software. The page cannot read switch contacts or prove that a duplicated character came from the keyboard rather than an input method.
Test the same key in another application and, when possible, another computer. A repeatable event pattern across environments is more useful than one unusual interval in a short sample.
03
Keyboard chatter test questions
Is a short second press definitely chatter?
No. The flag also appears after intentional fast taps or synthetic events. Compare controlled runs and another computer before drawing a hardware conclusion.
Why are held-key repeats separate?
Browsers mark operating-system auto-repeat events. The tool keeps them out of the physical-press count so a deliberate hold does not look like chatter.