What this test checks
Test keyboard presses and releases, recognised key positions, repeated events and simultaneous combinations in your browser.
InputAnalyzer processes test events locally and does not upload your raw inputs or result values.
How to run the test
Activate the test area
Select Start test, then keep focus inside the test while checking keys. Normal page navigation stays available outside it.
Press and release each key
Work through the keys you want to verify and watch their pressed and released states.
Try useful combinations
Hold several ordinary keys together, avoiding operating-system or browser shortcuts you do not want to trigger.
How to read the result
Observed signals, not artificial certainty.
Normal event pair
A key shows one initial press, optional deliberate repeat events while held, and a release when let go.
Missing or stuck state
No response, unexplained repeats or a key that remains active can merit a retest after restoring focus.
What this test cannot prove
What the browser cannot see
- Reserved system shortcuts and some media or firmware keys may never reach the page.
- The browser cannot prove that an untested key is broken, and keyboard layouts can give one position different printed labels.
- Results are browser-based estimates, not a physical hardware diagnosis.
Useful next tests
Frequently asked questions
Short answers before you test again
What is the difference between key position and key value?
Position identifies the physical location (`code`); value reflects the active layout and modifiers (`key`). InputAnalyzer shows both when available.
Why did a shortcut leave the test page?
Browsers and operating systems keep control of reserved shortcuts. The test deliberately does not block them globally.