How to test every keyboard key online

A useful keyboard test is more than typing a sentence. Normal text does not exercise every function key, modifier, navigation key, or number-pad position, and it can hide a key that works only when pressed at one angle. A visual tester makes the coverage visible.

Start with a controlled test

Open the keyboard tester, select the test panel, and press one physical key at a time. The page uses the browser’s physical KeyboardEvent.code, so a key is matched to its position rather than to the character produced by the current language layout.

Work across the board in rows. Watch for three things:

1. The expected virtual key reacts while the physical key is held.
2. The tested state remains after release, proving that position was covered.
3. The key counter advances once for the intended press instead of missing or rapidly repeating it.

Test both left and right modifiers. They are separate switches even when an application treats them as the same command. Toggle Caps Lock, Num Lock, and Scroll Lock where available, but remember that operating systems and compact keyboards expose lock state differently.

Check a suspicious key more than once

If a key is not detected, click the tester panel again before deciding it has failed. Browser focus may have moved to the address bar, a button, or another application. Some operating-system shortcuts are intercepted before a web page receives them, and firmware layers can remap a physical position.

Once focus is confirmed, press the key near its center and then from its edges. A switch that responds only with extra force or at one angle may have a mechanical contact, stabilizer, or socket problem. A key that always triggers a different position may be remapped in firmware or software.

Separate the keyboard from the computer

A browser test shows which keyboard events reached that page. It cannot inspect the switch electrically or prove where an event was lost. If a key stays absent:

• reconnect a wired keyboard directly instead of through a hub;
• recharge or replace batteries on a wireless model;
• test another USB port and close remapping utilities;
• try the keyboard on a second computer;
• compare the result in another browser.

If the same physical key fails everywhere, hardware becomes the stronger explanation. If it fails only in one application or profile, investigate software mappings and shortcuts first.

Test combinations after individual keys

Passing every key individually does not prove that every combination works. Keyboard matrices and firmware can limit simultaneous inputs. After the single-key pass, use the keyboard rollover tester for gaming, shortcut, or accessibility combinations that matter to you.

Keep the result practical: record the key, connection mode, port, browser, and whether the failure follows the keyboard to another device. That short record is more useful for troubleshooting or a warranty report than a single screenshot without test conditions.

Make a coverage plan for unusual keys

Compact and programmable keyboards need a little extra care. A key printed with two functions may expose only its base position to the browser; the alternate function can be generated by firmware when an Fn layer is active. Browsers usually do not receive a separate event for the Fn key itself. Test the output of the layer, such as volume, navigation, or function-row behavior, but do not mark Fn as broken merely because there is no matching browser key.

Media keys can also be handled by the operating system. If volume changes but the page shows nothing, the keyboard did send a useful command; the system simply consumed it outside the page. Screenshot, brightness, power, and vendor-specific controls have similar limitations. Record these separately from standard keyboard positions.

For a number pad, test Num Lock both ways. The same physical positions may report digits in one state and navigation commands in another. On a laptop, repeat the test with any embedded number-pad layer enabled and disabled.

Turn the result into a repeatable report

If you need support, avoid a vague description such as “some keys sometimes fail.” Use a compact table:

Field	Example
Physical key	Right Shift
Result	Misses about 2 of 10 centered presses
Connection	Direct USB, supplied cable
Comparison	Same result in two browsers and another computer
Other keys	Left Shift passes 10 of 10

Repeat only enough times to establish the pattern; pounding a damaged key adds no diagnostic value. Save the browser and operating-system versions if the failure is software-specific. For intermittent faults, note whether moving the cable, changing wireless distance, or allowing the keyboard to warm up changes the result. These observations help distinguish a switch problem from connection, power, or configuration behavior.

Technical references

• The W3C KeyboardEvent code Values recommendation defines the physical-position codes used by the tester.
• MDN’s KeyboardEvent reference explains the browser event interface and its platform-dependent limits.