Skip to end of banner
Go to start of banner

Buttons

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 67 Next »

Description

ONGOING 

A component that allows the user to trigger a "flow defined single action" (e.g. Apply, Continue, Expand) in context to a container its located in (e.g. screen, form, wizard, popup, popover, etc...). 

Example for a table with a row of buttons from different types (icon, Icon + name, split) at the top

Types

Type

Image

Usage

Dialog buttons

Used for either main or secondary actions on the page/pane/dialog

Icon buttons

Used for toolbars and displays where words won’t comfortably fit alongside icons.

Split buttons

Used when there are several possible related actions, and one main action (e.g most frequently used).

Toggle buttons

Used to quickly switch between two possible (e.g. ON/OFF)

Ribbon buttons

Used in the ribbon pattern. see Ribbon button.

Usage & Behavior

General guidelines

Content

Button labels tell users what will happen when they click the button.

  • Use verbs that describe the action, such as Add or Delete. Use sentence-style capitalization. 

  • For Sets of Buttons, use specific labels, such as Save or Discard, instead of using OK and Cancel. This is particularly helpful when the user is confirming an action.

Responsiveness 

According to button type

Positioning

According to button type

States

According to button type

Interaction (general for all buttons)

  • When hovering, Mouse cursor change
    from pointer

      To Hand

     

  • Clicking (pressing and releasing the left mouse button) on the button target area,  will initiate its action

Validations and errors

Transitions

According to button type

Best practices

  • Do not use Buttons as navigational elements. Instead, use Links.

  • In most cases, do not use more than three words for button labels.

    • Choose a button text that is short and meaningful.

  • Avoid acronym as labels in buttons.

Accessibility compliance

Focus management

Set in the general guidelines described in /wiki/spaces/UX/pages/308969693

Screen reader support 

Set in the general guidelines described in  /wiki/spaces/UX/pages/308248620

Contrast & size compliance

Are taken into consideration and embedded in the specific visual design

Design

According to button type


Code




Related

  • No labels