Give every key a quick check. A live keyboard map and event history show what your browser receives from your connected keyboard.
Fn / Globe, Touch ID, power and Eject / Lock are managed by macOS and excluded from your score. Layouts show classic physical positions; symbols and system keys vary by generation and input source. Some shortcuts may intercept keys. Test F1–F12 with Fn if needed.
Select a layout, focus the tester and press one key at a time. Check the event code when a label differs from your physical keyboard. KeyboardEvent.code refers to the physical position; KeyboardEvent.key reflects the active layout and modifiers.
Use the same test sequence for wired and wireless connections. If input is intermittent, repeat with a different connection when available. A web page sees the combined keyboard input and usually cannot identify which connected device produced it.
ANSI, ISO and language layouts differ. Some system shortcuts and unusual hardware keys will not produce a usable browser event. Use the event log alongside the key map and check unexpected behavior in a second app.
About the test, your keyboard, and that one key that won’t light up.
More answersYes. The Windows key is generally reported as Meta, which macOS uses for Command. Modifier remapping can change the behavior, so check your Mac settings too.
The active input source, modifier state and keyboard layout determine the character. The physical code can help distinguish a layout difference from a missing event.
From missed keys to double taps. Find the right Mac keyboard test for the job.
Inspect key codes, modifiers and input-method composition events.
Hold one key. Check the delay before repeat and its steady rhythm.
One press, two letters? Look for unexpected double-typing events.
Hold a few keys together. See which combinations make it through.
Tested in your browser. No accounts, no keystroke uploads, no fuss.
