Interactive diagnostic

Keyboard test

Verify that physical key presses reach your browser. Keystrokes stay in this page and are not stored.

Processed locally in this browser

Input inspection

Press every key you want to verify

Focus the test area, then press physical keys one at a time. A highlighted key means the browser received that input; it does not prove the switch is mechanically perfect.

Finishing saves only an evidence summary in this browser for 7 days for Device Check. Typed text, input order and movement coordinates are not stored. Untried checks are not failures.

Modifier keys0/8

Arrow keys0/4

Basic typing keys0/40

These counts show coverage of reference key groups; remaining keys are not faulty. Browser and system shortcuts can intercept input. Tab leaves the test area.

Click or tab here to start listening

EscapeF1F2F3F4F5F6F7F8F9F10F11F12

`1234567890-=⌫

TabQWERTYUIOPBracket LBracket R

CapsASDFGHJKL;'Enter

Shift LZXCVBNM,./Shift R

Ctrl LAlt LMeta LSpaceMeta RAlt R LUpDown R

Release all keys, then hold left Shift + A + S together. Verifies only this combination; it does not certify N-key rollover or diagnose ghosting.

Combination not run

On phones and tablets, connect a physical keyboard for this test.

Test guide

What this test proves—and what it cannot

The keyboard test highlights physical key events that reach the current page. It helps find intermittent keys, layout differences, modifier behavior, and browser-reserved shortcuts without installing a key logger or storing what you type.

Last reviewed: 2026-09-01

Signals measured

Keyboard events delivered to the focused browser page
Physical key code and interpreted key value when available
Modifier combinations and repeated keydown behavior
User-observed missing, duplicated, or inconsistent presses

How the test works

The test listens only while its page is open and focused.
Pressed keys are shown live. Finishing saves unique key codes and coverage locally for 7 days; a retest replaces the summary.
No typed sequence, password, or history is transmitted or persisted.
Browser and operating-system shortcuts may be intercepted before the page sees them.

Interpreting the results

SignalWhat it meansNext step

Key highlights onceThe expected event reached this page in the current layout.If one app fails, inspect its shortcuts, layout, and focus.

No eventThe page did not receive that press.Try a text editor, another port or keyboard, and check OS accessibility/remapping.

Duplicate or intermittent eventRepeat settings, contamination, switch wear, wireless link, or software remapping may contribute.Compare wired/another keyboard and an OS-level input test before repair.

Measurement limits

The page cannot see shortcuts captured by the browser, operating system, firmware, or accessibility tools.
Mobile on-screen keyboards do not expose every physical-key event.
A successful event does not test mechanical feel, switch force, backlight, or every rollover combination.

Missing or privacy-reduced detail is not scored as a fault by itself.

Questions about this test

Does DeviceTriage save what I type?

No. The page displays current key events for the test and does not send or persist a typed sequence. Do not enter passwords into any keyboard tester.

Why do some shortcut keys not appear?

The operating system or browser may reserve combinations for window control, navigation, screenshots, media, or security before a webpage receives them.