VOCABULARY / ENTRY
Contextual Actions
contextual-actions
Actions offered on or next to a specific object, applying only to that object, that appear when the user selects, hovers, focuses, or long-presses it — commonly shown as a context menu, row-level action buttons, or a floating toolbar.
Recognizing it
- Action entry points appear on or right next to the target object, not in a global toolbar
- Triggers include selection, hover, focus, or long-press, with at least one that does not depend on mouse hover
- The same actions can be reached by keyboard or touch, not only by hovering with a mouse
Concept boundary
Context menus, row action buttons, and floating toolbars are presentation variants of the same concept, not separate patterns: the test is whether the actions apply only to the selected or pointed-at object and appear on selection, hover, focus, or long-press. It differs from inline edit, which switches to an editing control in place and changes the content itself, while contextual actions only expose action entry points that may navigate, open a confirmation, or trigger inline edit. It also differs from batch actions, which apply to a multi-selection — batch actions has no entry of its own yet and is mentioned here only to draw the line.
When to consider it
- There are many objects, and giving each one a permanent action button would crowd the interface
- The actions only apply to the currently selected or pointed-at object and don't need global visibility
- A visible trigger elsewhere already covers users who can't rely on hover
When to be cautious
- The action is high-frequency or essential, so hiding it behind hover or long-press alone would make it unreachable for touch and keyboard users
- The same action must apply to a multi-selected group of objects — that is batch actions, not a single object's contextual actions
- The content needs to be edited in place; hand that to inline edit rather than opening a menu first and a separate edit panel after
Tradeoff
Keeps the default interface simpler and places actions close to their object, but discoverability drops: hover-only actions are invisible to touch and keyboard users and need an additional reachable trigger.
Conditional rules · Editorial advice
Related entries
Contextual actions supply the action entry point; inline edit changes the content in place. The two can be chained, but the entry point is not the edit itself.
Direct manipulation covers continuous, spatial actions; contextual actions add discrete, clearly named actions such as delete or archive.
Contextual actions suit one-step, lightweight actions; once an action grows complex enough to need its own interface, a modal dialog fits better than cramming it into a menu item.
Sources and what they support
Contextual menus should be reserved for genuinely secondary actions and must not hide high-frequency or essential actions behind an extra click; the menu must be openable and navigable by keyboard and fully readable and operable by screen readers, not reachable by click or tap alone.
Retrieved: 2026-09-15 · Archived 2026-09-16A menu button is a button that, when activated, opens a menu; it needs aria-haspopup and aria-expanded, and supports Enter, Space, and arrow keys to open the menu while the button has focus — one keyboard-reachable way to trigger contextual actions.
Retrieved: 2026-09-15 · Archived 2026-09-16Extra content that appears on hover or focus (such as a submenu or non-modal popup) must be dismissible, must let the pointer move onto it without it disappearing, and must stay visible while the trigger condition holds or the content remains valid; native browser title tooltips are exempt.
Retrieved: 2026-09-15 · Archived 2026-09-16Definitions reference these sources. Digital specimens, selection advice, relationships, and recipes are editorial work and have not been validated through user research.
Type extensions and implementation notes
This entry has no working specimen yet; the illustration is editorial. A real product still needs to verify that hover actions have keyboard and touch equivalents, that hover content meets the dismissible/hoverable/persistent requirements, and that high-frequency or essential actions have an entry point independent of the contextual menu.
{
"states": [
"idle",
"hovered",
"focused",
"long-pressed",
"open",
"closed"
],
"a11y": [
"The trigger control has an accessible name and exposes aria-haspopup and aria-expanded",
"The menu or toolbar can be fully operated with Tab, arrow keys, and Enter, not only by hovering with a mouse",
"Content triggered by hover or focus is dismissible, hoverable, and stays visible"
],
"motion": "Appearance and dismissal can skip animation; show or hide instantly under reduced motion"
}Open the Agent JSON file for this entryThis file repeats every field of this entry verbatim and adds its sources, archive status, and editorial scope.