WCAG Guideline 2.2.3: No Timing Explained
Estimated read time: 6–7 minutes
Guideline 2: Operable
The Operable principle ensures that all users can interact with and control web content, regardless of their abilities. This includes removing unnecessary time constraints that could prevent users from completing tasks.
Guideline 2.2: Enough Time
Guideline 2.2 focuses on making sure users have enough time to complete tasks. No Timing is the strictest standard, requiring that content does not impose any time limits at all.
What Is Guideline 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."
Guideline 2.2.3 No Timing is a Level AAA requirement in the Web Content Accessibility Guidelines (WCAG) .
- Content must not require users to complete tasks within a set time limit.
- Exceptions: real-time events and non-interactive synchronized media (like live video).
- Applies to forms, quizzes, games, and any interactive content.
This ensures users can complete activities at their own pace, without being rushed or excluded by time limits.
For more, see Web Accessibility Doesn’t Have a Deadline (BOIA) .
Why Does It Matter?
- Inclusivity: Time limits can exclude users who need more time due to disabilities.
- Legal Compliance: No Timing is a Level AAA requirement in WCAG 2.1 and 2.2.
- Usability: Prevents frustration and loss of access for all users.
For more, see W3C’s guidance on time limits .
What Needs to Support No Timing?
- Online forms and quizzes
- Games and interactive activities
- Any feature with a time limit
All must not impose time limits, unless an exception applies.
How to Make Content Accessible Without Timing
- Remove unnecessary time limits
- Allow users to complete activities at their own pace
- Document timing policies
- Test with users who need more time
For more, see the W3C's No Timing Techniques .
Common Mistakes to Avoid
- Unnecessary time limits
- No way to adjust or remove time limits
- Not documenting timing policies
- Not testing with users who need more time
Differences Between A, AA, and AAA for Guideline 2.2.3 in WCAG 2.2
- Level A: Not applicable for this guideline.
- Level AA: Not applicable for this guideline.
- Level AAA: Requires that timing is not essential for any event or activity, except for non-interactive synchronized media and real-time events. This is the core requirement for 2.2.3 and is mandatory for AAA conformance.
For more, see the W3C’s official documentation for 2.2.3 No Timing .
Quick Checklist
- No unnecessary time limits
- Users can complete activities at their own pace
- Timing policies are documented
- Tested with users who need more time
Summary
Guideline 2.2.3 is essential for ensuring users are not excluded by time limits. By removing unnecessary timing, you support users with disabilities, improve usability, and meet legal requirements. Test your site regularly and make timing flexibility a core part of your development process.