Not timing dependent
Silktide asks you to confirm that nothing on your pages requires visitors to act within a time limit. Timing should never be an essential part of using your website, except for real-time events and non-interactive media.
Examples of timing dependence include quizzes with countdown clocks, offers that expire while you watch, booking flows that release your seat after a few minutes, and games that require timed responses.
Why this matters
Any task with a clock excludes people who need longer: people with motor disabilities who type slowly, users who navigate a page step by step, and people with cognitive disabilities who need time to understand what is being asked. Where a time limit merely inconveniences one visitor, it can make the task impossible for another.
This is the strictest timing requirement in accessibility guidelines (Level AAA): rather than making time limits adjustable, it removes them entirely.
How to fix it
This check asks you to verify your pages manually. For each page, confirm that:
- No content or interaction requires a response within a fixed time.
- Where a process holds resources (such as a ticket reservation), the hold can be extended or the process restarted without losing entered data.
Two exceptions are allowed:
- Real-time events - a live auction or live stream genuinely happens at a fixed time and cannot wait.
- Non-interactive synchronized media - a video plays at its own pace by nature; this is covered by other checks such as .
How Silktide tests this
- Silktide cannot automatically detect time limits, because they usually live in application logic that only appears during interaction.
- Instead, this check raises one review prompt per page, asking you to verify the behavior yourself.
- Once you have verified a page, record your to mark it as checked.