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.

✨ This is an auto-generated AI summary of the ns-alert's documentation. It may not be accurate. ✨

Examples

Guidance

Highlighter

Labelled diagram of ns-alert

Key

KeyField typeGuidelines
AIconThe icon is dictated by the state.
BHeadingThe recommended length is between 4 and 12 words, not exceeding 50 characters in total.
CAnonymous slotA single, short paragraph works best. The text length should not exceed two paragraphs of 3 lines. Include emphasis with <strong>, inline links <a>, lists <ul> <ol>. Add a caveat link if required.
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:

Specification

Attributes

dismissible
Property
dismissible
Type
boolean
state
Property
state
Description
The contextual role of the alert message.
Type
string
Options
error info success warning
Default
error
type
Property
type
Description
The type of alert to use.
Type
string
Options
standard highlighter
Default
standard

Slots

SlotPermitted tagsDescription
heading<h2> <h3> The heading of the alert toned with its `state`. Heading level depends on its place in the semantics of the page.
Anonymous slot<p> <div> The anonymous slot for alert message.

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

Last updated: