Expected key detected
The keyboard produced an input that reached this browser. If the key still fails in one app or game, inspect its bindings, layout, shortcuts, remapping, and accessibility settings.
Unresponsive-key troubleshooting
Keyboard Key Not Working?
Select the physical key that seems unresponsive, then press it to see whether a matching event reaches this browser.
Detection stays in temporary browser memory.
Focused key check
Check whether the key is detected
After selecting, press that key on your physical keyboard. Detection uses KeyboardEvent.code.
Expected key—
Last key detected—
Keys tested0
Currently pressed0
Select the key you want to check
Choosing a physical key lets the test compare your expectation with the browser event.
Swipe sideways to view the full keyboard.
- Esc
- F1
- F2
- F3
- F4
- F5
- F6
- F7
- F8
- F9
- F10
- F11
- F12
- Prt Sc
- Scr Lk
- Pause
- ~`
- !1
- @2
- #3
- $4
- %5
- ^6
- &7
- *8
- (9
- )0
- _-
- +=
- Backspace
- Tab
- Q
- W
- E
- R
- T
- Y
- U
- I
- O
- P
- {[
- }]
- |\
- Caps Lock
- 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
- Num Lock
- /
- ×
- −
- Home7
- ↑8
- Pg Up9
- +
- ←4
- 5
- →6
- End1
- ↓2
- Pg Dn3
- Enter
- Ins0
- Del.
A detected event confirms only that this browser received that physical key position. It does not certify the keyboard hardware.
Three useful scenarios
Interpret what the browser received
No matching event yet
Press it again, then compare another browser, connection, USB port, or computer. Absence here makes a hardware issue more plausible only after those comparisons.
Not normally observable
Fn-layer controls, media keys, firmware-only functions, and OS-reserved shortcuts may never produce a standard browser event.
Hardware or software?
Why one key may stop responding
A single key can be affected by application bindings, an active keyboard layout, remapping software, accessibility features, firmware, connection state, or physical behavior. Detection here establishes only whether a matching physical-position event reached the page.
Laptop keyboard considerations
Laptop function rows and embedded numpads often depend on an Fn layer handled by firmware. Those functions may work normally without exposing a testable browser key code.
What to try before replacing the keyboard
- Press the selected key again and compare nearby keys.
- Test in another browser and a simple text editor.
- Review the current keyboard language and application bindings.
- Temporarily pause macro or remapping utilities where safe.
- Reconnect an external keyboard or try another suitable port.
- Compare the keyboard on another computer when practical.
Evidence, not certification
What browser detection can and cannot prove
If the selected key is detected here, the browser received an event from that physical position. This does not prove every application, modifier combination, or electrical path works normally.
If it is not detected, the page still cannot know whether the cause is the keyboard, operating system, firmware, connection, reserved shortcut, or browser. Cross-environment comparison is the useful next step.
Privacy: expected key, detected codes, and visual state are not uploaded or stored.