Related Pages:

Description

Empty states are moments in a user’s experience where there is no content to display.

Types

LUX has specific designs for 4 empty state types. In full page empty state instances, the appropriate corresponding illustration should be used. In instances where an empty state must be shown within a widget, the corresponding icon should be used in place of the relevant illustration.

Type	Usage	Illustration	Full page	Widget	Icon?
No results found	Use when a user’s search criteria returns no results.
No <entities> defined	Use when no entities, such as forms, have been added/defined.
You’re all caught up	Use when a user has no new notifications to review.
Waiting	When an action is in progress.

Usage & Behaviour

General guidelines

<<use the sub-section below for description, use only those which fit the component >>

Structure

An empty state may consist of:

An illustration - a visual that relates to the current state.
Subtext - a brief, informative message to communicate the state the application is in to the user.
A call-to-action button - a contextual action/UI element relevant to the user’s task.
A text link - a contextual action/UI element relevant to the user’s task.

Placement and Positioning

Empty states should be centered vertically and horizontally on full pages and in instances where the empty state must be shown in a container or pane.
In instances where empty states must be displayed inside a container or pane, the empty state should be centered vertically and horizontally.
Empty states should be positioned contextually to the relevant content.

Content

<<Including labels, microcopy, number of items, order of items etc… See example: Buttons content >>

Validations and Errors

<<Show images for Errors and warnings. See example: Radio button validations and errors>>

Best Practices

Use:

<…>
<…>

Don’t use

<…>
<…>

General

<…>

Accessibility Compliance

Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility

Focus management

	Text field	Drop-down
	<<Images with Focus>>	<<Images with Focus>>
Tab	<<Description >>
Space
Enter
Esc
Arrows

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, including recommended breakpoints, see the general Responsive Design guidelines.

Responsive Guidelines

< Guidelines for the responsive behavior of the pattern or component, down to tablet (960px) width >

Design

Zeplin link	Screen thumbnail
<<Short Zeplin link. You Use this >>	<<Screen with 200 width>>

Code

<<a box containing the code - when there is no code to present use the Coming Soon GIF>>

Copy of Empty States