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.
Individuals with attention deficit disorders can focus on content without distraction.
Individuals with low vision or who use screen readers will not have content updated while they are viewing it (which can lead to discontinuity and misunderstanding if they start reading in one topic and finish in another).
Example 1. Setting user preferences
The preferences page of a Web portal includes an option to postpone all updates and alerts until the end of the current session, except for alerts concerning emergencies.
Resources are for information purposes only, no endorsement implied.
(none currently documented)
Each numbered item in this section represents a technique or combination of techniques that theWCAG 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, seeUnderstanding Techniques for WCAG Success Criteria, particularly the "Other Techniques" section.
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.
(none currently documented)
The following are common mistakes that are considered failures of Success Criterion 2.2.4 by theWCAG Working Group.
This Web page is part ofUnderstanding WCAG 2.0: A guide to understanding and implementing WCAG 2.0 (see thelatest version of this document). The entire document is also available as asingle HTML file. See theThe WCAG 2.0 Documents for an explanation of how this document fits in with other Web Content Accessibility Guidelines (WCAG) 2.0 documents. To send public comments, please follow theInstructions for Commenting on WCAG 2.0 Documents.
Copyright © 2023World Wide Web Consortium.W3C®liability,trademark anddocument use rules apply.