Alert

Alert is deprecated. It was removed from the Figma library and no longer has a design source, so it will not be developed further.

Unusually for a deprecation, there is nowhere to send you: nothing else in the system covers a contextual, severity-coded page message. Don’t build new surfaces on Alert. Existing usages can stay — the CSS still ships, and it won’t be removed until a replacement is named.

Scheduled maintenance

Online booking is unavailable this Sunday between 02:00 and 06:00 CET.

Contact a dealer

Maintained by Platform

Deprecated — migrate away

CSS Accessibility

<div class="tng-alert">
  <div class="tng-alert-header">
    <i aria-hidden="true" class="tng-icon icon-info"></i>
    <h4 class="tng-alert-title">Alert Title</h4>
    <button class="tng-icon-button is-ghost" aria-label="Close">
      <i class="tng-icon icon-close" aria-hidden="true"></i>
    </button>
  </div>
  <div class="tng-alert-body">
    <p class="tng-text-body">…</p>
  </div>
  <div class="tng-alert-footer">
    <a class="tng-link" href="#">Link 1</a>
    <a class="tng-link" href="#">Link 2</a>
  </div>
</div>

Alert Title

Ea reprehenderit qui mollit. Magna quis veniam ea est deserunt labore eu ullamco ea ex cupidatat ullamco exercitation esse. Anim amet mollit qui mollit reprehenderit nisi commodo occaecat. Laboris esse ex amet consequat proident officia id velit cupidatat nostrud deserunt ipsum proident. Enim exercitation qui sunt.

Link 1 Link 2

Variants

<div class="tng-alert is-error">
  <p class="tng-text-body">…</p>
</div>

Sit sit occaecat minim aute tempor veniam Lorem non et anim. Id in quis eiusmod ea velit sit qui aute cillum aliquip ad aliqua ex. Proident irure proident labore occaecat ex velit Lorem.

<div class="tng-alert is-info">
  <p class="tng-text-body">…</p>
</div>

Sit sit occaecat minim aute tempor veniam Lorem non et anim. Id in quis eiusmod ea velit sit qui aute cillum aliquip ad aliqua ex. Proident irure proident labore occaecat ex velit Lorem.

<div class="tng-alert is-success">
  <p class="tng-text-body">…</p>
</div>

Sit sit occaecat minim aute tempor veniam Lorem non et anim. Id in quis eiusmod ea velit sit qui aute cillum aliquip ad aliqua ex. Proident irure proident labore occaecat ex velit Lorem.

<div class="tng-alert is-warning">
  <p class="tng-text-body">…</p>
</div>

Sit sit occaecat minim aute tempor veniam Lorem non et anim. Id in quis eiusmod ea velit sit qui aute cillum aliquip ad aliqua ex. Proident irure proident labore occaecat ex velit Lorem.

The alert follows the WAI-ARIA Alert pattern — a live region that announces an important message the moment it appears — and meets WCAG 2.1 AA. Match the live-region politeness to the urgency: an assertive live region interrupts the screen reader for errors and warnings, while a polite one waits for a pause for informational and success messages. An accessible alert makes its severity clear without relying on colour, announces itself to assistive technology as soon as it renders, and — when it can be dismissed — exposes a keyboard-operable close control with an accessible name.

For designers

Alert text, icons, and every variant must keep accessible contrast on each supported surface. Source: WCAG 1.4.3 Contrast (Minimum).
Severity must never ride on colour alone — the difference between error, warning, info, and success has to be carried by the icon and the wording too, not just the tint. Source: WCAG 1.4.1 Use of Color.
The dismiss button’s focus style must stay visible, meet contrast on every supported surface, and be clearly distinguishable from hover. Source: WCAG 2.4.7 Focus Visible.
Use semantic colour tokens (e.g. foreground/neutral/default) rather than fixed values, so the alert adapts correctly across themes and surfaces.

For developers

Render the alert as a live region so assistive technology announces it as soon as it appears — assertive for errors and warnings that must interrupt, polite for informational and success messages that can wait; the Labelling elements section gives the exact roles. Make sure the region is in the DOM before the message lands (or render the whole alert on demand) so the new content is announced rather than missed. Because the variant icon is decorative, let the title and body text carry the severity so it still reaches screen-reader users. When the variant is dismissible, the header holds a single icon-only close button — an ordinary tab stop that needs no custom focus scripting; after the user dismisses an alert, move focus to somewhere sensible, such as the control that opened it or the next piece of content, so focus is never stranded on a removed element. The per-element roles, names, and states are in the Labelling elements section below.

Keyboard interaction

Key	Action
`Tab` / `Shift + Tab`	Move focus to / away from the close button
`Enter` / `Space`	Dismiss the alert

The close button must present a large enough target for touch — meeting at least the 24 px WCAG AA minimum, with comfortable spacing from the alert’s edges. Source: WCAG 2.5.8 Target Size (Minimum).

Labelling elements

Give every element the role, name, and state assistive technology needs.

Alert region

role="alert" (assertive, implies aria-live="assertive") for errors and warnings, or role="status" (polite, implies aria-live="polite") for informational and success messages. The region takes its accessible name from the message it wraps — the title and body text — so keep that text self-describing; add aria-label only when there is no visible text to name it. The decorative variant icon is aria-hidden="true" so it isn’t announced.

Close button

An icon-only <button> with no visible text, so give it aria-label="Close" (or "Dismiss") for its accessible name. The icon-close glyph inside is aria-hidden="true", so the button announces as its label alone.

Source: WCAG 4.1.2 Name, Role, Value.