Informational (Non-Error) Alerts
Last updated: October 8, 2015 at 15:12 pm

These alerts can range from graphic badges to blocks of text informing your users of important information or events that can impact their experience.


Visual example of the element:


What problem does this element or pattern solve?
Not every user alert on your site needs to communicate an error. There are many instances where you will need to inform your user of anything from remaining battery life to urgency messages such as “Only 2 left at this price.”
It applies to these platforms:

Desktop Web, Tablet Web, Smartphone Web, Desktop App, Tablet App, Smartphone App

An example of this element or pattern in production:


Detailed specifications

Specifications To Consider

  • Define the various alert message types that you will display. Will you include sales or promotional messages in this section or within your content area? Or will all your alerts be limited to non-promotional events such as system status notifications?
  • What are the rules that govern the display of non-error alerts? If so, you should define the rules about when and where it can appear—otherwise you run the risk of overzealous product managers placing such messages everywhere.
  • In most instances, different message types should adopt different visual styling. Include those options here and provide examples. Do not forget links to iconography or images, legal content, nor other assets that may be required.


Location of assets to build this element or pattern
Location of UX or visual design assets
Location of development code repository


Additional details
Information on research, user testing, or usability reports:

Not Applicable (Remember: no field should be blank!)

This element or pattern may also be known as:
contextual messages, contexual alerts, urgent messages, temporary alerts, event notification, inline notifications, notice, fyi, info
Related elements within this Style Framework:

Not Applicable (Remember: no field should be blank!)



Owners and governance
UX or design 0wner
John Designowner
Email: design.owner@yourcompany.com
Business or marketing owner
Mary Businessowner
Email: business.owner@yourcompany.com
Development owner
Mike Devowner
Email: development.owner@yourcompany.com


Other information
Please include any other relevant information about this element or pattern:
Not Applicable (Remember: no field should be blank!)


Comments & Questions

Leave a Reply