Skip to end of banner
Go to start of banner

Copy of Empty States

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

Related Pages: << Links to related pages, if relevant >>

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 consists of:

are comprised of the relevant illustration and the corresponding subtext related to that state.

<<Describe the different parts that structure the component. See example: Numeric stepper structure >>

Placement and Positioning

<<Where should the component be located on the screen. See example: Pagination placement and positioning>>

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

<Whenever a recommendation (not a must) is provided>>

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

<See examples in https://kanasoftware.jira.com/wiki/spaces/UserExp/pages/1924924198/Copy+of+Combo+Box+Temporary#Focus-management , https://kanasoftware.jira.com/wiki/spaces/UserExp/pages/1924759856/Copy+of+Numeric+Stepper+Temporary#Focus-management >>

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>>

  • No labels