Press ? right now.
That sheet built itself from the registry. Nothing on this page maintains a list of shortcuts, which is why the list cannot go stale.
Every key below is live on this page. So is the guard that stops them firing while you type.
What the registry decided
Press any key. NeoKeys reports the verdict it reached and the reason, which is the
same value the dispatcher acts on. Then click into the field and type: the verdict
changes to typing and nothing fires.
Press a key anywhere on the page.
Four mechanics
Three the kit owns, one it only checks. Each is live here.
Try to break it
Register a shortcut below. Reserved keys are refused, keys already taken are refused, and fleet conventions are allowed with a warning, because only a person can judge whether your E really means export.
Add it to a site
Three steps. The third is the only one with any thinking in it.
The fleet key map
Surveyed across all 65 projects before any key was reserved. The counts below are what the code actually does today, not what anyone remembered.
Why a bare key is safe on a page full of text
Five layers, ordered by how early they act. The first three are the kit's job, the fourth is the visitor's, and the fifth runs before a site is ever switched on.
Single-key shortcuts and WCAG 2.1.4
Success Criterion 2.1.4 is Level A. A single-character shortcut has to be switchable off, remappable, or active only on focus. NeoKeys does all three, and the controls live in the same sheet as the list.
One thing the compliance does not solve: screen readers in browse mode claim H for "next heading", so a reader using one never reaches the toggle. Any site that turns chrome hiding on should keep a visible control too.