W3C WCAG 2.2 Understanding Success Criterion 2.2.5: Re-authenticating
Documents preserving user activity and data through re-authentication, reinforcing that exit and session-boundary warnings should protect context rather than merely announce loss.
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Exit warning | Choose exit warning when departure has already been attempted and leaving would lose work or context that is not safely recoverable. | The warning appears only after a departure attempt or immediately before a known session boundary that could cause loss. | W3C documents preserving user activity after re-authentication. |
| Session timeout | Choose session timeout when the authenticated session has already expired or been terminated and the next valid path is sign-in, reauthentication, restart, or safe task restoration. | The timeout state is driven by server or identity-provider session validity, not by a cosmetic client-only overlay. | Supports reauthentication recovery without loss of user activity or data. |
| Session timeout warning | Choose session timeout warning when the session is approaching an inactivity, absolute, device-lock, or reauthentication boundary that can interrupt authenticated work. | The warning is driven by the authoritative session or identity state, not only a local countdown. | W3C documents preserving user activity after reauthentication. |
Comparisons supported by this source
- Exit warning vs autosave form vs draft state vs confirmation dialog
W3C documents preserving user activity after re-authentication instead of losing data at a session boundary.
- Permission recovery vs permission denied state vs session timeout warning vs retry
Reauthentication guidance helps distinguish session recovery from authorization recovery.
- Session timeout vs session timeout warning vs sign in vs permission denied state vs autosave recovery
Supports preserving activity and data after reauthentication.
- Session timeout warning vs exit warning vs autosave form vs permission denied state
W3C documents continuing authenticated activity without data loss after reauthentication.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: World Wide Web Consortium. Last checked: .