KEYBOARD SUPPORT GUIDE

A keyboard key is not working. Find the fault before replacing anything.

Start with a repeatable browser check, then compare the pattern with another browser, another keyboard or the operating system. This guide helps you decide whether the problem is the key, the layout, software, the cable or the laptop assembly.

Start with the symptom

Choose the description that matches what you see. The next step stays deliberately small and reversible.

One key does not work

If the key never registers in KeyTest, repeat it in another browser and compare an external keyboard. One isolated failure points toward the switch, membrane or local contact.

Next: test the same key outside this browser, then compare the physical pattern.

KEYBOARD SUPPORT GUIDE

1. Run the keyboard test

Select the physical layout and form factor first. KeyTest records browser keyboard events locally; it does not save what you type.

Choose Laptop, Laptop + Numpad, Full Size, TKL, 60% or Mac to match the device.
Press each testable key once. Use the counter and the untested-key list to identify gaps.
Repeat suspicious keys in Advanced mode. Treat chatter and stuck-key indicators as signals to review, not an automatic hardware verdict.

KEYBOARD SUPPORT GUIDE

2. One key does not respond

A single missing event is not enough to identify the failed layer. Prove that the browser is receiving other keys, then compare the same key elsewhere.

Try the key in another browser and a plain text editor.
If an external keyboard works on the same computer, the built-in key or laptop assembly becomes more likely.
If the same key fails across keyboards, investigate layout, accessibility settings, remapping software or the operating system.

KEYBOARD SUPPORT GUIDE

3. The key sends the wrong character

When the physical key highlights but the character is unexpected, the input mapping is usually the first place to look.

Compare the printed legend, the selected KeyTest layout and the operating-system input language.
Check whether a keyboard utility or remapping tool changes the key before it reaches the application.
Use a plain editor to separate a browser shortcut from a layout problem.

KEYBOARD SUPPORT GUIDE

4. Repeating, chattering or stuck keys

A repeated event may be a physical switch signal, a held modifier, a macro, accessibility setting or an application loop.

Release every key, reset the test and repeat the key slowly.
Use Advanced mode to note repeats or possible chatter, then verify in another application.
Do not spray liquid or force a key mechanism; power down and seek service after a spill or visible damage.

KEYBOARD SUPPORT GUIDE

5. Multiple keys fail

The shape of the failure is more useful than the raw count. Adjacent rows, columns or a rectangular cluster can point to a shared circuit path.

Record the exact keys and their physical positions in the report notes.
Try a known-working external keyboard directly, bypassing an unpowered hub.
If only the built-in cluster fails, professional inspection of the keyboard matrix, ribbon and assembly is safer than probing it live.

KEYBOARD SUPPORT GUIDE

6. Numpad and system keys

Numpad behavior depends on Num Lock and the OS. Fn, Power, brightness and some media keys can be handled below the browser event layer.

Select the matching form factor and test Num Lock before judging number keys.
Treat navigation output from number keys as a mode clue, not proof of a failed keypad.
Use the laptop or manufacturer indicator for firmware-only keys; KeyTest cannot confirm events the browser never receives.

KEYBOARD SUPPORT GUIDE

7. External USB and laptop keyboards

A comparison keyboard is a useful isolation tool. It should be known-working and connected directly to the computer whenever possible.

For USB: try a different port, remove the hub, check the cable and confirm the OS detects the device.
For wireless: charge the keyboard, re-pair it and test the receiver on another port.
For laptops: after a spill, impact or repair, stop before opening the chassis and use a qualified technician if the cable or assembly may be damaged.

KEYBOARD SUPPORT GUIDE

8. When professional repair is appropriate

Seek service when there is liquid damage, a repeating cluster, a damaged ribbon, a keyboard that disappears from the OS, or a safety risk from continued use.

Save the local report or print it without including typed text.
Share the failed-key pattern, layout, form factor and comparison results with the repair shop.
Do not claim that a browser test proves switch health, firmware behavior or motherboard integrity.

QUICK REFERENCE

Symptom → likely cause → what to test next

Symptom → likely cause → what to test next
Symptom	Possible cause	What to test next
One key never registers	Local switch, membrane, contact or debris	Another browser, then compare a known-working keyboard
Wrong character	OS layout, input language or remapping	Verify the selected layout and test in a plain editor
Nearby keys fail together	Matrix row/column, ribbon or liquid damage	Map the pattern and compare an external keyboard
A press repeats	Chatter, a stuck key, macro or software repeat	Advanced mode, then another app and browser
Numpad acts as navigation	Num Lock or operating-system mode	Toggle Num Lock and test the numeric form
Fn or Power is invisible	Firmware or keyboard-controller handling	Use the on-device indicator; browsers cannot receive every system key
USB keyboard fails too	Port, hub, cable, driver or OS issue	Connect directly to another port with a known-good cable

TEST LIMITS

What this guide can and cannot prove

KeyTest is a browser event check. It can show which standard keyboard events reached the page and can help compare layouts, form factors and repeat signals. It cannot inspect firmware-only keys, every ghosting combination, switch health under load or the physical keyboard assembly.

LINKABLE DESCRIPTION

A short description you can quote

KeyTest is a browser-based keyboard and hardware diagnostic tool that lets people test individual keys, keyboard layouts and physical form factors without installing software.