Operable

2.2.1 Timing Adjustable

Level AWCAG 2.2Automated checks exist

When a page has a time limit, people must be able to turn it off, adjust it or extend it, with exceptions such as live auctions.

Who it helps

People who read, type or move more slowly, including many screen reader users.

Failures we see most

  • Session timeouts with no warning
  • Forms that expire before a slower typist finishes

How it gets tested

Our scanner runs this axe-core check for 2.2.1:

Automated checks for 2.2.1
CheckWhat it looks for
meta-refreshDelayed refresh under 20 hours must not be used

Automated checks can find failures of 2.2.1, but they cannot confirm that a page passes. A specialist still reviews it by hand.

How we fix it

A specialist fixes this in your site's code or content, and we re-test the page before you sign off.

Official text: W3C, Understanding 2.2.1 Timing Adjustable. Checks listed from axe-core 4.14.0.

Related criteria

Does your site fail 2.2.1?

Our free scan checks up to 50 of your pages and tells you which criteria fail and where.

Get a free scan