Understanding Success Criterion 2.2.4: Interruptions

Success Criterion 2.2.4 Interruptions (Level AAA): Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.

Intent

The intent of this Success Criterion is to allow users to turn off updates from the author/server except in emergencies. Emergencies would include civil emergency alert messages or any other messages that warn of danger to health, safety, or property, including data loss, loss of connection, etcetera.

This allows access by people with cognitive limitations or attention disorders by enabling them to focus on the content. It also allows users who are blind or have low vision to keep their "viewing" focus on the content they are currently reading.

Benefits

Examples

Related Resources

Resources are for information purposes only, no endorsement implied.

Techniques

Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. However, it is not necessary to use these particular techniques. For information on using other techniques, see Understanding Techniques for WCAG Success Criteria, particularly the "Other Techniques" section.

Sufficient Techniques

  1. G75: Providing a mechanism to postpone any updating of content
  2. G76: Providing a mechanism to request an update of the content instead of updating automatically
  3. SCR14: Using scripts to make nonessential alerts optional

Advisory Techniques

Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.

Failures

The following are common mistakes that are considered failures of this Success Criterion by the WCAG Working Group.

Key Terms

emergency

a sudden, unexpected situation or occurrence that requires immediate action to preserve health, safety, or property