Keyboard shortcuts
Single-key shortcuts make the Desk fast, so they need an off switch, a dialog that lists them, and a visible control for each.
The Desk shortcuts
Press ? in the Desk to open the dialog. The list below is read from the same table the Desk uses, so it can't drift.
| Keys | What it does | The visible control |
|---|---|---|
| J | Next request | Click the next row in the queue |
| K | Previous request | Click the previous row in the queue |
| E | Resolve the open request | Resolve button above the conversation |
| N | Add an internal note | Internal note tab by the reply box |
| ? | Show this list | Shortcuts link in the queue sidebar |
- Key caps. KbKbd shows the shortcut inside the button or menu row it triggers.
- aria-keyshortcuts. Set on the control so assistive tech hears the key.
- Shortcuts dialog. Opened by ?; lists each key beside its on-screen control and carries the off switch. Escape closes it and returns focus.
- Profile switch. People can turn single-key shortcuts off. ? still opens the dialog.
When to use
- Add a single-key shortcut only for an action done many times a shift.
- Every shortcut also has a visible control, and every header action is in the command palette.
- No shortcut for a destructive action.
- Shortcuts never fire while typing in a field, and never with a modifier held.
Keyboard and screen readers
- Single-character shortcuts must be turnable off or remappable (WCAG 2.1.4); the profile switch does that.
- The dialog traps focus, closes on Escape and returns focus to what opened it.
- Each shortcut has a pointer-and-keyboard alternative, so nothing depends on remembering a key.
- Key caps use text, not images, and keep 4.5:1 contrast.