Molecule
Queue foot
Where the keyboard is taught. 45 instances across 45 screens: one under every queue.
Design principle 5 puts keyboard before mouse and principle 3 says the override is one key and it teaches. The foot of the queue is where the analyst who has been clicking for a week finds out she did not have to. It is the quietest strip on the screen and it is deliberately never a dialog: a modal that teaches shortcuts is a modal that gets dismissed.
Anatomy
dark, shipped
light, the pair
.qfoota wrapping mono row at 11px with a hairline above itkeythe keys, three of them, and since 2026-08-26 they are the atom rather than a second drawing of it. They werekbdelements with a control border and a fixed secondary ink; they arekbd class="key"now, taking the strip’s own colour throughcurrentColor
Variants
| Axis | Value | The rule |
|---|---|---|
| count | three or four hints | A count. Which shortcuts a screen advertises is a fact about the screen |
| emphasis | no values | Prohibited. It is the last thing on the screen and it must stay there. A loud keyboard strip is a strip that gets read once and resented afterwards |
| placement | no values | Always the foot of the list, never floating and never fixed. It is a footnote, and a footnote that follows you is an overlay |
The open row, named rather than folded. Same job, two forms: kbd here and key everywhere else. Step 2 did not rule on it and this file does not collapse it silently. It goes to the reconciliation as a control drawing the same thing past the system, and the key page carries the same note from the other side.
When to use it
Under the queue, once. It is the only place in the product that lists shortcuts inline; the full set is the keyboard map at node 0.5, one key away.
Where she meets it. In week one, and then never again on purpose. The measure of this component working is that an analyst stops reading it.
Rule and anti-rule
Do
The key and what it does, in the analyst’s words, in the place she is already looking when a list ends.
Do not
Not a button that opens a list. Design principle 2 puts the cheapest correct thing first: four hints in a strip cost nothing, and a button costs a tap to learn what a tap would have saved.
Limits
Rules of composition and context, which no anti-rule can carry: nothing else is the right component to take, and what is wrong is the count or the neighbour. Counted on the grey corpus at stage 09, and every one of them is a function in design/kit/checks/rules.mjs. Full table with sources on Architecture.
- R1. Not more than one
.btn--primaryper layer, and a foot does not compete with it. A second is allowed only as the viewport twin of the first, or in a modal layer over the screen.
States
It has none, and it is not interactive. Nothing in it is pressable: it is a picture of the keyboard, and the keyboard is the control.
dark, shipped
light, the pair
What it reads, and where it stands
| Role | Surface | Where on the component | Dark | Light |
|---|---|---|---|---|
--text-secondary | ink 4.5:1 | the hints and the keys | ||
--line-control | line 3:1 | the border on each key | ||
--line-separator | line, exempt | the hairline above the strip |