WCAG 2.0 · Level AAA · Operable
2.2.4 Interruptions
Manual verification
How to validate 2.2.4 by hand
Check whether interruptions can be postponed or suppressed, except for emergencies.
Start with the extension result
Reopen the reported URL and reproduce the same state (for example, after expanding a menu or submitting a form). Use the result’s Highlight action when available, or its affected-element details and CSS selector, to find the reported content. Apply the checks below to that content and its context. If the element or state has changed, rescan and record that difference before deciding whether the finding still applies.
- Use the page or application long enough to encounter notifications, alerts, refreshes, or context changes.
- Check whether non-emergency interruptions can be delayed, dismissed, or disabled without losing important information.
- Repeat the task with interruptions suppressed and determine whether the user can continue at their own pace.
Evidence to record
Record the interruption, whether it was expected, available control, and any task or input lost.
Scope and exceptions
Emergencies are excepted. A message necessary to the current task may not be an interruption; assess its context and whether it takes control away from the user.
Record the review outcome
- Confirmed: the recorded evidence shows the requirement is not met in the tested page state, and no applicable exception explains it.
- Not reproduced: the reported issue is absent in the current state. Record the URL, state, and affected element you checked; this does not prove other pages or states conform.
- Needs more review: evidence is incomplete, the content requires human judgment, or an exception is uncertain. Record what remains to be checked instead of treating it as a pass.