Follow a fixed order
Starting from the top row prevents skipped keys. The progress counter makes it easy to resume after an interruption.
Work through the board from top to bottom. The progress panel counts tested keys, highlights detected and currently pressed states, and shows untested positions.
Starting from the top row prevents skipped keys. The progress counter makes it easy to resume after an interruption.
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.
Fn keys, media keys, and OS-reserved shortcuts may produce no browser event. The limitations panel explains which outcomes are not keyboard faults.
The visual board covers the common ANSI key positions. Some laptops add extra media and function keys that browsers may not expose.
The physical key is detected. A different event.key value usually means the active keyboard layout or modifier state changed the produced character.
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.
First, press and hold the key for a few seconds. If it still doesn't register, try cleaning around the key or testing with a different keyboard. Hardware failure may be causing the issue.
Yes, the test works with any standard USB, wireless, or built-in laptop keyboard. It maps common keys based on your operating system, so you can verify most layouts and identify stuck or non-responsive keys.