Default font size Increase font size  |   Decrease font size   |  
Skip to main content

Success Criterion 2.2.5 Re-authenticating: [Level AAA]

This deals with the preservation of state in transactions that require user authentication. If the user is logged out because of a time limit being exceeded, when logging back in, they should be able to pick up where they left off.

Techniques

Saving data

Often a time limit is set for terminating an application after a period on inactivity. In these cases, any data pertaining to the transaction should be saved and when the user is re-authenticated, that saved data restored for the user to continue with the transaction.

Sometimes it may be a security risk or even illegal to save any such data on the server. In these cases, the data may passed as hidden data to the page where the user can login/re-authenticate and this can then be passed back and restored to the point that the user was previously working.

Failures

No saving mechanism

A failure of this criterion would be caused by the inability for any data to be saved in the event of a session timeout.

Top