Why Some Keys Are Not Detected in Browsers

A missing highlight in an online keyboard test is a symptom, not a hardware diagnosis. The page only sees events delivered by the browser, and the diagram cannot represent every keyboard layout. Start with the keyboard key test and compare a normal letter with the key you are investigating.

Establish a baseline before testing a special key

1. Bring the test page to the foreground. Click a plain area of the page so that the address bar, search box, and other controls do not have focus.
2. Press and release A once. On a US English layout without Caps Lock, the event sheet should show a and KEYA.
3. Press Shift+A. The last key value should become A; the A-position code remains KEYA. Other layouts may produce a different character.
4. Release the keys and inspect the per-key list. In this Key Detail test, automatic repeats from holding a key do not increase the count. A new press after release does.
5. Use Reset before comparing the suspect key. It clears the displayed values, counts, and highlights. Switching away from the browser window also clears this test, so write down a result before leaving it.

These checks validate the event path and the tool display. They do not measure physical switch response time or certify the keyboard. Our October 14 software regression check exercises a received keydown followed by Reset and window blur; it does not simulate a physical Fn key or establish compatibility with every operating system.

Match the symptom to the next useful check

What you observe	What it can mean	Next step
Ordinary letters work; Fn does not appear	The keyboard firmware or system may handle Fn before the page can see it	Try the intended Fn function and consult the keyboard manual
A value appears, but the character differs from the keycap	Layout, Shift, Caps Lock, or an input method may change the produced character	Compare the active input layout and read key versus code
A code appears in the list but no matching key lights	This page draws an ANSI keyboard, which does not include every key	Use the event sheet and list as the result
The previous key stays on screen after a special key	No usable new event may have reached this tool	Reset, confirm a letter works, then repeat the suspect key
Nothing responds, including ordinary letters	Focus, a script-loading problem, or the input device may be involved	Refocus the page and reload; then compare a second browser
Keys work separately but not together	A combination may be intercepted or limited by the input path	Compare that combination in the rollover test

Why Fn, media keys, and shortcuts differ

Fn is often interpreted inside the keyboard or by its driver. Volume and brightness controls vary across devices, operating systems, and browsers. A working volume control with no entry in the test is therefore not sufficient evidence of a defective switch.

System and browser shortcuts can also act before a page handles them. Do not use a close-tab or switch-window shortcut as your first diagnostic test: it can close your test or clear its state. Some combinations may deliver part of their event sequence, while others may not. A web page cannot guarantee interception of every shortcut.

What this particular test can and cannot show

The event sheet displays the most recent keydown, with codes converted to uppercase for readability. It is not a complete keydown/keyup log. It does not show a separate event.location field. SHIFTLEFT and SHIFTRIGHT, when supplied, can distinguish the two Shift positions.

The tool ignores an event whose physical code is empty. This matters for virtual keyboards and unusual input devices: an unchanged result may reflect that limitation rather than an absent input. A phone’s touch keyboard is not a substitute for testing a physical board. The diagram is a reference layout, not automatic detection of your exact hardware.

Compare one condition at a time

Note your browser, operating system, keyboard model, active input layout, connection type, and the exact result. Then repeat the same ordinary key and suspect key in another browser. For printable keys, also try a text editor. For a media or Fn control, test its intended system function instead.

If the same physical key fails across applications, inspect the connection and try another port or device before assuming the switch is faulty. If a second keyboard works in the same setup, that narrows the investigation; it still does not identify a specific failed component. Continue with the unresponsive keys checklist for hardware-oriented checks.

Technical references

Browser character values depend on modifiers and layout; physical codes describe key positions rather than the character printed by the active layout. See MDN: KeyboardEvent.key and MDN: KeyboardEvent.code. Device-specific behavior still needs a test on the device concerned.