SYSTEM READYENGINE PLATFORM-V1SUITES 07 / 37 ENTRIESPROCESSING ON DEVICERAW UPLOAD 0 BOUTPUT JSON / SCORECARD / PRINT
IP-KEY-01 / KEY / CODE / LOCATION

Keyboard Key Test

Verify physical codes, labels, locations, down/up state and full-layout coverage.

PROBLEM / SEARCH INTENT

A key is dead, stuck, mislabeled or missing only in some applications.

This focused entry uses the shared Keyboard protocol. The measurement logic and Evidence version remain identical to the complete lab.

BEFORE YOU START

Remove the easiest false alarms first.

01

Match the visible layout, focus the test surface and close shortcut-heavy apps.

02

Press deliberate full chords; repeat the same chord before calling a key missing.

03

Test repeat and chatter with one key at a time so OS repeat is not confused with switch bounce.

CONTROLLED METHOD

Run one repeatable protocol.

  1. 01

    Select the matching keyboard layout.

  2. 02

    Focus the test and press each key once.

  3. 03

    Review untested keys and reserved browser shortcuts.

RESULT FIELDS

Evidence the result should expose.

DIRECT / INFERREDPhysical code
DIRECT / INFERREDKey label
DIRECT / INFERREDLocation
DIRECT / INFERREDCoverage
DIRECT / INFERREDHeld state
DECISION GUIDE

Separate observed, review and inconclusive.

01 / OBSERVED

A received down/up sequence proves the complete keyboard-to-browser path delivered that event.

02 / REVIEW

Repeat missing keys or rapid reactivations and compare the same chord in a plain text field or system tester.

03 / INCONCLUSIVE

Reserved shortcuts, OS repeat settings and browser focus can hide or reshape events without a keyboard fault.

IF THE RESULT LOOKS WRONG

Start with the likely path, then retest.

01

Switch failure

02

Layout mismatch

03

Browser or OS reserved shortcut

Open the evidence-bound workflow