Description

ONGOING

Tabs enable content organisation at a high level, such as switching between views, data sets, or functional aspects. Allowing user for dual screen support, and workspace customisation.

Types

Type	Usage (TBD)
Main Tabs	Use it as a tabbed navigation - Single row above their associated content
2nd Level Tabs	Single row above their associated content
Details Pane Tabs	Single row above their associated content in the details pane
Ribbon Tabs	TBD

Usage & Behavior

Guidelines

Present tabs as a single row above their associated content.
Tabs can be switched by clicking on a different tab.

Each tab label describes the content contained within it. Labels are concise and use no more than two words. 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 tab labels.

Labels

Each tab label describes its content and sets user expectations.
Tabs with related content should be grouped adjacent to each other
Labels are concise and use one to two words maximum.
Tab labels should succinctly describe the content within.
Icons are not permitted in tab labels.

Structure

The horizontal layout of the tab bar never changes. The tabs always appear side by side

The NavigationView pane can contain:

Navigation view top pane anatomy

Navigation items
Separators

Number of tabs

A maximum of four tabs may be displayed. This is to maintain an uncluttered UI and reduce cognitive load for users.

Order

Tab order should be consistent across an experience. Tabs with related content should be grouped adjacent to each other.

Implement the focus as follows:

By default, show the first tab as open. This is the initial setting provided by the control.
Note: Technically, you can also override the initial selection. However, this is not recommended.
Later on, you can show the tab last selected by the user.

Additional guidelines:

Do not display a loading indicator above the tab while the number for the item count is loading.
Handle empty tabs as follows:
- Hide tabs that do not contain any information, and do not allow the user to create content..
- Show empty tabs that allow users to create content, such as notes or attachments.
Only use the tab bars to navigate between tabs. Do not use any other navigation links. For example, do not let users click an item in tab A that takes them to tab B. This type of cross-navigation inside a container is confusing, and cannot be handled by the back navigation.