...
The header bar should expand/collapse with a transition effect.
No item selected
By default, the primary 1st level and 2nd level menu items should be selected when landing. However, in some instances there may be limitations which require a ‘No item selected’ state. In this case:
no blue selection lines or second level navigation are shown in the Verintop menu.
an animated graphic will be shown in the main workspace, explaining that the user must select a menu item.
...
On narrower screens, the message ‘Select a destination’ will be shown instead of the selected menu item, using a hint text colour.
See the Responsive Design section below for more information.
...
Best Practices
General
Truncation should be avoided, where possible, by using short labels.
Number of items for both 1st and 2nd levels should not exceed 8 items.
...
Keyboard | Trigger area | Menu |
|---|---|---|
Tab | Navigates to the next component. | N/A |
Shift + Tab | Navigates to the previous component. | N/A |
Space | Opens the menu and moves focus to the 1st item |
|
Enter | Opens the menu. |
|
Esc | N/A | Closes the menu without updating the selection. Returns focus to the Trigger area. |
Arrows | N/A | Unless otherwise specified are N/A
|
Responsive Design
For details on responsive design, see the main VerinTop pageVerint products should support all devices down to the common tablet size (960px width). For general guidelines, see Fundamentals - Responsive design.
As the screen width changes, the VerinTop should respond based on the number and length of menu items in both 1st and 2nd level navigation.
The space between menu items should not be adjusted at any width.
Each menu item will have the same padding either side of the label. The selection highlight should extend across this padding.
1st and 2nd level menu items will have an additional consistent spacing between them.
Wide screens
...
Where the screen size is wide enough to comfortably show everything contained within the VerinTop:
All content should be shown on one line, without wrapping. This includes:
1st level menu items, and
the application selector. This area may be expanded if the application name is long, and normally wraps onto 2 lines.
Elements aligned to the left- and right-hand sides (Product Area and User Profile) will remain there.
Narrow screens
Where 2nd level navigation does not fit within the screen width a More… option should be added on the right-hand side.
Clicking More… will open a drop-down menu containing the remaining menu items.
The same hover and selected states from the main menu should be used for menu items in the drop-down.
When an item has been selected from the drop-down, the blue underline should be added to the More… button.
...
Where 1st level navigation does not fit within the screen width, even after line wrapping:
The entire menu should be replaced by a menu icon button ⋮.
When the icon button is clicked, a drop-down menu will open.
1st level menu items will be shown on the left.
When a 1st level menu item is hovered over or clicked, the related 2nd level menu items will be shown on the right.
When a 2nd level menu item is selected:
the menu will close.
the new page will be shown in the workspace.
The current selection should be shown at both levels with a blue check mark.
When the menu is first opened, the currently-selected 1st level and 2nd level menu items should be shown by default.
A hover state should be shown for all menu items on hover (unless using a touch device).
Where possible, the selected menu item will be shown next to the menu icon button in the header bar. This should include both 1st and 2nd levels, separated by a >.
Where no menu item is currently selected, the message ‘Select a destination’ will be shown instead. See No item selected for more information.
Current selection | Hover |
|---|---|
 |  |
For more information about responsive design for mobile, please contact the UX team.
Design
Zeplin link | Screen thumbnail |
|---|---|
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 | |
 |
...