WCAG Master Guide: Timing

Do you have content or elements on your site that users need to read or complete in a certain amount of time? You could be alienating more website visitors than you might realize. 

Timing is a part of the Operable section of the Website Content Accessibility Guidelines (WCAG) and should be a key consideration when remediating your website. 

Timing and Accessibility

WCAG states that you should never force timing on a user.

Users with disabilities often need to take more time to read or listen to content, or complete tasks such as filling in a form.

By enforcing a time limit, you are inadvertently creating a more stressful and frustrating user experience. You may also be limiting your site’s potential and causing brand damage. 

WCAG Timing Success Criteria

Here are the timing success criteria you would need to meet in order to achieve Level A or higher.

Timing Adjustable

Should you need to time any of your site’s functions or content, the following requirements need to be met:

• Users have the ability to turn the timer off.
• The timer can be adjusted by up to ten times the original limit.
• A 20-second warning is given to users who are close to reaching a time limit, giving them the ability to extend it.

The only time these requirements wouldn’t apply is if the limit is essential to the function, is linked to a real-time event, or the limit is 20 hours or longer.

Pause, Stop, Hide

For blinking, scrolling, or auto-updating content, the following requirements will apply:

• Moving, blinking, or scrolling content that starts automatically, lasts more than five seconds, or is presented in conjunction with other content can be paused, stopped, or hidden by the user.
• Auto-updating content can also be paused, stopped, or hidden. 

Level AAA Timing Requirements

Most website owners only need to aim to achieve WCAG Level AA. However, for those who want to achieve Level AAA, the following requirements need to be met for timed content:

• Unless timing is an essential part of an activity or content, it should be avoided wherever possible.
• Users have the ability to switch off updates from the author/server except in emergencies such as civil emergency alert messages or any other messages that warn of danger to health, safety, or property.
• When an authenticated session expires, a user can continue their activity without losing any input data after re-authenticating.
• If data will be lost after an activity times out, the user should be notified in advance. 

Timing Best Practices

To help you meet Level AA, the ideal WCAG compliance level, here are a few timing best practices you can apply. 

1. Avoid timed content where possible. Unless it’s absolutely necessary, it’s best to avoid timed content and functionality altogether. 
2. Keep time controls clear and easy to access. Make sure users know exactly how to pause, stop, or hide content by keeping these controls in an accessible place. Controls should also be distinguishable and easy to click.
3. Create clear timing warnings. Timeout warnings should be distinguishable and accompanied by clear text and not just an icon. 

Frequently Asked Questions