> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# KBD

> KBD, known as keyboard shortcuts, provide users with quick access to frequently used actions or commands, improving efficiency and streamlining workflows. They are typically represented by key combinations (e.g., Ctrl + C) and can appear in contexts like Menus, Tooltips, or documentation.

## KBD

<Badge color="blue">v1.0.0</Badge> | [View in Storybook](https://master--695bb4b1b8041ae09768950a.chromatic.com/?path=/docs/primitives-kbd--docs)

### When to use

* To accelerate common tasks for power users.
* When an action is frequently repeated and benefits from faster execution.
* To complement menu items and Buttons by offering an alternative input method.

### When to use something else

* For critical actions without clear undo (e.g., delete all), unless safeguarded by confirmation—prefer explicit [Button](/aura-design-system/primitives/button) or [Dialog](/aura-design-system/primitives/dialog) flows.
* As the only means of accessing an action; always provide a visible control ([Button](/aura-design-system/primitives/button), [Menu](/aura-design-system/primitives/menu) item).
* Where discoverability matters and users won’t learn shortcuts.
* When key chords would conflict with the browser, OS, or assistive tech.

### Dos and don'ts

* Do use letters for meaning. Letters make shortcuts more memorable, as they can convey meaning (e.g., C for Comments).
* Do always use modifiers (e.g., ⌘, Ctrl) with letters to prevent accidental triggers and to avoid overriding focus states.
* Do show shortcuts next to the action they trigger, e.g., inside Menus, Dialogs, or Tooltips.
* Do be selective: Not every action needs a shortcut. Consider how often users perform the action and where its trigger point is in the UI.
* Don't use two-letter shortcuts: Two-letter shortcuts can conflict with single-letter ones.
* Don’t override native Shortcuts: Respect browser and OS defaults to avoid confusion and conflicts.
* Don't assign shortcuts to critical actions (like "Delete all") without an undo or confirmation option.

### Behavior

* Decorative display of key chords next to actions; implementing code must register the same shortcuts they surface in UI.
* Modifiers reduce accidental activation; single-letter chords without modifiers are risky in text fields.

### Often used with

* [Menu](/aura-design-system/primitives/menu) item labels, [Button](/aura-design-system/primitives/button) or [Tooltip](/aura-design-system/primitives/tooltip) hints, command palette ([Command](/aura-design-system/primitives/command)) results, in-app docs.