2.2.3 No Timing

1. What is the goal of this criterion?

Imagine trying to buy a ticket online, but the system only gives you 30 seconds – and you need a minute to enter your details. Frustrating, right? For many people with disabilities, this is everyday reality with time-limited content.

The goal of Success Criterion 2.2.3 is radically simple: content should work without timing requirements. People with disabilities often need more time to read, understand or operate content – and they should get that time.

2. What exactly does it require?

Success Criterion 2.2.3 goes one step further than the Level A criterion Timing Adjustable. The rule: timing must not be an essential part of an event or activity – with only two exceptions:

Allowed exceptions:

• Non-interactive synchronized media (for example, a video with sound that doesn’t require any interaction)
• Real-time events (for example, live auctions or live broadcasts)

Not allowed, for example:

• Timed tests or exams – even if time is part of the task
• Forms that expire after a certain time
• Automatic page changes or timed redirects
• Time-based games or activities that aren’t real-time events

The difference from Level A: 2.2.1 allows time limits if they can be turned off, adjusted or extended, and has exceptions for essential time limits and limits over 20 hours. With 2.2.3, these exceptions disappear – only synchronized media and real-time events remain.

3. Why does it matter for accessibility?

Imagine taking an important online test that cancels automatically after 60 minutes – even though you know the material and simply need more time to read.

Content without time pressure creates real accessibility because it:

• gives blind people more time to process screen reader output and understand the layout of a page,
• allows people with low vision to find and read content calmly,
• lets people with motor impairments type and interact without stress,
• gives people with cognitive disabilities enough time to understand and process information,
• gives Deaf people, for whom written language is often a second language, time to read,
• offers everyone a more relaxed, stress-free experience.

In short: without time pressure, everyone can focus on the content instead of racing against the clock.

4. How to meet the criterion

The good news: it’s often easier than you think – it’s mainly about removing artificial time limits, not building new features.

Do:

• Remove automatic timeouts from forms and tests.
• Design games to be turn-based rather than time-based.
• Use links or buttons instead of automatic redirects.
• Score tests by points, not by time.
• Offer a pause function for all activities.
• Let users navigate through content themselves.

Don’t:

• Expire sessions without a compelling security reason
• Put time limits on e-learning modules or tutorials
• Advance content automatically before people have had a chance to react
• Use countdowns for everyday activities

In practice:

• Forms: No session timeouts unless needed for security – and then in a way that no data is lost after signing in again (see Re-authenticating).
• Tests: Untimed by default.
• Games: Turn-based rather than real-time.
• Online shops: The shopping cart is saved permanently.
• Content: Users control pace and progress themselves.

Technical notes:

• Avoid setTimeout() when it imposes a time limit on users.
• Replace automatic redirects (for example via <meta http-equiv="refresh">) with user decisions.
• Save input on the server or locally so nothing gets lost.

5. Why this criterion matters for businesses

Level AAA isn’t legally required – but content without time pressure still brings real benefits.

1. A wider audience

According to the WHO, around 1.3 billion people worldwide live with a significant disability. Content without time pressure makes your services usable for many of them in the first place. Older people, stressed users and anyone in a distracting environment benefit too.

2. Fewer drop-offs

Time limits are a common reason people abandon a process. Without time pressure, more people reach their goal – whether that’s an order, a registration or a learning module.

3. The legal picture

The European Accessibility Act (EAA), implemented in Germany by the Barrierefreiheitsstärkungsgesetz (BFSG), relies on the harmonised standard EN 301 549, which references WCAG 2.1 Level AA. AAA criteria like 2.2.3 are not mandatory there. If you implement them anyway, you go beyond the minimum and usually cover 2.2.1 along the way. This is general information, not legal advice.

And finally: for learning platforms, public sector portals and services aimed at older people in particular, dropping time limits is often a noticeable gain in quality.

6. The success criterion in the W3C’s words

Success Criterion 2.2.3 No Timing (Level AAA)

Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.

In short: timing must not play an essential role in any event or activity – the only exceptions are non-interactive synchronized media and real-time events.