Keyboard Typing Shortcuts Instead of Letters: How to Fix
You press S and nothing appears. You press it in a browser and the page tries to save. The keyboard is clearly alive — it is just treating every letter as a shortcut instead of as text.
Almost nobody reaches this state through hardware failure. A modifier key is being held down, and the machine believes it, so every letter you type arrives as a combination.
Find the key that is holding itself down
Take your hands off the keyboard completely. Then open the keyboard test and look at Held at once. With nothing pressed, that number should read zero.
If it reads one or two, something is down that you are not pressing. Ctrl, Alt, Cmd and Win are the usual culprits, and the board will show you which one. That single number turns a vague problem into a specific key.
The fix is often physical. Press and release the stuck modifier a few times firmly. A key that has been pressed and not returned — a crumb under the cap, a cable jostled at the wrong moment — frequently clears this way.
When the test says zero and it still happens
If nothing is held and letters still behave like commands, the modifier is stuck in software rather than in the switch. This happens after a shortcut that was interrupted: you held Ctrl, the window changed, and the release event went to a window that no longer existed. The system never heard the key come up.
Tapping each modifier once usually resolves it, because the release event finally arrives. Locking and unlocking the screen forces the same reset from a different direction.
The accessibility settings that cause this on purpose
Both Windows and macOS ship features that hold modifiers deliberately, so that people who cannot press two keys at once can still use shortcuts. Turned on by accident — and they are turned on by accident often, because pressing Shift five times in a row is a shortcut for enabling one of them — they produce exactly this symptom.
The names differ by platform and by version, so rather than quoting a menu path we have not verified on your build, search your system settings for the accessibility section covering keyboard input. What you are looking for is any option that keeps a modifier active after you let go.
Numbers instead of letters is a different fault
A related complaint is letters producing digits — you type J and get 1. That is not a modifier problem. Compact keyboards without a separate number pad overlay one onto the letter keys, and a lock key toggles which layer is active. The keyboard test will show the letter key registering correctly while your document shows a number, which is the signature of a layer problem rather than a hardware one.
What none of this covers
Everything above assumes the keys are sending signals. If the test screen shows nothing at all when you press — no color, no count — then the problem is upstream of any setting, and you are looking at a cable, a port, or a switch. That is a different diagnosis, and telling a dead switch from a dead board is where it starts.
The distinction is worth thirty seconds. Software problems and hardware problems present almost identically to the person typing, and only the test screen separates them.
Related Desk Armory note
A stuck modifier produces commands instead of letters; a dead key produces no event. If one key never appears in the browser, use Keyboard Key Not Working to split the switch from the computer.
How this note was made
Desk Armory used browser keyboard events to separate a modifier that remains logically active from a key that does not register. Accessibility and keyboard menu paths vary by operating-system version, so the article describes the state to check rather than claiming one permanent menu path.