...
Buttons allow the user to perform a defined single action, such as navigating to a different view, choosing an option, or completing a task. These actions are always in context, relating to the container it's located in, such as a screen, form, wizard, popup, popover, etc..
 |
 |
Types
Type | Image | Usage |
 | Use for primary and secondary actions. | |
 | Use in areas where dialog buttons won’t comfortably fit, such as toolbars and tables. | |
 | Use when there are multiple related actions, with one primary action (e.g. the most frequently used). | |
 | Use to quickly switch between binary options, e.g. On/Off. | |
 | Use within the Ribbon /wiki/spaces/UserExp/pages/1390479038 component. |
Usage & Behavior
...
As per each individual button type.
For large button menus, up to 3 primary actions should be shown at top level. Additional, secondary buttons should be grouped within a menu icon button, shown to the right of the primary buttons.
...
Content
Button labels tell users what will happen when they click the button.
...
Do not use Buttons as navigational elements → use Links.
In most cases, do not use more than three words for a button label.
Choose Labels labels which are short and meaningful.
Avoid using acronyms as labels in buttons. Use language which the user will understand.
...
Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility.
Responsive design
Verint products should dynamically respond to the user’s screen size, platform, and orientation, supporting all devices down to the common tablet size (960px width).
For more information see the general Responsive Design guidelines.
Responsive guidelines
For button menus:
where the width of the container is reduced and the 3 primary buttons cannot all be shown, they should be moved into a hamburger menu along with the other secondary buttons.
the most important primary action, such as Save, should always remain visible.
Design
As per each individual button type.
...