Accessibility lab # AI quiz timer accessibility test A reproducible timer-state and recovery audit for warnings, extensions, expiry, reconnects, focus, answer persistence, and authoritative timing. Published2 October 2026Reading time9 minEvidenceTimer state matrix and recovery acceptance testAuthorThe AI Quiz Lab Test a timed quiz with the timer off, at the default limit, with every supported extension, through warnings, expiry, reconnection, and assistive-technology use. Unless timing is genuinely essential, participants need a documented way to turn off, adjust, or extend the limit. A countdown that looks correct can still lose answers, trap focus, or announce warnings too late. ## Key findings, verified 2 October 2026 - WCAG 2.2 Success Criterion 2.2.1 requires time limits to be adjustable unless a stated exception applies. - W3C explains that many disabled people need more time to read, navigate, or respond. - An extension must preserve answers, focus, remaining time, position, and the same scoring path. - Expiry, network loss, background tabs, and clock changes require explicit recovery tests. - Accessibility conformance does not prove that a timer improves validity or prevents cheating. ## What is a quiz timer accessibility test? A quiz timer accessibility test is a repeatable audit of every state in a timed attempt: configuration, start, warning, extension, pause, expiry, reconnection, and return. It checks both the participant experience and the authoritative server record. The goal is not merely to see a countdown; it is to prove that people receive enough time, can use allowed adjustments, understand status changes, and retain their work. ## Timer state matrix and recovery acceptance test StateTestExpected resultPublication blockerStartBegin with standard and extended timeAnnounced limit matches configurationHidden or wrong durationWarningCross each warning thresholdVisible and programmatic notice without focus theftWarning is visual onlyExtendRequest every allowed extensionTime updates and all answers persistRestart, answer loss, or changed scoringPauseUse pause where supportedClock and state resume consistentlyTimer continues invisiblyExpireAllow time to reach zeroDocumented submission or recovery behaviorSilent loss or ambiguous statusReconnectDisconnect near expiryServer and client reconcile predictablyDuplicate or missing submissionReturnBackground and restore the tabAuthoritative time remains correctClient clock becomes the source of truth ## Reproducible timer test: nine steps - Document the purpose. Record why timing is used and whether a WCAG exception is claimed. - Inventory the rules. List default, per-person, and per-group limits, warning thresholds, pauses, grace periods, and extension controls. - Build equivalent attempts. Run the same quiz with no limit, default time, and every supported extension. - Complete an input journey. Test every warning and control with a keyboard and screen reader. - Check status behavior. Confirm warnings are programmatically announced without moving focus from the current task. - Seed recoverable state. Enter answers before every warning, extension, pause, expiry, and reconnect event; then verify persistence. - Reconcile records. Compare the visible clock, server record, submitted answers, score, and audit log. - Stress the interface. Repeat at narrow width, 200% zoom, reduced motion, and a throttled or interrupted connection. - Save the evidence. Record expected and observed results with the build identifier, configuration, assistive technology, browser, and test time. ## Worked example: an extension resets the attempt A participant requests double time after answering eight questions. The interface reloads with a longer clock but restores only six answers. The extension exists, yet the attempt is not equivalent. Block publication until all answers, current position, focus, remaining time, and scoring state survive the change. ## What timing adjustment requires WCAG 2.2.1 allows several paths where no exception applies: turn the limit off, let the participant adjust it over a sufficiently wide range, or provide an extension mechanism with adequate warning. W3C technique G180 documents an extension flow that warns before expiry and permits repeated extensions. Treat these as minimum conformance patterns, not permission to skip product-specific usability and recovery testing. ## Source-bounded timer QA prompt Using only the timer configuration, state log, client events, server events, and accessibility observations supplied below, compare expected and observed behavior for Start, Warning, Extend, Pause, Expire, Reconnect, and Return. For every failure, name the affected state, exact evidence, participant impact, and retest condition. Do not infer behavior that is absent from the evidence. Return “not tested” when a state lacks a recorded observation. ## Publication blockers - The time limit is not adjustable and no documented WCAG exception applies. - A warning is visual only, steals focus, obscures the question, or arrives too late for the participant to act. - An extension resets the attempt, loses answers, changes position, or uses a different scoring path. - Client and server clocks disagree about expiry or accepted answers. - Automatic submission or recovery behavior is undocumented or ambiguous. - A dropped connection creates duplicate, missing, or silently discarded submissions. - The countdown, warning, or controls fail keyboard, reflow, zoom, reduced-motion, or assistive-technology checks. ## What this test does not prove This test checks timer adjustability, warnings, state preservation, and recovery. It is not legal advice or a complete WCAG conformance audit. It does not prove that the assessment is reliable, fair, secure, valid, or suitable for high-stakes decisions. Where timing is claimed to be essential, document that decision and have qualified accessibility and assessment professionals review it. ## Sources, verification date, and corrections This guide was verified on 2 October 2026 against W3C's current [Understanding Success Criterion 2.2.1: Timing Adjustable](https://www.w3.org/WAI/WCAG22/Understanding/timing-adjustable), [Enough Time guidance](https://www.w3.org/WAI/WCAG22/Understanding/enough-time.html), and [technique G180 for extending time limits](https://www.w3.org/WAI/WCAG22/Techniques/general/G180). Those sources support the adjustment, warning, extension, and additional-time principles. The state matrix, nine-step recovery audit, worked example, QA prompt, and blockers are original AI Quiz Lab evidence assets. Report changed guidance or reproducibility problems through the [corrections process](https://bestaiquizgenerator.com/corrections). ## Next checks Run the full experience through the [AI quiz accessibility checklist](https://bestaiquizgenerator.com/blog/accessible-ai-quiz-checklist), verify the questions with the [question-quality checklist](https://bestaiquizgenerator.com/blog/how-to-evaluate-ai-generated-quiz-questions), and test score-boundary behavior with the [score-band threshold test](https://bestaiquizgenerator.com/blog/ai-quiz-score-band-test). --- Canonical: https://bestaiquizgenerator.com/blog/ai-quiz-timer-test