Quick answer
What Keyboard Test tells you
Press keys on a visual ANSI keyboard and inspect key, code, location, modifier and repeat state in real time.
- Observed here
- Key down and key up events, Left and right modifiers, Numpad location.
- How to interpret it
- A highlighted key means its key event reached this focused page. The displayed key and code describe the interpreted value and physical-key identifier; they can differ when a layout or modifier changes.
- Important limit
- Results reflect events and values exposed by this browser.
- Data handling
- Key events and typed text stay in this browser. They are not sent to our server or analytics.
Useful next comparison: For a missing key, focus the test area, repeat that key alone and compare it in another application before blaming the switch.
Understanding the result
What a result means
A key is observed only when the page receives both its press and release events. Compare key for the produced value, code for the physical position and location for left, right or number-pad controls; one highlighted key does not prove that every combination works.
Confirm the pattern by repeating key down and key up events. Results reflect events and values exposed by this browser.
How to use this test
- Read the privacy and compatibility notes.
- Start the test and interact only inside the marked test area.
- Repeat the action several times and compare the live indicators.
- Use the troubleshooting section before deciding that hardware is faulty.
What this test checks
- Key down and key up events
- Left and right modifiers
- Numpad location
- Simultaneous keys and repeat state
What this test cannot check
Results reflect events and values exposed by this browser.
This test does not certify hardware or replace professional inspection.
System shortcuts are never intentionally blocked.
IME and accessibility input can produce different event sequences.
Common problems and troubleshooting
If a key stays dark, click the test pad again and try the same key in a plain text editor. When code appears but key is unexpected, check the active keyboard layout, Num Lock, modifiers and IME before reconnecting or cleaning the keyboard.
- Repeat the same observation. Focus the test surface and repeat “Key down and key up events” three times under the same conditions.
- Change one condition. Compare “Left and right modifiers” after changing only the relevant port, connection, browser setting or application.
- Rule out focus or interception. Close overlays and reserved shortcuts, keep the page visible and confirm that the live indicator changes during the action.
- Keep the result within its limit. Results reflect events and values exposed by this browser.
If the same pattern remains across relevant applications and connections, give the manufacturer or a qualified technician the repeatable observations instead of a guessed fault label.
Browser compatibility
Modern desktop browsers expose KeyboardEvent key, code, location and repeat, but operating-system shortcuts may be intercepted before the page. Mobile software keyboards and assistive input do not reproduce a physical keyboard event stream reliably.
| Browser | Reference status | Evidence basis | Version | Notes | Checked |
|---|---|---|---|---|---|
| Chrome | Supported | Expected baseline | Not recorded | Feature detection is authoritative; permissions, platform and device support can change availability. | 2026-08-27 |
| Microsoft Edge | Supported | Expected baseline | Not recorded | Feature detection is authoritative; permissions, platform and device support can change availability. | 2026-08-27 |
| Firefox | Partial | Expected baseline | Not recorded | Feature detection is authoritative; permissions, platform and device support can change availability. | 2026-08-27 |
| Safari | Partial | Expected baseline | Not recorded | Feature detection is authoritative; permissions, platform and device support can change availability. | 2026-08-27 |
Privacy information
Key events and typed text stay in this browser. They are not sent to our server or analytics.
The public analytics allowlist does not accept pressed keys, typed text, pointer coordinates, media labels, device IDs, recordings, video frames or controller input. Test results are not written to LocalStorage.
Primary technical references
These specifications define the browser signals used by this test. They document web-platform behavior; they do not certify a particular device.
Frequently asked questions
Is this Keyboard Test free?
Yes. The test works without an account, download or payment.
Is my test data uploaded?
Key events and typed text stay in this browser. They are not sent to our server or analytics.
Does this result prove my hardware is faulty?
No. It shows what the browser can observe. Repeat the test, compare another browser or device, and seek qualified support when the result matters.
Turn this result into a useful comparison
A working indicator or an unexpected event is only a starting point. Choose a plan to compare another application or connection and record what changed.
- Plan a Missing Keyboard Input Check — Separate page focus, layout and connection problems with a three-comparison keyboard worksheet and a clear record for support.