Loading...
Loading content...
Loading content...
If a session expires, users can log back in and continue where they left off without losing data.
Why it matters: Prevents data loss for users who take longer to complete tasks.
When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.
What This Means: This success criterion requires that when a user's authenticated session expires (times out), they must be able to re-authenticate (log back in) and continue their work without losing any data they had entered. All form data, progress, and work must be preserved and restored after re-authentication.
Why It's Important: Users with disabilities may take longer to complete tasks, making them more likely to encounter session timeouts. If data is lost when a session expires, these users lose their work and must start over, which is frustrating and may prevent them from completing tasks. By preserving data across session expiration, we ensure users don't lose their progress.
Save all user input and progress automatically, either to the server or local storage. When a session expires, show a clear message and allow re-authentication. After re-authentication, restore all saved data so users can continue exactly where they left off. Test by letting a session expire and verifying that all data is preserved and restored after logging back in.
This criterion ensures that all users can access and understand the content, improving their overall experience and ability to use the website effectively.
This criterion ensures that users with motor disabilities can access and understand the content, improving their overall experience and ability to use the website effectively.
This criterion ensures that users with cognitive disabilities can access and understand the content, improving their overall experience and ability to use the website effectively.
Impact: When this criterion is properly implemented, it removes barriers for these user groups and creates a more inclusive web experience for everyone.
When session expires, all form data is lost and cannot be recovered.
<form>
<input type="text" name="data">
<!-- Data lost on session expiration -->
</form>When session expires, data is saved and restored after re-authentication.
<form onchange="saveDraft()">
<input type="text" name="data">
<!-- Data saved and restored after re-auth -->
</form>This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 2.2.5 Re-authenticating are met. Check off items as you complete them.
To meet this success criterion, ensure the following requirements are met:
While meeting the minimum requirements ensures compliance, consider these enhancements for a better user experience:
Session expiration is a security feature, so data loss is acceptable.
Security and accessibility can coexist. Data should be preserved even when sessions expire, allowing users to re-authenticate and continue.
Session expiration causes complete data loss.
Implement auto-save functionality. Preserve form data in localStorage or server-side. Restore data after re-authentication.
Users must re-enter all data after session expiration.
Auto-save data as users type. Restore all data automatically after re-authentication. Provide clear messaging about data preservation.
Note: These are official W3C resources for 2.2.5. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 2.2.5 Re-authenticating correctly requires understanding your specific context. Code solutions vary significantly based on multiple factors:
HTML, React, Vue, Angular, PHP, Python, and other frameworks each have different patterns and best practices.
Server-side rendering, client-side rendering, static generation, and hybrid approaches require different solutions.
Your existing components, styling approach, and UI library influence how accessibility must be implemented.
Your specific user base, content type, and interaction patterns determine the most appropriate implementation.
We provide tailored implementation guidance by analyzing your specific technology stack, coding patterns, design system, and project requirements. Our team reviews your codebase and provides custom solutions that integrate seamlessly with your existing architecture.
Get Custom Implementation HelpPart of
Operable PrincipleGuideline
2.2 Enough Time