Keyboard Test Keys Not Detected: 4 Fixes That Actually Work

Last reviewed 2026-05-03. If your browser keyboard test opens but some keys never highlight when you press them, the keyboard is rarely broken - one of four causes below is far more likely. Walk the list top-down; each fix takes under a minute.

Fix 1 - The page lost keyboard focus

Browsers route key events to whichever element has focus. The keyboard test draws an on-screen layout, but unless you click into the page first, your keystrokes go to the address bar, an extension popup, or a different tab. The symptom: every key looks like it works (the OS captures it), but nothing on the test highlights.

Click into the test: click any empty area of the keyboard test page once. The page now owns the keystroke routing; press a key and it should highlight immediately.

Close popups and overlays: autofill prompts, password manager extensions, and screenshot tools (Snagit, Greenshot) sometimes capture global hotkeys. Close every popup, then re-test.

Switch tab and switch back: if a meeting client (Zoom, Teams) was the previous foreground window, it may still be holding global keystrokes. Switch tabs and back into the keyboard test to force the browser to reclaim focus.

If clicking back into the page makes the keys highlight, focus was the cause. Move on only if highlighting still fails.

Fix 2 - OS keyboard layout or language mismatch

The keyboard test uses the JavaScript KeyboardEvent.code to identify the physical key (e.g. KeyA, Quote). When your OS keyboard layout does not match the labels printed on the keys, the press registers, but it lands on a different on-screen position - which looks like "the key did nothing" because the highlight appears on a different cell.

macOS: System Settings → Keyboard → Input Sources. Confirm the active layout matches your physical keyboard (US, UK, Vietnamese Telex, etc.). If you recently switched languages, switch back; the test should highlight the correct cell.

Windows 11 / 10: Settings → Time & language → Language & region. Check the active input method per language. Press Win + Space to cycle layouts and re-test.

Linux (X11 / Wayland): run setxkbmap -query to see the active layout; setxkbmap us resets to a US layout for testing.

Quick test: press the Q key on the top-left and confirm "Q" highlights on the test layout. If it highlights "A" instead, your OS thinks the keyboard is AZERTY (French). Switch the OS layout, do not relabel the keys.

Fix 3 - Accessibility filter is intercepting events

Modern OSes ship accessibility helpers (Sticky Keys, Filter Keys, Slow Keys, Mouse Keys) that absorb or delay keystrokes before the browser sees them. Sticky Keys turns chord input (Ctrl + C) into sequence input (Ctrl, then C); Filter Keys ignores brief presses to help users with hand tremors; both also affect a quick-press keyboard test.

Windows: Settings → Accessibility → Keyboard. Turn off Sticky Keys, Filter Keys, and Toggle Keys. Re-test.

macOS: System Settings → Accessibility → Keyboard. Turn off Sticky Keys and Slow Keys. Many laptops accidentally enable Slow Keys when the user-help shortcut (5x Shift) fires.

Virtual-keyboard drivers: some keyboards ship with their own remapping software (Logitech G HUB, Razer Synapse, ASUS Armoury Crate, Karabiner-Elements on macOS). These can intercept events for macros. Quit the helper app and re-test; if keys now highlight, the helper had a remap that pointed elsewhere.

Browser extensions: Vimium, Surfingkeys, and Tridactyl rebind keys at the page level. Disable browser extensions or use a guest profile.

Fix 4 - Hardware-level lock or connection

The last layer is the keyboard itself. A few common hardware reasons cause keys to never reach the OS:

Fn-row toggle: business laptops (ThinkPad, Latitude, EliteBook) ship with an Fn-Lock that swaps the F1-F12 row between media keys (default) and function keys. Press Fn + Esc (most ThinkPads) or Fn + Shift to toggle. If the F-keys never highlight, this is usually why.

Lock keys (Caps / Num / Scroll): the LED on the keyboard tells you whether a lock toggle is on. Test: turn Num Lock ON and press the numpad - the digits should highlight. If they do not, the keyboard's numpad is wired to a separate USB controller that may not be enumerated.

USB / Bluetooth connection: external keyboards on a flaky cable can drop individual keystrokes. Re-seat the cable in a different port; for Bluetooth, re-pair. A wireless keyboard with a near-empty battery often presents this exact symptom.

BIOS HID disable: Lenovo, Dell, and HP business BIOS expose a "USB keyboard support" toggle that controls whether the keyboard works in pre-OS environments and whether all keys are forwarded to the OS. Reboot, enter setup (F1 / F2 / F12), look for Devices → USB Setup or Security → I/O Port Access → USB, confirm enabled.

Still some keys missing? - the diagnostic flow

1. Try a second site. Open en.key-test.ru in the same browser session. If that site also misses the same keys, the cause is upstream of the test page (focus, layout, accessibility, or hardware).
2. Try a second browser. If Chrome misses keys but Firefox catches them, the cause is browser-level (extension, profile, or a stale event listener). Use a guest profile to confirm.
3. Try a second user account. Switch to a freshly-created OS user and open the keyboard test. If it works there, the cause is in your user profile (a remap, an accessibility flag, or a virtual-keyboard driver registered for your user).
4. Try a second machine. If a phone or tablet shows the keyboard test working immediately with a paired Bluetooth keyboard, the failing machine has a hardware or driver issue. Open Device Manager (Windows) or System Information (macOS) and look for the keyboard under Human Interface Devices.

The four steps narrow the cause from the test page outward to the hardware in under five minutes.

What about modifier keys (Shift, Ctrl, Alt, Cmd, Win)?

Modifier keys are the most common "missing" keys on a quick keyboard test because they only highlight when you also press a non-modifier in chord. The keyboard test page handles each modifier as a standalone press: hold Shift (left or right) and the corresponding cell on the test should highlight - no other key required. If only one side highlights, the other side's switch may have a stuck contact - press both sides and look for asymmetric behaviour.

FAQ

Why does the same key sometimes highlight and sometimes not?
Intermittent detection is usually a hardware problem - dirt or wear under the keycap. Pop the keycap, blow out debris with compressed air, and re-test. If the issue persists in another OS user (Fix Diagnostic 3), the keyboard hardware needs warranty service.

Does Caps Lock affect the keyboard test results?
No. The test reads KeyboardEvent.code, which is the same regardless of shift / caps state. If A and a both light the A cell, the test is working correctly.

Why don't multimedia keys (Play, Pause, Volume) highlight?
Most OS-level multimedia keys are absorbed by the OS before the browser sees them. The keyboard test cannot reliably highlight them. Their absence does not mean the keys are broken - press one and check the OS volume responds.

I see the right key highlight on the test, but the wrong character types in a text field. Is the keyboard broken?
No - the keyboard hardware is fine. Your OS keyboard layout is set to a different language (Fix 2). The test confirms the physical key works; the layout decides what character it produces.

Related

• Keyboard test - the tool itself; run it after each fix.
• How to test a keyboard online, step by step - the 60-second walk-through that covers every key.
• Keyboard tester online: rollover vs anti-ghosting - the concept guide for why some chords miss keys.
• Camera test black screen: 4 fixes - the same four-layer model applied to camera input.
• Microphone test no sound: 4 fixes - the same four-layer model applied to microphone input.
• Device test checklist for remote work - the weekly cadence that catches new failures before a call.
• Device test tools hub - keyboard, camera, microphone, LCD, and more in one cluster.