Skip to content

Alert

<ns-alert>

Overview

Alert can be used to communicate error, info, success and warning messages in an accessible and visual way.

Examples

type="highlighter"

Guidance

Highlighter

Key

KeyField typeGuidelines
AIconThis is the icon inside the highlighter type. This is dictated by the state of Alert. The specification table has a list of options.
BHeadingThe recommended length is between 4 and 12 words, not exceeding 50 characters in total.
CContentA single, short paragraph works best. You are able to use inline text links within the paragraph if necessary. Don’t add additional headings within the paragraph and the copy length should not exceed more than two paragraphs of 3 lines each. Can contain bold copy <b>, inline links <a>, and a caveat at the end of the relevant paragraph if required <a href="#caveat">1</a>.
DAccentThis is to support the context of the messaging. This colour matches that of the icon.

Considerations

  • Be clear and concise

The message must be in plain English, and help the user out of the situation by providing an actionable link if possible.

Implementation

Placement

The ns-alert component can be used in the following components:

  • <div> wrapped in <ns-panel>
  • <ns-form>

Specification

Attributes

dismissible

Property
dismissible
Type
boolean

state

Property
state
Description
The state of the alert.
Type
error info success warning
Default
error

type

Property
type
Type
string
Default
standard

Slots

SlotPermitted tagsDescription
heading<h2> <h3> The heading of the alert.
Anonymous slot<p> <div> Anonymous slot for content.

Events

NameDescription
close-alertDispatched when the alert is closed.

Accessibility

The information contained in the alert should always be the most important information on the page. To ensure that screen reader users are informed about the importance of these messages the content is read aloud as soon as the alert type is used. This could be when the page loads or when it is dynamically added to a page.

If there are multiple alerts on a page they are read:

  • from top to bottom on page load
  • in the order they have been added to the page when dynamically added