Techniques for WCAG 2.0

On this page:

-

# G105: Saving data so that it can be used after a user re-authenticates

## Applicability

Web pages that require user authentication and limit the time available for submitting data.

This technique relates to:

- Success Criterion 2.2.5 (Re-authenticating)
  - How to Meet 2.2.5 (Re-authenticating)
  - Understanding Success Criterion 2.2.5 (Re-authenticating)

## Description

Web servers that require user authentication often terminate the session after a set period of time if there is no activity from the user. If the user is unable to input the data quickly enough and the session times out before they submit, the server will require re-authentication before proceeding. When this happens, the server stores the data in a temporary cache while the user logs in, and when the user has re-authenticated, the data is made available from the cache and the form is processed as if there had never been a session time-out. The server does not keep the cache indefinitely, merely long enough to ensure success after re-authentication in a single user session, such as one day.

## Examples

- A user has logged in to use a forum and replies to a post. The time taken to write the reply is longer than the time allowed by the server for a session of inactivity. The user submits the reply and is informed of the time out and prompted to log in again to submit the response. The user's post reply is retained by the server and if the user log-in is successful the reply is processed as normal. If the log-in cannot be successfully completed the reply is discarded.

- The user had logged in to a secure area and fills out a form. The session times out for security reasons. The form data is retained by the server and the user is informed of the time out and is prompted to log-in again. If the user logs in correctly, the form is presented to the user with all of the data previously entered and user can submit the form. If the log-in cannot be successfully completed the form data is discarded.

## Related Techniques

- G181: Encoding user data as hidden or encrypted data in a re-authorization page

## Tests

### Procedure

On a site that requires user login to submit data,

1. Log in and begin the timed activity.

2. Allow the session to time out.

3. Submit the data.

4. Re-authenticate.

5. Check that the process can continue and be completed without loss of data, including the original data and any changes made after re-authentication.

### Expected Results

- #5 is true.

- Top
- Contents
- Intro
- Previous: Technique G103
- Next: Technique G107