Short answer: when a key types twice from one tap, the switch under that key is almost always chattering — it bounces on contact, so the keyboard reports two presses where you made one. The browser (and every app) sees a second keydown you never intended, and a second character lands. It is the keyboard cousin of mouse double-click chatter: the same worn- or dirty-contact family, only on a key instead of a button. Rule out the key-repeat setting and software first, then open the keyboard check, tap the suspect key once, and watch whether that single tap shows up as 2 down / 2 up. Keep in mind the check counts the key events your browser receives — it can show one tap arriving as two presses, but it cannot measure the switch bounce itself, the debounce window, or polling rate.
What “types twice” actually is
One clean tap should produce one keydown and one keyup for that key. Typing twice means a second press slipped in: the contact made, broke, and made again in a few milliseconds, so the firmware read two separate hits. Name your symptom before chasing a fix, because two ordinary things feel similar but are not chatter:
- Auto-repeat from holding. If you rest on a key, the operating system repeats it on purpose after a short delay (“jjjjj”). That is the key-repeat feature, not a fault, and it only starts when a key is held, not tapped.
- Two fast taps of your own. Light, springy switches and fast typing can produce a real double you did not notice making. If it only happens on hard, quick strokes and never on a slow, deliberate tap, suspect technique, not the switch.
- Real chatter. A single, deliberate, unhurried tap still produces two characters, repeatably, across different apps. That is the hardware pattern this guide is about.
Rule out settings and software first
Most doubling that is not a bad switch lives here, so clear it before you blame the key:
- Check the key-repeat delay. A very short repeat delay makes a normal hold fire extra characters and mimics chatter. In Windows Keyboard settings or macOS Key Repeat / Delay Until Repeat, lengthen the delay and retest a slow tap.
- Look at accessibility options. Filter Keys, Bounce Keys, and Slow Keys all change how repeated or quick presses are handled. One switched on — or off — can change the behavior you are seeing. Set them to a known state and retest.
- Test in a plain text field, across apps. Type the key in a bare editor or the address bar, not just one program. If it doubles everywhere it is more likely the keyboard; if it only doubles in one app with autocomplete or macros, suspect that software.
- Change the path. Try another USB port, a different cable, or — for wireless — fresh batteries and a closer receiver. A flaky connection or low battery can drop and repeat keys in ways that look like chatter.
Confirm it in the browser
Open the keyboard check, start a run, focus the pad, and tap the suspect key once, cleanly and without holding. The check lists each key it saw as a per-key count — N down / M up. A clean tap reads 1 down / 1 up. A tap that reads 2 down / 2 up means two full presses reached the browser from your one hit — the doubled press, captured. Do several slow, single taps; genuine chatter tends to repeat, while a one-off under a heavy background load is not proof. Helpfully, the check ignores the operating system’s auto-repeat, so merely holding a key does not inflate the count — what it counts are discrete presses, which is exactly what chatter adds.
What each result means
- 1 down / 1 up per tap — the key is registering once, as it should. Your doubling is coming from a short repeat delay, an accessibility option, one app, or fast technique. Fix those and it steadies.
- 2 down / 2 up on repeated single taps — the key is sending two presses from one hit. That is contact wear or debris in the switch, the same mechanism behind a mouse that double-clicks only sometimes — the contact is bouncing, and here the bounce reads as an extra keypress. The cleaning-then-replace path mirrors fixing a mouse that double-clicks on a single click.
What the browser can and cannot see
A web page sees only the key events your system sends it — keydown and keyup, by physical key — after the operating system and driver have processed them. So the keyboard check can show you a tap arriving as two presses: a real, repeatable symptom you can act on. What it cannot do is measure the switch bounce directly, the debounce window the firmware applies, the matrix scan or polling rate, or wireless latency; none of those are exposed to a browser. The keyboard check also is not timestamped the way the double-click test is, so it counts the doubled press but does not report the millisecond gap between the two. Anything claiming to read a bounce time or polling rate from a web page is inferring, not measuring — the same reason a page cannot truly read a polling rate.
The same family as mouse double-click chatter
A key that types twice and a mouse that clicks twice are the same failure wearing different clothes: a switch whose contact bounces, so one action registers as two. The mouse side of this is the better documented one on this site — if you want to see the interval pattern in real numbers, the double-click chatter reference walks through an open dataset of mouse double-click intervals (mouse data, not keyboard, but the bounce behavior is the shared idea). For rate-style keyboard checks rather than per-key events, the keyboard counter and typing test are where a doubled letter usually first shows up in everyday use.
If it is the switch
Once settings and software are ruled out and a slow single tap repeatedly reads 2 down / 2 up, treat it as hardware. Cleaning resolves some early cases: power down, pop the keycap, and blow out dust and debris with compressed air. A key that keeps doubling after cleaning is failing — on a hot-swap mechanical board you can replace that one switch, while on a soldered or membrane keyboard it usually means a board-level repair or a new keyboard. If the keyboard is in warranty, capture the repeatable symptom — a short screen recording of the keyboard check showing one tap register as two presses — the same way you would build evidence for any warranty or RMA claim. Not sure how a run is judged first? The method page explains what a completed observation does and does not certify.