
Success criterion 2.2.3
No Timing
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.
- Level AAA
- Principle 2: Operable
- Guideline 2.2: Enough Time
In a user’s words
“The Internet's already a race; don't make it a timed obstacle course too!”
What each role can do
- Product manager
- Eliminate time-based actions unless they are absolutely necessary for the functionality or the content.
- Designer
- Design experiences that do not rely on timed interactions for accessibility.
- Developer
- Avoid code that requires user input within a specific time frame, unless it's critical for real-time or synchronized media.
- Tester
- Check that the website or application does not enforce unnecessary time limits on user actions.
Once it is fixed
“You’ve turned the race into a leisurely stroll. How refreshing!”
Share this with your team
The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 2.2.3 in the W3C quick reference for WCAG 2.2 (opens in a new tab).
Or press ←the left arrow and →the right arrow.