Keyboard

How this is generated

Source: the <KeyboardTable> block on every component page, which is the same block the component page renders rather than a separate list. Script: scripts/build-reference.mts. Command: pnpm run generate.

Aggregating rather than re-authoring is the whole point. A separate global keyboard list is a document that is correct on the day it is written and wrong within two releases, because the person changing a component's focus order does not know it exists. Here, a key that is not documented on its component page cannot appear on this page, and a component page without a keyboard table fails the build.

Four columns. Component and part say where you must be focused. Key is written the way a keyboard prints it, so Enter, Esc, Shift Tab. Action describes the outcome, not the implementation. Notes carries the exceptions: what changes in a right-to-left layout, what a screen reader's browse mode intercepts, what differs on iOS where an external keyboard is attached.

What is deliberately excluded. Browser and operating-system defaults are not listed, because Tab moving focus forward is not a feature of a component. The global focus contract, focus-visible behaviour and the skip-link rules live in Keyboard and focus, which is doctrine and belongs there rather than in a table.

This site's own shortcuts are not part of the system either; the search dialog opens with Ctrl K and that is a property of the documentation, not of opsinjs.

This script does not parse the <KeyboardTable> blocks yet, so nothing is aggregated here - not because no component documents its keys. Every component page carries its own table, and that is where the contract is readable today. The global contract every component must meet is in Accessibility under Keyboard and focus.