How the keyboard test works
Every key press sends two pieces of information to the browser. KeyboardEvent.code names the physical key (the one in the position of Q on a US keyboard is always KeyQ), and KeyboardEvent.key gives the character your layout produces (q in QWERTY, a in AZERTY). The test draws the keyboard from the first value, so a key is found at its place whatever language your keyboard is set to.
- Orange means the key is held down right now.
- Green means the key has been tested at least once.
- The counter shows how many keys of the drawn keyboard you have tested. Aim for all of them.
- The panel under the keyboard shows the last key with its character, its code and its legacy key code, plus a history of your last presses.
Space, the arrow keys, Tab and the function keys are held back while the test is active, so the page does not scroll or lose focus. Press Escape twice to leave the test with the keyboard and get your normal Tab navigation back.
Pick the right layout
Choose ANSI or ISO to match the shape of your Enter key, then the labels: QWERTY (US and UK), AZERTY (France, Belgium) or QWERTZ (Germany, Austria, Switzerland). The labels change, the test does not: a key is a key. In Chrome and Edge, the page asks the browser for your real layout and uses it when available. Hide the numeric keypad for a laptop or a tenkeyless keyboard, so the counter only counts the keys you actually have.
Reading the result
| What you see | What it means |
|---|---|
| A key never turns green | Dead switch, broken solder joint or dirt under the keycap. Check it in a text editor to rule out a system key. |
| A key lights up without being touched | Stuck switch or short circuit in the matrix. |
| One press shows twice in the history | Chatter: a worn mechanical switch that bounces. Clean or replace it. |
| A key lights up a different key | The keyboard is set to the wrong layout in your operating system, or a remapping tool is running. |
| Several keys fail when held together | That is ghosting. Run the keyboard ghosting test. |
The limits of a browser test
A web page only sees what the operating system passes on. Fn never leaves the keyboard. The Windows or Command key, Print Screen and some media keys are often intercepted or only reported on release. A few shortcuts, like Alt+Tab or Ctrl+W, act before the page can stop them, so test those keys alone.
The test does not measure how many keys you can hold at once (the ghosting test does), nor the latency of your keyboard. If every key turns green here but one does not work in a game, check the game’s key bindings or any macro software before blaming the hardware.
Frequently asked questions
Why does a key not light up?
Either the key is dead, or your operating system keeps it for itself. Try it in a text editor. If it types there but not here, it is a system key (see the limits below). If it types nowhere, the switch or the keyboard matrix is faulty.
Why are the Windows and Fn keys not detected?
Fn is handled inside the keyboard and never reaches the computer. The Windows key and some shortcuts (Alt+Tab, Ctrl+Alt+Del) are caught by the operating system before the browser sees them, or only half reported. That is a browser limit, not a fault in your keyboard.
Does it work with an AZERTY or QWERTZ keyboard?
Yes. The test reads the physical position of each key, so it works with any layout. Pick QWERTY, AZERTY or QWERTZ to match the labels. In Chrome and Edge the labels are read from your system settings automatically.
What is the difference between ANSI and ISO?
ANSI keyboards, common in the US, have a wide one-row Enter key and a long left Shift. ISO keyboards, common in Europe, have a tall L-shaped Enter and an extra key between the left Shift and Z (or W on AZERTY).
Is what I type recorded?
No. The keys are read in your browser and only kept in memory to draw the keyboard and the history. Nothing is saved or sent, and reloading the page clears everything.
Updated October 26, 2026