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 or reload.
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 check; holding it adds repeat information.
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.
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.