Your test data stays in this browser.Security and Privacy
Device Test Bench

Observation → comparison → next step

Plan a Missing Keyboard Input Check

Separate page focus, layout and connection problems with a three-comparison keyboard worksheet and a clear record for support.

Published 2026-10-01

Your working record stays in this page. No automatic device access, media capture or saved test history. Copy or print only if you choose.

A key can look dead even when its press reaches the operating system. A shortcut can intercept it, a layout can change the character, or focus can be in another control. This plan separates three questions: does the page receive the press, does another application receive it, and does the behavior follow the keyboard or the computer? Keep the key, connection and action identical between comparisons.

Before the comparison

Comparison 1 of 3

Check focus and the delivered event

Focus Keyboard Test, press and release the affected key three times, and compare a nearby key. Check both key and code instead of looking only at the diagram.

Why it matters. key describes the interpreted value; code describes the physical-key position exposed by the browser. Their disagreement can identify a layout question without proving switch damage.

Open Keyboard Test (new tab)

All possible observations and next steps
ObservationWhat it suggestsUseful next step
The affected key now appearsRefocusing changed the observation. The original application may still have its own focus or shortcut behavior.Repeat in the original application without changing any hardware.
code appears but the character is unexpectedAn event reached the browser. Input language, modifiers, Num Lock or remapping may explain the character.Compare Key Code Tester with the intended operating-system layout selected.
Nearby keys appear but the affected key does notThis is a localized missing event in one application, not yet proof of a failed switch.Keep the connection unchanged and make the second-application comparison below.

Comparison 2 of 3

Compare a second application

Try the same harmless key in a plain text editor. For a modifier, use a safe combination rather than a shortcut that closes a window.

Why it matters. A result confined to one application favors an application or event-interception investigation. Agreement across applications narrows the uncertainty but does not distinguish a cable, driver, accessibility setting or switch.

Open Key Code Tester (new tab)

All possible observations and next steps
ObservationWhat it suggestsUseful next step
It works in the second applicationThe key can generate usable input under another application path.Inspect the original application shortcuts, extensions and input settings.
The same input is missing in bothThe pattern is reproducible beyond this page.Compare the connection or keyboard once, leaving layout settings unchanged.
The second application was not checkedThere is no cross-application evidence yet.Record this as not tested rather than interpreting the browser result as a hardware verdict.

Comparison 3 of 3

Identify what the failure follows

For an external keyboard, compare a direct port or another compatible computer. Alternatively, try a known-working keyboard on this computer. Repeat the same affected key in Keyboard Test and change only one factor.

Why it matters. A direct-port improvement is evidence about the connection path. A failure that follows the board deserves model-specific support; a failure that stays with the computer deserves a settings or input-path comparison.

Open Keyboard Test (new tab)

All possible observations and next steps
ObservationWhat it suggestsUseful next step
A direct connection changes the resultThe connection path is relevant; the test does not isolate which hub, cable or port caused it.Record the two connection paths and verify the improvement again before replacing equipment.
The issue follows this keyboard to another computerThe board-associated pattern is stronger evidence, but it still is not an electrical diagnosis.Give the manufacturer the key and repeated comparisons; follow its cleaning or warranty instructions.
A second keyboard has the same issue on this computerA shared setting, application or computer input path remains a useful lead.Check layout, remapping and accessibility settings before proposing a keyboard repair.

Your private comparison record

Use a general device description, not a serial number or private recording. Do not enter passwords, complete typed messages or sensitive personal information. Leaving or reloading this page can discard the record; the site does not save it.

How to describe evidence

Illustrative example, not a measured case report. The A key is absent here but appears in a text editor with the same keyboard and port.

Useful conclusion. The failure is application-specific in this comparison. The next check is focus or interception, not a switch replacement.

Stop conditions and limits

Do not remove keycaps, apply liquid or change firmware solely because a browser missed a key. Stop using physically damaged or unusually hot equipment and consult the manufacturer.

This workflow cannot certify hardware, decide warranty eligibility or replace model-specific inspection. It does not request camera, microphone or controller access. Dedicated tests require separate deliberate actions.

Primary and official references

These sources document browser behavior or platform troubleshooting. Our comparison sequence is an editorial workflow, not a manufacturer-approved repair procedure.

Questions about this comparison

Does a missing highlight prove a dead switch?

No. It records a missing browser event. Repeat in another application and compare the connection before assigning a physical cause.

Can I compare a built-in keyboard with a USB keyboard?

Yes, but record that they use different input paths. A working external keyboard is useful evidence, not a complete diagnosis of the built-in assembly.

Read the detailed explanation

Choose another problem · Report a correction

Search