Loading...
Loading content...
Loading content...
No time limits on content interaction.
Why it matters: Removes pressure and ensures all users can complete tasks at their own pace.
Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.
What This Means: This success criterion is a stricter version of 2.2.1 (Level A). At Level AAA, no time limits should be imposed on user interactions, except for non-interactive synchronized media (like videos that play automatically) and real-time events (like auctions or live games where timing is essential). Users must be able to take as long as they need to read, understand, and interact with content.
Why It's Important: Time limits create pressure and can prevent users with disabilities from completing tasks. Users with cognitive disabilities may need more time to process information. Users with motor disabilities may need more time to interact. By removing time limits entirely (except where essential), we ensure that all users can complete tasks at their own pace without pressure.
Remove all time limits from forms, reading content, and interactive activities. Allow users to take as long as needed. Only keep time limits for real-time events (like auctions) or non-interactive media (like videos). For session management, use very long timeouts (20+ hours) or provide clear warnings with easy extension options.
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.
Impact: When this criterion is properly implemented, it removes barriers for these user groups and creates a more inclusive web experience for everyone.
A form automatically submits after 5 minutes, causing data loss.
<form onsubmit="submitForm()">
<!-- Form auto-submits after 5 minutes -->
</form>A form allows users to take as long as needed to complete it.
<form>
<!-- No time limit, users can take as long as needed -->
</form>This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 2.2.3 No Timing 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:
All time limits are bad and must be removed.
Time limits for non-interactive media (videos) and real-time events (auctions) are acceptable. The issue is with time limits on user interactions like forms or reading content.
Forms that auto-submit after a timeout.
Remove auto-submit timeouts. Allow users to take as long as needed. Save progress automatically.
Reading time limits or deadlines on content consumption.
Remove time limits on reading or viewing content. Users should be able to take as long as needed.
Note: These are official W3C resources for 2.2.3. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 2.2.3 No Timing 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