Keyboard Test: Check Keys and Key Combinations

Test an unresponsive key with a repeatable task

Click inside the keyboard tester to activate it. Tap the suspect key five times slowly, fully releasing it between taps. Next, tap two nearby keys five times each as comparison keys. Write the exact sequence in the task field—for example, “A × 5, S × 5, D × 5; USB keyboard; US input layout.” Use your own suspect key and keep that sequence for the retest.

Read press and release separately: keydown is the browser event for a key being pressed; keyup is the event for it being released. Look for a press followed by a release for each deliberate tap. Check the event log as well as the visual keyboard, especially when a key has no matching tile. The displayed labels include codes such as KeyA and ShiftLeft; use them to track the same physical key rather than treating them as a transcription of what you typed. [键盘检测 - 免费在线测试机械键盘按键是否正常 - escwasd wasd test 机械键盘]

An online keyboard test can show whether the browser receives a key event, but it cannot identify every hardware or software fault by itself. [Keyboard Test – Free Online Keyboard Tester]

Record the first result before making an adjustment. Choose one next step: reconnect the keyboard, try another USB port, or recharge a wireless keyboard. Reset the current observations, reactivate the test area, and repeat the same keys in the same order, with the same number of taps and release rhythm. Keep the keyboard, browser, input layout, and Num Lock state unchanged unless one of those is the condition you are deliberately testing.

Describe the outcome narrowly. For example: “Before: no S events in five taps. After changing the USB port: five S presses and five releases.” That is useful evidence of a change under those conditions, not proof of the original cause. If the key still fails, repeat the task in another browser or a plain text editor; use another computer if available. Note each environment change separately. Persistent failure across those checks is a practical reason to seek manufacturer support or repair assessment.

If the key registers here but fails in one application, check that application's shortcuts and key assignments, then repeat the action there. If it registers as an unexpected character, record the active input language and layout before changing them. Keep “no event,” “different character,” and “fails only in this app” as separate observations.

Separate held-key repeat from double typing

Holding a key is a different test from making a brief tap. The browser's repeat property is true when a key is held down and automatically repeating. [KeyboardEvent: repeat property - Web APIs | MDN]

In this tester, “Press (keydown)” identifies a press event without the repeat flag, “Automatic repeat (keydown)” identifies an event with that flag, and “Release (keyup)” identifies a release. Several automatic-repeat entries during one intentional hold should be recorded as held-key repeat, not counted as several deliberate taps.

To compare the two behaviors, first tap the suspect key five times with a full release and a clear pause between taps. Then hold that same key for about two seconds and release it. Record the tap result separately from the hold result. For example: “Five brief taps: no unexpected extra input. Two-second hold: automatic-repeat entries while held.” Use exactly the same tap count and hold duration after your adjustment.

If a brief tap appears to produce extra press events, or produces two characters in a text editor, record that as unexpected extra input and check whether it happens again. Do not diagnose switch chatter from a flashing tile, an event count, or one attempt. The repeat flag describes the event the browser reported; it does not inspect the switch or establish why an unexpected event occurred.

For a key that appears to stay held after release, keep the test area focused while checking the sequence. If focus is lost, release every key and click the area again before restarting the task. This tester clears its temporary held-key display when focus leaves the area, so an interrupted attempt should not be used to judge whether a release was detected.

Check Fn and combinations within browser limits

Browser and operating-system shortcuts can reserve some keys. [Keyboard Test – Free Online Keyboard Tester]

On many laptops, Fn is handled by keyboard firmware and is not exposed to the browser as a normal keyboard event. [Keyboard Test – Free Online Keyboard Tester]

A missing Fn entry therefore does not establish a fault. Test the intended Fn function separately—for example, whether Fn plus the brightness key changes brightness—and note that functional result alongside the browser observation. Check your keyboard manufacturer's instructions for its Fn layer and Fn Lock behavior.

For a combination, test each participating key alone first. Then hold the exact combination you need, such as Shift + W + Space, and compare the held-key display with your fingers. Release all keys before trying again. Record which key is missing, the order you pressed the keys, and whether each key worked individually.

A missing key in a combination can reflect keyboard rollover limits, the connection, or browser and operating-system handling. [Keyboard Test – Free Online Keyboard Tester]

Retest the same combination with the same press order after one adjustment. A successful combination only demonstrates that particular combination in the current environment; it does not certify every combination or N-key rollover. If the keys work separately but the combination remains incomplete, preserve that distinction in your result.

Tab is intentionally reserved for leaving this test area and is not logged as a tested key. Avoid shortcuts that close tabs, navigate away, or interrupt your session. If a shortcut moves focus or opens a browser or system feature, record the attempt as interrupted, release all keys, and reactivate the area. To check the shortcut's intended action, try it in the application where you normally use it.