This success criterion only applies to timeouts that are within the content provider's Timeouts should be displayed to the user once at theīeginning of the related task or process and not at each step. To save the user data the author must warn the user about the duration of inactivity Start and finish a task, taking breaks as needed. This enables the user with disabilities and the aging community to
The best way to conform to this success criterion is to keep the user data for at This Success Criterion works in tandem with Success Criterion 2.2.1 Timing Adjustable,īut is specifically focused on notification of timeouts related to user inactivity.
If users cannot takeĪ break and check their work, many will often be unable to complete a task correctly. Users shouldīe able to leave a process without losing their current place within the process,Īnd without losing information that has already been entered. The user may not beĪble to complete the process in one sitting and may need to take a break. Instructions and data input required to complete the process. The use of timed events can present significant barriers for users with cognitiveĭisabilities, as these users may require more time to read content or to perform functions,ĭuring the completion of an online process, such as to reserve a hotel room or purchaseĪ plane ticket, a user with a cognitive impairment may become overwhelmed with lengthy Know what duration of inactivity will cause the page to time out and result in lostĭata. The intent of this Success Criterion is to ensure that when a timeout is used, users In brief Objective Users do not lose data due to unknown timeouts Author task Tell users how long their session can be inactive before they may lose information Intent
0 kommentar(er)
