2.2.4 Interruptions

1. What is the goal of this criterion?

Your phone buzzes, your browser shows notifications and something is constantly popping up – our digital lives are full of interruptions. For many people, these constant disruptions are more than just annoying: they make websites and apps simply unusable.

The goal of Success Criterion 2.2.4 is clear: users need to be in control of interruptions. Every automatic update, every pop-up and every notification should be possible to postpone or suppress entirely – unless it’s a genuine emergency.

2. What exactly does it require?

It covers all kinds of interruptions that a website or application triggers on its own – without the user doing anything directly.

The criterion requires that users can either:

• postpone such interruptions (for example, “Remind me again in 30 minutes”)
• or suppress them entirely (for example, “Turn off all automatic updates”).

Important exception: emergencies. WCAG defines an emergency as a sudden, unexpected situation that requires immediate action to preserve health, safety or property – such as a severe weather or disaster warning, or an alert that someone else is accessing your account right now.

A practical example: a news site that refreshes its headlines every five minutes must offer a setting that lets users postpone or turn off these automatic updates – for instance by only showing new stories after a click on “Show new articles”.

3. Why does it matter for accessibility?

Imagine you’re reading an important article with a screen reader – and suddenly the page loads new content. Not only do you lose your reading position, you have to reorient yourself completely. Or you have ADHD and are trying to focus on a text when a chat window suddenly pops up.

Controllable interruptions improve accessibility because they:

• allow people with attention disorders to focus on content without distraction,
• help screen reader users keep their reading position when content suddenly updates,
• protect people with low vision who use magnification and only see part of the screen from changes they don’t notice,
• give people with cognitive disabilities a calmer, more predictable experience.

And not least: they make websites more relaxing for everyone – including people without disabilities who simply want to work in peace.

4. How to meet the criterion

Above all, meeting this criterion takes a deliberate decision: which interruptions are really necessary – and how do you give users control over them?

Offer mechanisms:

• Settings for a “quiet mode” or “do not disturb”
• Pause buttons for automatic updates
• Ways to turn off all notifications that aren’t emergencies
• Postponing options (“Remind me later”)

Keep emergencies narrow:

• Security alerts (for example, “Someone is trying to sign in to your account”)
• Warnings about imminent data loss that require immediate action
• Disaster or severe weather warnings and urgent health notices

Ads, newsletter pop-ups or announcements of new features are never an emergency.

Technical implementation:

• Store the chosen settings in the user account or locally in the browser so they persist on the next visit.
• Bundle notifications in one central control.
• Use aria-live="polite" instead of aria-live="assertive" for updates so screen readers don’t cut off what they’re currently announcing.
• Offer fine-grained control (not just “all on” or “all off”).

What to avoid:

• Automatically reloading the page without consent (see also Change on Request)
• Pop-ups or overlays that can’t be turned off permanently
• Animated ad banners without a stop function (see Pause, Stop, Hide)
• Push notifications without a way to unsubscribe

5. Why this criterion matters for businesses

Even though 2.2.4 is a AAA criterion, implementing it brings clear benefits – especially at a time when many people want to be more mindful of their attention.

1. A wider audience

People with attention disorders, anxiety disorders or neurological conditions make up a larger part of the population than many assume. Controllable interruptions make your product accessible to them – and show respect for everyone’s time and attention.

2. A better experience

Fewer disruptions mean happier users. People who can decide for themselves when notifications arrive are more likely to build a positive relationship with your product and come back.

3. Trust and brand image

In an age of constant sensory overload, you position yourself as a responsible provider that takes its users’ concentration and wellbeing seriously.

And finally: AAA criteria like 2.2.4 are not mandatory under the European Accessibility Act (EAA) or its German implementation, the Barrierefreiheitsstärkungsgesetz (BFSG), since the harmonised standard EN 301 549 references WCAG 2.1 Level AA. Implementing them is a deliberate step beyond the minimum. This is general information, not legal advice.

6. The success criterion in the W3C’s words

Success Criterion 2.2.4 Interruptions (Level AAA)

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

In short: users must be able to postpone or suppress interruptions – only emergencies may always get through.