keyboard

A keyboard-summoned overlay whose single search box finds and runs any command or destination in an application by name.

A key drawn as a small keycap in running text or a menu, so a shortcut reads as something you press rather than something you say.

The panel opened by pressing question mark that lists every shortcut in the application, grouped by area.

A nested list where branches expand and collapse in place, navigated with arrow keys as a single tab stop.

A single letter, usually shown underlined, that jumps straight to a menu or control once the access modifier is held.

A shortcut whose keys are held down together like a chord, in contrast to one typed as a sequence of separate presses.

A held key firing repeatedly after an initial delay, which is how arrow keys scroll and backspace deletes more than one character.

A shortcut typed as an ordered run of presses, where the first key opens a mode and the next chooses within it.

A key or key combination that runs a command directly, giving practised users a path that skips the menus and the pointer entirely.

A key held to change what another input means, so the same click or keystroke can copy instead of move, or add instead of replace.

Moving or changing a value by one small fixed step with an arrow key, with a modifier switching to a larger step.

A temporary mode held open by the user, such as a key kept down, so it cannot be forgotten and ends the moment the hold ends.

Choosing a contiguous run of items by marking one end and holding Shift while marking the other, selecting everything between them.

A focus technique where only one item in a group is in the tab order and arrow keys move that position, so Tab enters and leaves the whole group once.

A widget where moving focus also selects, so arrowing through tabs or a listbox changes the selection immediately rather than on a second press.

A focus technique where DOM focus stays on a container or input and aria-activedescendant names which child is active, used when focus must not move.

The screen reader mode that intercepts keystrokes for reading and navigation, as opposed to focus or forms mode where keys reach the page.

The rule that decides which element to use: a link goes somewhere, a button does something, and the choice sets the keyboard, the cursor, and the announced role.

Single letter shortcuts that fire without a modifier, which must be switchable off or remappable because speech input and screen readers trigger them by accident.

A second, non-dragging route to anything a drag can do, such as arrow keys or a move-to menu on a sortable list.

The size and contrast a focus indicator must reach to count as visible: enough area around the control, enough change against both the control and its background.

A shadow root option that forwards focus from the host into the first focusable element inside it, so clicking the padding of a custom element does not leave focus nowhere.

Deliberately moving keyboard focus after a state change so the reader lands on the new content instead of at the top of the document.

The requirement that a focused control is not completely hidden by sticky headers, footers, cookie bars, or chat widgets when it receives focus.

The sequence keyboard focus follows through a page, which should match reading order instead of source quirks or positive tabindex values.

The visible outline drawn around the element that currently holds keyboard focus, showing where the next keypress will land.

A constraint that keeps keyboard focus cycling inside one region until that region is dismissed.

A focus style shown only when focus arrived by keyboard or another non-pointer route, so a mouse click does not leave a ring behind.

A control styled as unavailable but left in the tab order with aria-disabled, so a reader can find it and learn why it is off.

Giving a scrollable box its own tab stop so a keyboard user can scroll it, which matters whenever the content inside holds no focusable element of its own.

An element hidden from assistive technology that is still in the tab sequence, so keyboard focus lands on something a screen reader refuses to describe.

A state that removes a subtree from focus order, hit testing, and the accessibility tree at once, used to seal the background behind a dialog.

Where focus lands when a view, dialog, or page first appears, chosen deliberately rather than left on the body or dumped on the first close button.

A place keyboard focus can enter but not leave by keyboard alone, stranding anyone who is not using a pointer.

Using tabindex values above zero to force an order, which yanks those elements to the front of the whole page sequence and is almost always a bug.

A CSS property that repoints reading and tab order at the visual arrangement of a flex or grid container, instead of leaving both stuck in source order.

The order content is exposed in the DOM, which drives both speech output and tab order, and which visual reordering can silently contradict.

A link at the very start of a page, revealed on focus, that jumps past repeated navigation to the main content.

Moving focus by direction rather than by sequence, so arrow keys, a D-pad, or a TV remote jump to the nearest control up, down, left, or right.

One position in the tab sequence: a place the Tab key can reach, counted once even when the widget it belongs to holds many focusable parts.

Reachable by the Tab key, as opposed to merely focusable: an element with tabindex of -1 can take focus from script but never from Tab.