Marcelo Paiva

All criteriaPresent as slides

A woman in a wheelchair with her mouth open, beside a large round door and swirling smoke.Meant to show: A woman in a manual wheelchair, a mug balanced on her lap

Success criterion 2.2.6

Timeouts

Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.

  • Level AAA
  • Principle 2: Operable
  • Guideline 2.2: Enough Time

In a user’s words

“I stepped away for a coffee and came back to a locked vault. Let me know if you're timing me out!”

Who this helps: Various, including mobility and cognitive impairments

What each role can do

Product manager
Clearly communicate any timeouts that might result in data loss.
Designer
Design notifications or alerts to inform users about the session timeout.
Developer
Implement mechanisms to warn the user prior to timeouts and preserve data whenever possible.
Tester
Test for session timeout warnings and data preservation across different scenarios.

Once it is fixed

“Now I can enjoy my coffee and still know what's going on. Cheers!”

The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 2.2.6 in the W3C quick reference for WCAG 2.2 (opens in a new tab).

Or press the left arrow and the right arrow.

A success criterion

This is one page of a phrase book. It takes one success criterion and tells it from the side of the person it helps.

From top to bottom

  1. At the top, the site header: my name, which goes home, then links to Writing, Work, Signal, Tools and Resume, then Settings, where you choose the drawings, light or dark, and movement.
  2. Links back to all the criteria, and to present this one as slides.
  3. A drawing, the criterion’s number and name, what it requires in one sentence, and its level.
  4. In a user’s words: a quote from the person who meets the barrier.
  5. What each role can do: one task each for the product manager, the designer, the developer and the tester.
  6. Once it is fixed: the same person again.
  7. Share this with your team: post to LinkedIn, download the slides as a PDF, or copy a link.
  8. Some criteria then have a t-shirt to order.
  9. Links to the previous and next criterion. The left and right arrow keys go there too.
  10. At the bottom, the footer: a note on how this site is built, links to Illustrations, Pens, Concepts and Accessibility, this Describe this page button, then GitHub, LinkedIn and email.

What you can do here

Learn what this criterion asks, and what your part of the fix is.

Also here

The quotes are written to illustrate the criterion. They are not from real people.