Keyboard Test

How to use this keyboard test

This keyboard test checks whether a key press reaches the focused browser panel. Click the detection area once, then press each key you want to verify. The page shows the visible key value, the browser key code, and the number of distinct keys it has detected. Start with letters, numbers, arrows, and modifier keys one at a time. Testing slowly matters: it helps distinguish a key that never arrives from a key that was pressed while another app, browser shortcut, or system feature had focus.

What the keyboard test records

Browsers expose a key value and a physical-style code for keyboard interaction. For example, the visible value can reflect a layout while the code helps identify the physical key location. This keyboard test shows both so that a key such as Shift, Enter, ArrowLeft, or Space is easier to describe accurately. The W3C KeyboardEvent key values specification documents the values browsers use for these events. A detected event is evidence that this tab received the press, not a complete hardware diagnosis.

Test individual keyboard keys systematically

Work through the part of the keyboard that concerns you rather than pressing random keys. If a letter feels unreliable, press it 10 to 15 times with normal force and watch whether every fresh press updates the test. If a modifier seems wrong, test it separately and then with a letter. For an external keyboard, repeat the same short set after reconnecting the cable, charging it, or moving its wireless receiver. A written result such as “the E key was detected 9 of 10 times on two browsers” is more useful than saying the keyboard feels inconsistent.

Why a key may not appear in a browser test

Focus is the first thing to check. Click the test control and try again, because key events go to the currently focused element. Some shortcuts are intentionally handled by the operating system, browser, accessibility software, or a vendor utility before a webpage sees them. Media keys and special function layers may also behave differently from a standard letter key. If one key is absent only in one application but appears here, the issue is more likely application configuration than an immediately provable keyboard switch problem.

Keyboard layouts, repeats, and modifiers

A keyboard layout can change the printed character without changing the physical key you pressed. Auto-repeat can also create repeated keydown events when a key is held, which is not the same as repeatedly pressing and releasing it. For that reason, make individual checks with deliberate releases between presses. Test left and right modifiers separately when relevant: a shortcut may depend on one specific key position. This page does not block normal key behavior broadly, so avoid system shortcuts that could navigate away or change another application.

Use focused follow-up tools

Individual keys and combinations answer different questions. Use the Keyboard Ghosting Test when a key works alone but seems to disappear while W, A, S, D, or Space are held together. Use the Spacebar Test when the long Space key misses presses or repeats unexpectedly. These focused pages keep one intent per test, making a result easier to reproduce and explain.

Limits of an online keyboard test

An online keyboard test cannot inspect a switch, keycap stabilizer, cable, receiver, battery, firmware, or operating-system driver. It cannot confirm how a particular game captures raw input. It can, however, provide a neutral browser comparison. Try the same keyboard on another computer, or try a known-good keyboard on the same computer, before deciding whether the fault follows the device. Clean or service a keyboard only according to its manufacturer’s guidance, especially if it is wireless or has a built-in battery.