Keyboard repair claim: document key failures

A keyboard repair claim is easier to assess when you can show exactly what fails, when it happens, and whether the problem follows the keyboard. A vague note like “some keys do not work” may not give a repair shop enough to reproduce the fault.

Use the Keyboard Test to check whether keys register in your browser and how many keys work at once. Then write down the results and repeat the checks under simple, consistent conditions. The test helps document symptoms, but it cannot identify the damaged component inside the keyboard.

Test the keyboard and record what happens

1. Open the Keyboard Test on the computer connected to the keyboard you want to claim. If possible, disconnect other keyboards so you can identify which one is sending input.
2. Press each key once, including the keys involved in the problem. Watch the test as you press them, and make a written list of keys that do not register or behave differently than expected.
3. Repeat each problem key several times at a normal typing pace. Note whether the failure happens every time, only occasionally, or only after the keyboard has been in use for a while.
4. For a problem that happens only with key combinations, press the usual combination together and note which keys register. The test checks how many keys can work at once, but results can depend on the keyboard's design and the combination you press.
5. Take a screenshot of a useful test result if the page shows one, and keep your written notes with it. Record the keyboard model, connection type, computer, browser, date, and the exact steps that reproduce the fault.

Describe what you physically pressed and what appeared in the test. Do not assume a key failed just because the intended character did not appear in a document. A different keyboard layout or application setting can change the character without stopping the key from registering.

What the result means

A key repeatedly does not register

If the same physical key is missing across repeated presses, that is a clear symptom to report. Test nearby keys too, then check the keyboard on another computer if you can. A failure that follows the keyboard is stronger evidence of a keyboard-side problem than a failure seen on only one computer.

Several nearby keys fail together

A cluster of nonworking keys may point to a shared keyboard circuit or connection, but a browser test cannot confirm the cause. Record the exact key names and whether the failures began at the same time. Do not remove keycaps or open the keyboard before checking the warranty terms.

Keys register alone but not in a combination

This may be a rollover limit. Rollover is the number of simultaneous key presses a keyboard can report. Some keyboards cannot register every possible combination, and some combinations may be blocked by the keyboard's design. Include the exact keys and test them on another keyboard before treating this alone as proof of a defect.

The test shows the keys, but the wrong characters appear

The keyboard is sending input, so check the selected keyboard layout and the app where you noticed the problem. If the issue happens only in one program, include that detail in your notes. It may be a layout or software issue rather than a failed key switch.

Function or shortcut keys do not show a response

Some keys do not reach the browser as ordinary key input. The Fn key never reaches the browser, and the Windows key, Print Screen, and laptop brightness, volume, and Wi-Fi shortcuts are usually handled by the operating system first. A missing response for one of these keys in a browser test does not by itself prove that the keyboard is faulty.

Rule out common causes before filing the claim

1. Check for a physical lock or mute setting. Look for a keyboard lock, gaming mode, or function-layer setting that could change key behavior. Check the keyboard manual if you are not sure what a mode indicator means.
2. Check accessibility settings. On Windows 11, open Settings › Accessibility › Keyboard and check whether Filter Keys is changing how key presses are accepted. On a Mac, open System Settings › Accessibility › Keyboard and check Slow Keys. Record the original setting before changing it, then repeat the test.
3. Check the keyboard layout. Confirm that the selected input language and layout match the keyboard. On Windows 11, check Settings › Time & language › Language & region. On a Mac, check System Settings › Keyboard › Text Input.
4. Reconnect the keyboard. For a USB keyboard, try another port and connect it directly instead of through a hub. For a wireless keyboard, check its battery and reconnect its receiver or Bluetooth connection.
5. Test another computer or keyboard. Connect the same keyboard to another computer and repeat the problem-key check. If available, connect a known-working keyboard to the original computer. This helps show whether the symptom follows the keyboard or stays with the computer.
6. Restart and repeat the test. A restart can clear a temporary input problem. Keep the same test steps and write down whether the result changed.

When the keyboard may need repair

A hardware claim is more convincing when the same key or group of keys fails repeatedly, the symptom follows the keyboard to another computer, and a second keyboard works normally on the original computer. Include brief notes rather than a long diagnosis: name each affected key, describe the failure, state how often it happened, and list the checks you performed.

If the keyboard was exposed to liquid, was dropped, or has a damaged cable, report that honestly. Stop using it if it becomes unusually hot, smells burnt, or has visible damage. Do not keep pressing a key that sticks or feels physically jammed. Follow the seller's or manufacturer's instructions for the claim, and avoid opening the device unless they authorize it.

What the browser test cannot prove

The Keyboard Test checks input the browser receives. It does not inspect the keyboard's internal circuit, measure how much force a key needs, identify a specific damaged switch, or confirm firmware behavior outside the browser. Operating-system shortcuts can also prevent some keys from appearing in the test. Describe the result as an observed symptom, not as a confirmed diagnosis.

Keep the original notes and screenshots together, and do not include passwords or private messages in any evidence you send.