A keyboard tester on iPhone can verify only keys that the browser receives as physical key events; it does not test taps on the built-in iOS keyboard.
That distinction matters because the Keyboard Tester uses a QWERTY display to report physical key events captured by the browser. Its verified compatibility statement covers modern browsers on desktops and laptops, not iPhone itself. On an iPhone, treat the page as a possible external-keyboard check rather than a confirmed iPhone-compatible tester; a result counts only when the browser actually delivers the attached keyboard's events.

What This iPhone Test Can Actually Verify
The tool's on-screen QWERTY layout is a visual report of received physical key events. It is not the iPhone's native software keyboard. The supported workflow is therefore aimed at a physical keyboard: press a key, watch its matching button light up, and review the reported values. Do not interpret an unmarked key on the QWERTY display as proof that the corresponding button in iOS is defective.
| Target or behavior | What the tool can show | Important boundary |
|---|---|---|
| Attached physical keyboard | A matching QWERTY key lights up, remains marked as tested, and glows while held. | Support for the browser page itself is not guaranteed on iPhone, even when the external keyboard is connected. |
| Built-in iOS software keyboard | No supported physical-key check. | This workflow does not validate taps or the behavior of the native iPhone keyboard. |
| Fn, media, or some lock keys | They may appear when the browser receives a keyboard event. | iOS or the keyboard hardware may handle some of them before the browser can report them. |
| Several keys held together | Which simultaneous presses the browser receives. | The tool does not calculate or display a numeric rollover limit. |
| Stuck or repeating key | A key can remain highlighted after release or fire repeatedly from one tap. | This suggests a switch or mechanical problem, but it does not provide a hardware diagnosis. |
These distinctions keep the result meaningful. A physical keyboard event that never reaches the page, a key intercepted by iOS, and a physically failed key can all look similar if you judge only by an unlit QWERTY button.
Run a Physical-Keyboard Test on iPhone
- Confirm what you are testing. This workflow applies to an external physical keyboard connected to the iPhone, not the built-in software keyboard. Use a connection method supported by both the keyboard and the iPhone. Without an external keyboard, there are no physical key presses for this tester to report.
- Open and focus the tester. Open the tester page in the browser on your iPhone, then click or tab into the tool's on-screen QWERTY display so it becomes active and starts capturing key presses. The tool needs no installation, sign-up, or extension. If the page cannot take focus or your browser exposes no external-key events, stop rather than treating the result as a hardware verdict.
- Press each physical key one at a time. Work across the attached keyboard deliberately. The matching on-screen key should light up and stay marked as tested. A key held down should glow while it is held. Include letters, numbers, symbols, Enter, Space, Backspace, Tab, Escape, arrow keys, modifiers, and function keys that your browser reports.
- Read the last-key panel after each press. The panel reports the key, code, and keyCode for the most recent event. Check it when you need the exact browser value rather than relying only on the visual highlight. This is also useful when a button lights but the expected character does not appear.
- Check unlit keys and key combinations. Look for buttons that never lit after their corresponding physical keys were pressed. Those are suspects, not automatic proof of failure. Then hold several keys together to see which presses register and which disappear. That comparison can reveal rollover or ghosting symptoms in the browser's event stream.
- Reset before a fresh pass. Click Reset to clear every tested mark and the last-key readout. Use this after a second attempt, after cleaning beneath a troublesome key, or whenever you want to begin with an empty display.
Read the Key, Code, and KeyCode Values
The last-key panel is most useful when the three values are considered together. The key describes what a press produces, the code identifies its physical position, and the keyCode provides a legacy numeric value. Confusing these fields can make a working key appear faulty when the real issue is a layout or remapping difference.
| Reported field | Official meaning | Example | How to use it |
|---|---|---|---|
| key | The character or name produced by the key. | a, Enter, or ArrowUp | It can change with the active layout and held modifiers. |
| code | The fixed physical position of the key. | KeyA or Space | It stays consistent across language layouts, making it useful for identifying the same physical key. |
| keyCode | An older numeric identifier retained for compatibility. | Numeric value shown in the panel | Some software and games still rely on this value. |
If a key produces the wrong character but its code still points to the expected physical position, investigate the active layout or key remapping before blaming the hardware. If the same physical key does not register at all, the character value cannot help because the browser never received that press.
Distinguish Dead Keys, Sticky Keys, and Ghosting
Dead or unresponsive keys
A key that stays dark after a deliberate press is a suspect. First confirm that the on-screen QWERTY display still has focus. If it does, consider whether iOS or a global shortcut intercepted the key before the browser received it. Comparing the key in a plain text field can help separate an input-handling problem from a physical failure. A key that still fails under those checks may be dirty, disconnected, or physically dead.
Sticky or chattering keys
A sticky key can remain actively highlighted after you release it, beyond its ordinary tested mark. A chattering key can fire repeatedly from a single tap. Both patterns point toward a mechanical or switch problem that may need cleaning or repair. Reset the display before checking the key again so the previous session does not make the behavior harder to judge.
Ghosting and rollover symptoms
Hold two or more keys at once and watch which on-screen buttons illuminate. If one of the pressed keys disappears, the browser has not reported that combination as expected. This reveals a rollover or ghosting symptom without identifying its underlying cause: dropped input can involve keyboard hardware, iOS, or browser event handling. The tester provides the observed event behavior, not a numeric hardware rating.
Run a Confirmation Pass Before Troubleshooting
After the first pass, retest every dark or inconsistent key individually. Note the key, code, and keyCode shown in the last-key panel, then repeat the same physical press in a plain text field. Next, test the suspected key alone and in the combinations that failed. This separates a one-off missed press from a repeatable problem.
Use Reset to clear the display and begin the confirmation pass. Because Reset removes both the tested marks and the last-key readout, record any failures in your own notes before clearing them. Those notes can make a later troubleshooting, support, or warranty conversation more precise without claiming more than the browser actually reported.
Privacy and Keys That May Not Reach the Browser
All detection happens locally. The page listens for keyboard events directly in your browser and never records, stores, or transmits what you type. There is no keystroke logging and no upload, and closing or refreshing the page clears the session. Local processing protects the test data, but it does not remove the compatibility limitation: the browser still has to receive the key event for the on-screen display to react.
Some laptop Fn combinations, media keys, and certain lock keys are handled by the operating system or hardware before the browser sees them. Their absence from the display is therefore not automatically a dead-key finding. Keys that could otherwise scroll or navigate the page, including Space, Tab, Backspace, arrow keys, and function keys, are held in place only while the on-screen keyboard is focused. Keep that area focused during the pass, and click away or press Escape when you want to leave.
For a deeper look, see Keyboard Tester on Laptop: Dead, Sticky, Ghosting Keys.
For a deeper look, see Online Notepad on iPhone: Quick Notes That Save Locally.