Accessibility

Accessible global alert requirements

Keep these considerations in mind if you're modifying the Design System or creating a custom component.

WCAG guidelines

2.1 Keyboard accessible

Ensure that global alerts are operable by providing keyboard accessibility. Users should be able to navigate and interact with alerts using only a keyboard, without requiring a mouse or other pointing device. This includes ensuring that all interactive elements within the alert are keyboard accessible (W3C, 2018).

3.1.3 Unusual words

Avoid using jargon, technical terms, or uncommon words in alert banners. If an unusual word is necessary, provide a clear definition or explanation in the alert or through a link to more information.

Example: Instead of ‘Our DNS server is down.’ use ‘Our website is temporarily down.’

3.1.5 Reading level

Make sure the text in alert banners is written at a reading level of between Grade 7 and 8. Use simple sentences and common words so it can be understood by more people.

Example: Instead of ‘This website's functionality is unavailable. Our technical team is working expeditiously to rectify the situation.’ use ‘This site is temporarily down. We’re working to fix this as quickly as possible.’