Why this matters
Time-limited interactions are common in educational technology: timed quizzes, session timeouts, rate-limited forms, and auto-saving features. For some students, these time limits are manageable. For others, they create impossible barriers. A student using a screen reader may need 50% more time to read and respond. Someone with fine motor control challenges might type at 10 words per minute instead of 60. A student with processing disorders may need double the time to understand questions and formulate answers.
Beyond individual disabilities, time limits affect equity. They disadvantage students whose first language is not English, those with limited technology access, and those managing competing responsibilities. As educators and technologists, we should build systems that give students the time they need to succeed, not systems that penalize them for working differently.
Accommodations for time limits aren’t “special treatment” – they’re necessary equalization that ensures all students can demonstrate their learning.
WCAG Requirements for Time Limits
WCAG 2.1 addresses time limits in two key criteria:
- WCAG 2.2.1: Timing Adjustable: If content has a time limit, users must be able to turn it off, extend it, or adjust it. There are limited exceptions for real-time events (like live events) and essential timing (like an emergency alert).
- WCAG 2.2.3: No Timing: For content that auto-updates or refreshes, users should be able to control the timing. Auto-advancing carousels, auto-refreshing pages, and real-time feeds need pause or stop controls.
Adjustable Time Limits
Offer Time Extensions
If your application or form has a time limit, offer users clear ways to extend it. Display a countdown timer using an element with aria-live=”polite” so screen reader users hear the time remaining, and provide a clearly labeled button to request more time. This gives users both visual and audio feedback about time remaining.
Allow Turning Off Time Limits
When possible, let users disable time limits entirely. Not all time limits are necessary. If they are necessary, users should have the option to work at their own pace.
Provide Multiple Extensions
Don’t limit users to a single extension. If a student asks for more time once, they may need it again. Allow multiple extensions, or provide a substantial initial extension (like 50% more time) rather than forcing students to request it repeatedly.
Avoid Surprise Timeouts
Never silently log users out or discard their work when a time limit expires. Always warn them before the session ends. Use aria-live=”assertive” with role=”alert” to announce an urgent warning that the session will expire soon, and provide a button to extend the session. This ensures both sighted and screen reader users get the warning in time to take action.
Session Timeouts with Warning
Session timeouts (logging a user out after inactivity) are common for security. They can strand students in the middle of work. If you use session timeouts, implement them carefully:
Warn Before Timeout
Display a clear warning at least 5 minutes before the session expires. Tell users exactly how much time remains and how to extend their session. This warning can be a modal or alert dialog with role=”alertdialog” and clear buttons to extend or log out, giving users explicit control over the timeout behavior.
Make Extension Easy
Extending a session should require minimal action – a single click. Don’t require users to re-enter a password or fill out additional information.
Save Work Automatically
Before timing out, save any unsaved work to a recovery location. Users should be able to recover their work after logging back in, even if they were logged out unexpectedly.
Consider Extending on Activity
Many applications automatically extend session timeouts when users are actively working. This balances security with usability. If a user is typing or interacting, they’re actively engaged and shouldn’t be logged out.
Timed Assessments and Accommodations
Timed quizzes and tests are common in educational systems. However, time limits can measure speed more than knowledge, potentially disadvantaging students with disabilities.
Provide Accommodated Time Limits
Many students qualify for extended time as an accommodation. Your learning management system should support different time limits for different students. Students with disabilities should have access to extra time (commonly 1.5x or 2x the standard time).
Use Your LMS Accommodations System
Canvas, Blackboard, and other learning management systems have built-in accommodation tools. Work with your institution’s disability services office to set up accommodations for students who need them.
Consider Alternatives to Timed Assessments
Ask yourself: Is the time limit essential to what you’re assessing? If you’re measuring knowledge of course content, a time limit may not be necessary. If you’re assessing processing speed or real-time decision-making (like a pilot’s reaction time), then timing may be essential. Most academic assessments don’t require time limits.
Offer Untimed Alternatives
When possible, offer untimed quizzes or assignments in addition to timed ones. This gives students with time-management challenges more options and reduces stress for all learners.
Real-Time Events and Essential Timing
Some content legitimately requires timing. Examples include:
- Live events: A live-streamed lecture or Q&A session happens at a specific time.
- Synchronous communication: A real-time chat or video call requires participants to be present simultaneously.
- Emergency alerts: A safety alert needs immediate attention.
- Time-sensitive processes: Airline booking, stock trading, and other real-time systems require immediate action.
Provide Alternatives or Records
For live events, offer alternatives:
- Record the live event and provide an on-demand version
- Provide transcripts or meeting notes for those who can’t attend live
- Schedule multiple sessions at different times
- Offer one-on-one consultations for students who can’t join group sessions
Allow Asynchronous Participation
When possible, structure synchronous events to also work asynchronously. Students who can’t attend live can submit questions beforehand and access results afterward.
Inactivity Warnings
If you implement inactivity-based timeouts, test them carefully with assistive technology users. A screen reader user may appear inactive (not mouse movements, few keystrokes) while actively reading and engaging with content.
Use Interaction-Based Timeouts Instead
Rather than timing out based on total inactivity, timeout based on meaningful interaction. Reset the timer when users:
- Type or enter data
- Click buttons or links
- Navigate between pages
- Scroll or interact with content
Count All Interactions
Make sure your timeout mechanism counts keyboard interactions, not just mouse movements. A user relying on keyboard alone should have the same session duration as someone using a mouse.
Common mistakes to avoid
- No time extension option: Always allow users to extend or disable time limits when possible.
- Session timeout without warning: Always warn users before their session expires.
- Timeout based only on mouse movement: Use interaction-based detection that includes keyboard activity.
- Losing user work on timeout: Auto-save or recover work before timing out.
- Timed assessments without accommodations: Provide extended time for students who qualify.
- Hard time limits on open-ended assignments: Allow students to work at their own pace on most tasks.
- No countdown timer: Show users how much time remains so they can pace themselves.
- Multiple rapid timeout warnings: Show one clear warning, not repeated alerts.
Related DASH resources
Getting help
UGA’s Digital Accessibility Services Hub (DASH) is here to support you. Whether you need guidance on making your content accessible, help troubleshooting an issue, or training for your team, we are ready to help.
- Contact DASH at [email protected] for consultations, training, or technical assistance.
Accessibility is a shared responsibility, and every step you take makes UGA’s digital environment more inclusive.