Alerts
Search the component library

Alerts

v2.0.0-beta.2
Download UI Kit v1.9.0

Presents important feedback or information to users either in response to their actions or upon page load.

Download UI Kit v1.9.0

Usage Guidelines

Simple confirmation acknowledgements that don’t require additional detail should just use a confirmation button. If an error occurs or additional information is needed to clarify then the appropriate alert style may be dynamically presented.

Features

  • Modes for page load and dynamic presentation
  • Animated presentation
  • Error, information, and confirmation styles

Popover alerts (Static)

When a message is displayed upon page load, for example if there was an error confirming an email address, the alert should appear statistically in the upper left corner of the page or if on a mobile device the message will appear in the center of the mobile devices screen. The location will make it noticeable even when the user screen is magnified.

This message can simply be closed by clicking on the close button or it will auto close the window upon time out.

The message should appear in the upper corner as part of the normal page load.

At responsive sizes the alert occupies the top part of the viewport.

Responsive popover alert.

Popover alerts (Dynamic Presentation)

Alerts can also appear dynamically in response to user actions like submitting a form, choosing an option, or completing an assignment. In this case the alert will animate down from the top.

The animation for showing/dismissing a dynamic alert.

Content (task) level alerts

The alert that applies to a specific task or section content will be displayed above or below where the action occurred.

The example of message appear below the content area.

Example of responsive version content level alert.

Alert Types

Warning
  • Use when an error occurred that cannot be resolve on the user end.
  • Use when an issue that may or may not cause problems for the users, but the user should know about.
  • Example: System alert
Error
  • Use to let user know that something has gone wrong and it needs to be resolved to complete the task. IT can also provide suggestions on how to proceed.
  • Use to communicate an unsuccessful action
  • Example: Form Error, login error, search error.
Success
  • Use to tell user that a task has been completed successfully.
  • Use to let user know that everything is working property.
  • Example: Submitting a form, completing a quiz
  • The success alert can be closed to save screen estate.
Information
  • Use to inform the user about something relevant: to share tips or suggestions.
  • Use to let user know that everything is working property.
  • Example: Information about the specific content
  • The information alert can be closed to save screen estate.

Redlines

Dimensions
  • Color bar is 3px high
  • Horizontal and bottom padding is 28px (desktop)
Colors
Typography
“X” icons
Alert/warning icons
Animation
  • Drop in uses an ease-in-out easing curve with a duration of 300ms
  • Slide out uses an ease-in easing curve with a duration of 200ms
Focus Behavior
  • Most alerts can just be announced by using ARIA alert roles and don’t need special focus treatment
  • If an alert is particularly important, focus should be moved to the first element of the alert (and restored to it’s original position upon dismissal)
  • Statically presented alerts should just be read and focused in the normal flow of the document

Popover alerts

Content(task) level alert

Changelog

2.0.0-beta.2

  • UPDATED: Animation video uses latest copy

2.0.0-beta.1

  • CHANGED: New visual design. adding more alert types

1.0.0-beta.5

  • CHANGED: Uses basic CSS easing curves, rather than springs.

1.0.0-beta.4

  • FIXED: Accessibility verbiage is now more accurate
  • FIXED: Spacing verbiage, other typos

1.0.0-beta.3

  • ADDED: Positioning details to redlines
  • UPDATED: Keyboard and focus redlines.

1.0.0-beta.2

  • ADDED: Success style, redlines, a11y checklist

1.0.0-beta.1

Initial version