Loading...
Loading content...
Loading content...
Users must be able to turn off, adjust, or extend time limits.
Why it matters: Users with disabilities may need more time to read or interact with content.
For each time limit that is set by the content, at least one of the following is true: (Level A) Turn off: The user is allowed to turn off the time limit before encountering it; or Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, 'press the space bar'), and the user is allowed to extend the time limit at least ten times; or Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or Essential Exception: The time limit is essential and extending it would invalidate the activity; or 20 Hour Exception: The time limit is longer than 20 hours.
What This Means: This success criterion requires that any time limit set by content must allow users to either turn it off, adjust it (to at least 10x the default), or extend it (with at least 20 seconds warning and ability to extend at least 10 times). Exceptions exist for real-time events (like auctions), essential time limits (where extending would invalidate the activity), and time limits longer than 20 hours.
Why It's Important: Users with disabilities may need more time to read content, fill out forms, or complete tasks. Cognitive disabilities, motor disabilities, or low vision can all require additional time. If time limits cannot be controlled, these users are excluded from accessing the content or completing tasks.
For session timeouts, provide warnings before expiration and allow users to extend. For form timeouts, allow users to adjust or extend the time limit. For timed tests or activities, provide options to turn off or adjust timing. Only use fixed time limits when they're essential to the function (like real-time events) or when the limit is longer than 20 hours.
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.
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 low vision 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.
A session times out after 15 minutes with no way to extend it, causing data loss.
setTimeout(() => { logout(); }, 900000);A session warns users before timeout and allows them to extend the session.
setTimeout(() => { showExtensionDialog(); }, 840000);This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 2.2.1 Timing Adjustable 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:
If I warn users about time limits, that's enough.
Warnings alone are not sufficient. Users must be able to actually extend or turn off the time limit, not just be warned about it.
Time limits are necessary for security, so they can't be extended.
While some time limits may be essential, most can be extended. Security concerns should be balanced with accessibility needs. Consider longer default timeouts or user-adjustable limits.
Session timeouts without extension options.
Provide a way to extend sessions. Show warnings before timeout and allow users to extend. Save work automatically to prevent data loss.
Form submission deadlines without extension.
Allow users to extend deadlines or remove them entirely. If deadlines are essential, clearly explain why and provide alternatives.
Time limits that cannot be turned off or adjusted.
Provide controls to turn off or adjust time limits. Only keep essential time limits that cannot be changed, and clearly mark them as such.
Note: These are official W3C resources for 2.2.1. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 2.2.1 Timing Adjustable 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