2.2.1 Timing Adjustable

MCS Accessibility Team

MCS Accessibility Team
Last Updated July 23, 2020

The following directions are part of a full step-by-step guide to making a HubSpot website WCAG 2.1 AA compliant. These recommendations are intended for websites managed on the HubSpot CMS but can be adapted for other content management systems.

Principle: Operable
User interface components and navigation must be operable.
Guideline: Enough Time
Provide users enough time to read and use content.

For each time limit that is set by the content, at least one of the following is true:

  • Turn off: The user is allowed to turn off the time limit before encountering it; or
  • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
  • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
  • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  • Essential Exception: The time limit is essential and extending it would invalidate the activity; or
  • 20 Hour Exception: The time limit is longer than 20 hours.

Note 1: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

View Official WCAG 2.1 Compliance Techniques

Understanding 2.2.1 Timing Adjustable

This criteria ensures that people with disabilities are given enough time to interact with web content such as filling out forms when possible. People with low vision, blindness or cognitive limitations may require more time when reading content or filling out form. If certain functions like timed surveys or quizzes are required there needs to be an option that allow people to turn off the timer, customize the length of time and/or request more time before time runs out.

The developer should provide these options in the order that is most helpful to user starting with allowing the user to disable the time, then changing the time, and then requesting more time.


If there are session time limits, or the time limit is controlled by a script, or time limits on reading. A sufficient technique to meet this criteria as a developer would be to provide a way for the user to turn the time limit off, adjust the time or extend the time ideally at the top of the page. However, just because this is not automatically resolved does not mean that you're not meeting the criteria's standards. The average website does not have the need for this type timing adjustment.


There are some exceptions when it comes to adjusting the time limit.

  • An auction where a time limit is required for bidding
  • Any password protected environment where the time limit is required
  • You do not need to provide a time limit if it's over 20 hours

For more information, please visit the official W3C article: Understanding 2.2.1 Timing Adjustable


Let us know if we can help you address this specific WCAG Recommendation.