Understanding Success Criterion 2.2.4: Interruptions

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

Intent of Success Criterion 2.2.4: Interruptions

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 of Success Criterion 2.2.4: Interruptions

Examples of Success Criterion 2.2.4: Interruptions

Resources Success Criterion 2.2.4: Interruptions

Techniques for Success Criterion 2.2.4: Interruptions

Sufficient Techniques

  1. 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. Using scripts to make non-essential alerts optional

Advisory Techniques

Failures