Skip to end of banner
Go to start of banner

Toolbar

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 32 Next »

Description

A toolbar is a grouped set of controls used to apply actions to related content.

Usage & Behavior

The toolbar may be used in conjunction with 3 components:

Type

Image

Data Table

List

Chart

General guidelines

Structure

  • The toolbar is shown as a horizontal, single row.

  • It may contain one or more items.

Placement and Positioning

  • The toolbar is located on top of a data area (e.g. the data table).

  • It should use the maximum width of the data area.

  • Where relevant, the toolbar should be divided into two areas:

    • Action controls - any action that impact the data (e.g. delete), left-aligned.

    • View controls - options impacting the view of the data (e.g. print, search, change view mode etc.)

    • In case all items are view controls, they will be left-aligned.

Content

  • A toolbar may include:

    • a variety of components, such as Action Menus, Buttons, and Search.

    • information such as counters and statuses. (See data table image above).

  • Dialog Buttons cannot be used within a toolbar.

  • Optionally, a Icon Button can be used to group multiple actions into an Action Menu (see chart image above).

  • If actions can be grouped, they should be separated by a vertical divider (for example, table-level actions | row-level actions).

Internal Logic

  • Controls in the toolbar can be applied to either the entire data set or to one or more items within the content (depending on what has been selected).

  • Controls in the toolbar can be enabled/disabled in response to data selection (e.g. Delete can be disabled if no data is selected).

States

The toolbar itself has no states. Each control on the toolbar will behave according to its own states.

Validations and errors

The toolbar itself has no validations or errors. Each control on the toolbar may have its own validations.

Best practices

Use:

  • if the user can perform actions or change the view of the related content.

  • if the related content allows multi selection.

Don’t use:

  • In case of a single selection data table, if all actions can be performed on a row-level.

  • If a ribbon pattern is used.

General:

  • Where possible, consider using only Icon Buttons, with a corresponding Tooltip.

  • Icon buttons with text should be used to emphasize one or two specific actions.

Accessibility Compliance

Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility.

Design

Zeplin link

Screen thumbnail

https://zpl.io/aB4Eedp

Code

  • No labels