Button bar

It is often necessary to provide users with page level actions. These actions should be contain in a button bar as described in this guideline.

For solutions not described in this article, please refer to other related patterns or contact the Commerce UX Design team.

When to Use

When Not to Use

Rules

General Rules

Location

Button Bar Position in Page

Button Bar Position in Slide-in Panel

Page Level Button Order and Priority - General Rules

Ordering of Button Bar

Page level buttons can be logically grouped as follows:

Groups can contain multiple CTAs but only one primary CTA. Groups should follow the below order:

Ordering by Importance

There should never be more than one primary page level CTA on the same page. Page level CTAs should assume an ascending order of importance from left to right wherever possible, i.e. least important buttons followed by most important.

Style

All buttons should be right aligned. The button bar is spread across 12 columns and should be fluid.

Recommendation

  1. It is recommended that all buttons in button bar should only be in one line. Because the button bar is in fluid grid, it is possible for the buttons to be wrap around to the next line.
  2. If you have multiple page-level buttons. We recommend using the split button rather having too many buttons that will clutter the page.

Sticky button bar

To ensure page level actions are always visible, The button bar should stick to the top of a browser as the user scrolls and the top of button bar hits the top of browser.

Initial State

After user scrolls, the button bar sticks to the browser

Accessibility

Buttons should make use of CSS and HTML so that button text is never dependent on a graphic asset.