Goal
Allow users to control interruptions.
Success Criterion · WCAG 2.2.4
Interruptions
Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.
Level AAAWCAG 2.0Operable2.2 · Enough Time
Copy button ready
What to do
Provide a mechanism to postpone or suppress interruptions (like notifications), except for emergencies.
Why it matters
Interruptions can break concentration and can be especially harmful for users with cognitive disabilities.
Success criterion
What WCAG 2.2.4 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.
Intent
Why WCAG created this requirement
- Unexpected interruptions disrupt task flow and comprehension.
- Users should control when and how interruptions are presented.
- Emergency alerts are an exception because safety takes priority.
Benefits
Who gains when you pass
- Users with attention and cognitive disabilities can stay focused.
- Users can finish form entry or reading without being interrupted.
- Users with anxiety can reduce stressful interruptions.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Popups can interrupt typing and cause errors or data loss.
Users may lose context when an interruption steals focus.
Exception guidelines
Use the WCAG 2.2.4 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Emergency
Emergency interruptions are permitted.
Requirement
Only genuine emergency alerts are exempt.
Overview
This AAA criterion requires that users can postpone or suppress non-emergency interruptions, such as pop-ups, notifications, and alerts that interrupt a task. Emergency interruptions are allowed.
- Avoid focus-stealing dialogs; use non-modal notifications when possible.
- Provide notification settings (mute, do not disturb, snooze).
- Do not treat marketing popups as “essential.”
Reference: All summaries and highlights originate from Understanding WCAG 2.2.4 and the W3C quick reference.
Fast facts
- Conformance level
- Level AAA
- WCAG version introduced
- WCAG 2.0
- Principle
- Operable
- Guideline
- 2.2 · Enough Time
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Chat widget
Pass
Chat invitation can be dismissed and “Don’t show again” is available.
Fail
Chat widget opens a modal repeatedly and cannot be disabled.
System alerts
Pass
Non-critical alerts appear as non-modal toasts that do not steal focus.
Fail
Marketing popup steals focus while user is filling a form.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document notification policy and which interruptions are suppressible.
- Record settings UI and default behavior.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Inventory interruptions: popups, toasts, banners, chat prompts, session warnings.
- Add settings to suppress/postpone non-critical notifications.
- Avoid auto-opening modals; require user action when feasible.
- Ensure any alerts do not steal focus unless truly necessary.
- Clearly label emergency alerts and keep them limited to real emergencies.
Testing ideas
Prove conformance with evidence
- Trigger notifications during task flows and verify user can postpone/suppress.
- Verify interruptions do not steal focus unexpectedly.
- Confirm emergency alerts (if any) are the only ones that cannot be postponed.
Related success criteria