No Timing

Why it matters

An adjustable limit still asks the user to notice a warning, work out what it means, and act on it before the clock runs out. Removing the limit removes that whole job from the people who find noticing and acting hardest. W3C's list of who needs the time is longer than most people expect, and it starts with blind readers, who need time to understand a screen layout before they can even begin the task. A deaf reader working through a live interpreter is running an extra translation step inside whatever clock you set.

Who this rule protects

W3C names blind readers first, then people with low vision, then people with cognitive limitations and people with motor impairments, and adds deaf readers for whom written text is a second language.

How to check it yourself

1. 1List every place where finishing on time changes the outcome. Bookings that release, sessions that drop, tests that close.
2. 2For each one, ask whether the timing is genuinely essential to the activity or a design choice somebody made.
3. 3Check the two exceptions honestly. A video has a running time. A live auction has a close. A countdown you wrote is not a real-time event, because a real-time event is not generated by the content.
4. 4Send the carousels and auto-advancing panels to criterion 2.2.2 instead, which is Level A and is where moving content actually belongs.

Failures we see most often

• A checkout countdown creates urgency rather than holding any stock.
• Session expiry is set short for convenience rather than for a security requirement anybody can point at.
• A timed test gets defended as a real-time event, which it is not. W3C's own answer is to calibrate the test on untimed scores instead.

Who this one is for

Read from this rule's own note above, so the grouping and the note cannot disagree.

• Blind and screen reader userspeople who cannot see the screen
• Low visionpeople who can see the screen but not easily
• Deaf and hard of hearingpeople who cannot hear the audio
• Motor and keyboard-onlypeople who cannot use a mouse, or cannot use one precisely
• Cognitive and learningpeople for whom the difficulty is understanding, remembering, or staying with it

How to fix it

• Remove decorative and marketing timers outright, which is the only sufficient technique W3C lists for this criterion.
• Hold stock quietly in the background instead of counting down at the shopper.
• Design the timing out of an assessment rather than claiming an exception for it.
• Where security genuinely requires a session limit, look at criterion 2.2.5 next door, which asks that the user's work survives the login.

Passes vs. fails