2.2.3 No Timing

What this rule means

WCAG 2.2.3 is the AAA-level extension of 2.2.1 (Timing Adjustable). While 2.2.1 requires mechanisms to turn off, adjust, or extend time limits, 2.2.3 goes further by requiring that timing is eliminated entirely from content interactions. Users should be able to complete any task at their own pace without any time pressure whatsoever.

Only two exceptions exist: non-interactive synchronized media (pre-recorded video/audio where timing is inherent to the content) and real-time events (live broadcasts, auctions). Every other type of time limit — session timeouts, form deadlines, quiz timers, auto-advancing content — must be removed entirely, not just made adjustable.

Why it matters

Even with adjustable timing (2.2.1), some users may not respond quickly enough to extend a timer, may not notice a timeout warning, or may find the extension process itself disruptive. Users with severe cognitive disabilities may not understand the concept of a timeout at all. Eliminating timing entirely removes these barriers.

For applications targeting AAA conformance, removing time limits signals a commitment to universal access. It allows users with the most severe disabilities — including those with significant cognitive impairments — to interact with content at whatever pace they need, without anxiety about losing progress or being locked out.

Related axe-core rules

There are no automated axe-core rules for this criterion. Detecting the absence of time limits requires comprehensive manual review of application logic, server-side session management, and client-side timers.

How to test

Testing requires a thorough inventory of all timed functionality and verification that timing has been removed.

1. Audit the entire application for any form of time limit: session timeouts, form submission deadlines, auto-advancing content, countdown timers, or timed assessments.
2. For each time limit found, determine if it qualifies as a real-time event or synchronized media exception.
3. Verify that non-exception time limits have been completely removed, not just made adjustable.
4. Leave pages open for extended periods (hours) and verify no session expiration occurs for content interaction.
5. Confirm that all content can be consumed at the user's own pace with no time pressure.

How to fix

Remove time limits entirely or use indefinite sessions where security permits.

Indefinite form session

// Instead of a session timeout, auto-save progress
let autoSaveInterval = setInterval(() => {
  const formData = collectFormData();
  localStorage.setItem('form-draft', JSON.stringify(formData));
  // Also save to server periodically
  fetch('/api/save-draft', {
    method: 'POST',
    body: JSON.stringify(formData),
    headers: { 'Content-Type': 'application/json' }
  }).catch(() => {
    // Silent fail — local storage serves as backup
  });
}, 30000); // Auto-save every 30 seconds

// Restore draft on page load
window.addEventListener('load', () => {
  const draft = localStorage.getItem('form-draft');
  if (draft) {
    restoreFormData(JSON.parse(draft));
  }
});

Untimed assessment

<!-- Bad: timed quiz -->
<div class="quiz">
  <p>Time remaining: <span id="timer">05:00</span></p>
  <!-- quiz questions -->
</div>

<!-- Good: untimed quiz with progress indicator -->
<div class="quiz">
  <p>Question 3 of 10 — Take as much time as you need</p>
  <progress value="3" max="10"
    aria-label="Quiz progress: 3 of 10 questions"></progress>
  <!-- quiz questions -->
</div>

Common mistakes

• Making time limits adjustable but not eliminating them entirely (only satisfies 2.2.1, not 2.2.3).
• Session timeouts that cannot be removed due to security policies without exploring alternative session management.
• Timed assessments or quizzes where timing is not truly essential to measuring the skill being tested.
• Auto-advancing presentations that do not offer a self-paced mode.
• Transaction deadlines (e.g., "Complete checkout within 15 minutes") that could use cart persistence instead.