What this criterion requires
When a session expires, the user can continue the activity without data loss after re-authenticating.
Who it helps
Slow typists and anyone whose session lapses mid-transaction.
Example: fails vs passes
Re-login discards the application form the user spent 20 minutes on.
After re-authenticating, the form is restored exactly as it was.
Preserve state server-side or locally across the auth boundary.
How to meet and fix it
- Preserve form state across re-login and restore it afterwards
Common failures auditors find
- Login redirects that discard a filled cart or application form
Automated scanning catches a share of these instantly - run a free check - and a manual audit covers the judgement calls a tool cannot make.
Sources
- W3C, Understanding 2.2.5: Re-authenticating - w3.org/WAI
- W3C, How to Meet 2.2.5 (quick reference) - w3.org/WAI/quickref
Last updated . Reviewed by the EqualWeb accessibility team.
Does your site pass 2.2.5?
Run a free automated check now, or have certified IAAP/CPWA auditors test every criterion and document the result.