2.2 Enough Time · SC 2.2.4

AAA2 min read

Interruptions

Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.

In plain language

People should be able to postpone or turn off interruptions (like content updates or alerts) whenever they want. Genuine emergency messages are the exception.

Why it matters

An interruption in the middle of a task, such as a notification popping up or content refreshing, can throw off someone with attention or cognitive difficulties, or make a screen reader user lose their place. Control over non-urgent interruptions lets people stay focused.

In practice

Fails this criterion

A news site refreshes its headlines every 30 seconds with no way to turn it off, interrupting screen reader users again and again while they read.

Meets this criterion

The same site has a setting that lets users postpone all non-emergency updates and alerts until they choose to check for them.

Test it yourself

Look for anything that updates or interrupts you on its own while you use the site (notifications, auto-refreshing content). Is there a way to postpone or turn these off? If not, and they aren't genuine emergencies, this criterion is failing.

Read SC 2.2.4 on the official WCAG 2.2 specification ↗