See Understanding Techniques. Providing options to continue without loss of data using one of the following techniques: G105: Saving data so that it can be used after a user re-authenticates G181: Encoding user data as hidden or encrypted data in a re-authorization page Failures for Success Criterion 2.2.5 F12: Failure of Success Criterion 2.2.5 due to having a session time limit without a mechanism re-authentication Back to top 2.2.6 Timeouts Level AAA (Added in 2.1) Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions. Understanding 2.2.6 Show Hide techniques and failures for 2.2.6 Sufficient Advisory Failures Sufficient Techniques for Success Criterion 2.2.6 Note: Other techniques may also be sufficient if they meet the success criterion. See Understanding Techniques. Setting a session timeout to occur following at least 20 hours of inactivity.