Follow a fixed order
Starting from the top row prevents skipped keys. The progress counter makes it easy to resume after an interruption.
Full Keyboard Test
Work through the board from top to bottom. The progress panel counts tested keys, highlights detected and currently pressed states, and shows untested positions.
Mobile note: This systematic test requires a physical keyboard and is not usable as a typing exercise on touch screens.
esc F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12
` 1 2 3 4 5 6 7 8 9 0 - = backspace
tab Q W E R T Y U I O P [ ] \
caps A S D F G H J K L ; ' enter
shift Z X C V B N M , . / shift
ctrl win alt space alt win menu ctrl
Recorded keys
Local event.key Waiting
event.code Not recorded
modifiers None
0 tested
0 untested
Privacy: key events are processed only in this tab and are never transmitted.
Counts clear on reset, reload, or when the window loses focus. If you allow analytics, only a coarse test-start/test-end signal is sent, never the keys you press.
About this test
Untested vs detected
A key moves to detected when the browser sends at least one keydown. Pressing it once is enough for a basic detection check; this view ignores automatic repeats.
Some keys cannot be tested
Fn keys, media keys, and OS-reserved shortcuts may produce no browser event. The limitations panel explains which outcomes are not keyboard faults.
Run a useful comparison
What if a key is missing from the diagram?
Reset the workspace and click the heading to move focus off the Reset button. Tap A twice. The per-key list should show KEYA with a count of 2, while the progress panel marks just one diagram position as tested.
If your keyboard has a separate numeric keypad, press its Enter key. When the browser reports NUMPADENTER, it gets a separate row in the list. This ANSI diagram has no keypad, so its tested and untested totals stay the same. Press the main Enter key next: ENTER appears as a separate physical position and the tested total rises by one.
Test one row at a time with separate press-and-release actions. Note keys that are absent from the drawn layout separately. A detected key confirms an event reached the page in that attempt; it does not prove every switch, combination or intermittent fault is resolved.
Browser event background: physical key codes and automatic repeat events. For a missing key, follow the step-by-step comparison procedure.
Related tools
Related guides
How many keys does the full test cover?
The visual board covers the common ANSI key positions. Some laptops add extra media and function keys that browsers may not expose.
What if a key lights but the value looks wrong?
The physical key is detected. A different event.key value usually means the active keyboard layout or modifier state changed the produced character.
What do the different key states or colors mean in the full test?
Untested keys are gray, currently pressed keys highlight when held, and detected keys remain lit after release. This helps you see exactly which keys have been successfully registered and which still need pressing.
What should I do if a key never registers as detected?
Test a normal letter first, confirm page focus, and compare the suspect key in another application. Missing browser events alone do not prove hardware failure. Follow manufacturer instructions before cleaning or disassembly.
Does this full keyboard test work for laptops, desktops, and different keyboard layouts?
The diagram uses a fixed ANSI arrangement. Physical keyboards with a different layout can still send events. Compare their reported codes in the per-key list; only positions present in the diagram count toward completion.