Status | ||||
---|---|---|---|---|
|
...
Tabs enable content organization at a high level, such as switching between views, data sets, or functional aspects. Allowing user for dual-screen support, and workspace customization.
...
Usage & Behavior
Tabs organize and allow navigation between groups of content that are related and at the same level of the hierarchy.
General guidelines
...
Structure
The horizontal layout of the tab bar never changes. The tabs always appear side by side
Structure Elements
Container
Display a navigation text element arranged together with the active inactive highlighted
Tab item
Describes its content and sets user expectations
Each tab label describes the content contained within it
one to two words maximum
Icons are not permitted as tab labels
Active tab
To differentiate an active tab from an inactive tab, apply a 3 px underline and color change to the active tab’s highlighted.
...
States (TBD - not final design)
...
Main tabs
...
2nd level tabs
...
Details pane tabs
...
Ribbon tabs
...
State | Image | Comment |
---|---|---|
Regular | ||
Hover | ||
Active | ||
Selected | ||
Other focused | ||
Other focused hover | ||
Other focused active | ||
Selected focused |
Special States (TBD - not final design)
...
You can click on the entire label
Tabs can be switched by clicking on a different tab
There's always one tab open
Only 1 content can be viewed at a time when clicking on another tab the display will change for the selected tab
Hovering over a tab will show a tooltip with the full ?????????????? name of the section header
Validations and errors
State | Image | Comment |
---|---|---|
Tab item error | ||
Tab item warning |
Best practices
Keep in mind that at mobile widths and during translation, the character length of a label will impact the experience. Do not use icons in the tab label
A maximum of four tabs may be displayed. This is to maintain an uncluttered UI and reduce cognitive load for users.
Use clear labels
Tab order should be consistent across an experience. Tabs with related content should be grouped adjacent to each other.
Future Version (TBD)
Accessibility compliance
Each component should be A11y complied, please follow the 3 guidelines linked below. At the very least we should document that each component is in compliance with each of the 3
Focus management
We already set a general guidelines described in Keyboard & Focus Management Guidelines
Screen reader support
Make sure the components support screen reader for content or behavior where needed - see Screen Reader Guidelines
Contrast & size compliance
Design
Zeplin link | Screen thumbnail |
---|---|
Main Tabs | |
2nd Level Tabs | |
Details Pane Tabs | |
Ribbon Tabs - Expand |
Code
...
TBD
Current appearances in our products
...
Maximum tab number - vertical and horizontal
Scroll tab - out of the windowTab + Filter - how it works together
Align tab solutioan between mobile and desktop (card / line)
Tab title - text / icon / icon and title
Missing connection between the current tab to the content area in horizontal
Decide about maximum letter on title
...