WCAG 2.2.3 No Timing: Remove All Time Limits from Web Content

What This Criterion Requires

WCAG 2.2.3 requires that 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. This is the AAA-level extension of criteria 2.2.1 (Timing Adjustable) and 2.2.2 (Pause, Stop, Hide). While those lower-level criteria allow time limits that can be extended or paused, criterion 2.2.3 goes further by requiring the complete removal of time constraints. This means forms should not expire, content should not auto-advance, and users should have unlimited time to read and interact with all page elements. The only exceptions are live streaming content where timing is inherent to the medium, and real-time events like auctions where timing is fundamental to the activity itself. Meeting this criterion benefits users with cognitive disabilities who process information slowly, users with motor disabilities who interact with interfaces at a reduced pace, and screen reader users who navigate content sequentially.

Why It Matters

Time limits are one of the most significant barriers for users with disabilities. People with cognitive disabilities, learning disabilities, or attention deficit disorders often need substantially more time to read, understand, and respond to content. Motor disabilities can make physical interactions with a computer many times slower than average. Screen reader users must listen to content sequentially and cannot skim a page at a glance, making any timed interaction significantly harder. Even users with temporary situational disabilities, such as a person in a noisy environment or using a device one-handed, benefit from the removal of time pressure. Session timeouts on forms can cause users to lose significant amounts of entered data, creating frustration and potentially preventing them from completing critical tasks like applications, purchases, or healthcare forms. Removing timing requirements is the most inclusive approach and eliminates an entire class of accessibility barriers.

Common Failures and How to Fix Them

// Server-side session expires after 15 minutes
app.use(session({
  cookie: { maxAge: 900000 },
  rolling: false
}));

// Remove session timeout for form data
// Save form progress to database instead
app.post('/save-progress', (req, res) => {
  saveFormProgress(req.user.id, req.body);
  res.json({ saved: true });
});

<div class="carousel" data-auto-advance="5000">
  <div class="slide">Important announcement...</div>
  <div class="slide">Another update...</div>
</div>

<div class="carousel" data-auto-advance="false">
  <div class="slide">Important announcement...</div>
  <div class="slide">Another update...</div>
  <button class="carousel-prev">Previous</button>
  <button class="carousel-next">Next</button>
</div>

<div class="quiz">
  <p>Time remaining: <span id="timer">5:00</span></p>
  <p>What is the capital of France?</p>
</div>

<div class="quiz">
  <p>Take as long as you need to answer each question.</p>
  <p>What is the capital of France?</p>
</div>

How to Test

1. Identify all time-limited interactions on the site, including session timeouts, auto-advancing content, countdown timers, and timed assessments.
2. For each timed element, determine whether timing is truly essential to the activity. If it is not, the time limit should be removed entirely.
3. Test forms by leaving them idle for extended periods to verify that session data is preserved and the user can resume without losing progress.
4. Check that carousels, sliders, and rotating content do not auto-advance, or provide a permanent stop mechanism.
5. Verify that any remaining time limits are only for real-time events or synchronized media where timing is inherent.

CMS-Specific Guidance

This criterion commonly causes issues on these platforms:

• Wordpress Accessibility Checklist
• Shopify Accessibility Checklist
• Squarespace Accessibility Checklist

Further Reading

• Accessible Forms Guide
• Accessible Ecommerce Checkout Guide
• Keyboard Navigation Testing

Related WCAG Criteria

• WCAG 2.2.1
• WCAG 2.2.2