Action bars are used for single and bulk selection patterns, when a user needs to perform actions on either a single or multiple items at the same time.
An action bar is not emphasized by default. This is best used for when it needs to blend in with the rest of the UI, directing a user’s focus to elsewhere in a view.
The emphasized action bar has a blue background that adds visual emphasis on the actions and selection. Use this for when the bar should call attention (e.g., floating in a table).
From the design point of view, each component has a number of options. These options and their names are platform agnostic, and each implementation should adapt these to fit into their framework.
yes / no
An action bar has a close button to quickly and easily deselect all items and close.
Users need to be able to readily view how many items will be affected by taking an action. Include a count of how many items are selected.
Action bars always include an action group. Show the most common actions that are contextual to your use case, and limit these to five or less.
At larger screen or section sizes, use an action group that shows a label and icon. For smaller screen or section sizes, use an icon-only action group. Place any overflow actions into a menu at the end of the bar.
When a user selects items with relevant actions, an action bar appears at the bottom of the viewport. The bar should have margins of 12 pixels on desktop and 16 pixels on mobile on the sides and bottom.
Include a safe zone of at least 24 pixels between the item counter and the action group.
Action bars slide and fade in from the bottom of the page or section. They remain or "stick" there until a user either deselects the items or navigates away.
An action bar appears when items in a list or grid view are selected, and it remains in place until items are deselected or a user navigates away. Action bars can not be moved or dragged.
Action bars appear on top of content. Allow space for a user to still be able to view the content underneath, especially if they're taking actions on a table or a list of items and need to be able to scroll.
Instead of quick actions, use an action bar for both single and bulk selection patterns. An action bar is useful for when a user needs to perform actions on either a single or multiple items at the same time. It can be used on either a grid view or a table view.
Don’t use quick actions — a deprecated component — because it presents conflicting nested actions (for example, a whole asset card could open a detailed view). This makes targeting specific actions very difficult, especially on smaller screens or with the keyboard.
|Tab||Move from component to component, from start to end, within the action bar.|
|Left or Right Arrow||Move within component groups from left to right (e.g., first action button to second action button within an action group).|
|Apr 06, 2022||4.0.0|
|Jan 27, 2022||3.0.0|
|Nov 22, 2021||2.0.0|
|Jan 08, 2021||1.0.1|
|Feb 27, 2020||1.0.0|
Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).
Works properly across all four color themes (lightest, light, dark, darkest).
Includes a desktop scale (UWP, macOS, web desktop) and a mobile scale (iOS, Android, web mobile).
Color is not used as the only visual means of conveying information (WCAG 2.0 1.4.1).
Text has a contrast ratio of at least 4.5:1 for small text and at least 3:1 for large text (WCAG 2.0 1.4.3).
Visual information required to identify components and states (except inactive components) has a contrast ratio of at least 3:1 (WCAG 2.1 1.4.11).
UI language and information design considerations have been incorporated into component design.
Includes relevant options (variant, style, size, orientation, optional iconography, decorations, selection, error state, etc.)
Includes guidelines for keyboard focus, layout (wrapping, truncation, overflow), animation, interactions, etc.
Includes a list of dos and don'ts that highlight best practices and common mistakes.
Includes content standards or usage guidelines for how to write or format in-product content for the component.
Works properly across various locales and includes guidelines for bi-directionality (RTL).
Follows WCAG 2.0 standards for keyboard accessibility guidelines and includes a description of the keyboard interactions.
All design attributes (color, typography, layout, animation, etc.) are available as design tokens.
Includes a downloadable XD file that shows multiple options, states, color themes, and platform scales.
Includes a downloadable XD file, generated by code using design tokens defined in Spectrum DNA, and shows multiple options, states, color themes, and platform scales.
Component is included in the Spectrum for Adobe XD plugin.