Timed page refreshes and redirects must not occur without giving users control. Automatically refreshing or redirecting a page, whether through <meta http-equiv="refresh"> or other mechanisms, can interrupt users while they are reading, navigating, or completing a task. When these changes occur without user initiation or the ability to pause or adjust timing, they create accessibility barriers.
This issue is not about banning a specific HTML element. It is about unexpected, time-based changes that users cannot control.
WCAG Success Criteria
Improper use of timed refreshes can result in failures of the following WCAG success criteria:
2.2.1 Timing Adjustable (Level A)
Users must be able to pause, stop, or adjust time limits unless the timing is essential.
3.2.5 Change on Request (Level AAA)
Changes of context must not occur without user request, unless the change is essential.
A timed refresh or redirect only fails WCAG when it removes user control or causes an unexpected change of context.
Why This Matters
Users do not expect a page to refresh or redirect automatically.
When a timed refresh occurs without warning or control:
- Keyboard focus is reset to the top of the page
- Screen readers restart reading from the beginning
- Users may lose their place or entered data
- Tasks can be interrupted or abandoned
For users with cognitive disabilities, unexpected refreshes are disorienting.
For screen reader and keyboard users, they can make content feel unstable or unusable.
Accessibility requires predictable interaction and user control over timing.
Understanding Meta Refresh
<meta http-equiv="refresh"> is a technique, not a WCAG failure by itself.
It is commonly used for:
- Redirecting users after a delay
- Periodically refreshing content
- Session timeout handling
Problems arise when it is used to:
- Refresh or redirect without user initiation
- Impose a time limit without pause or extension
- Change context unexpectedly
WCAG evaluates the effect on users, not the presence of a specific tag.
Immediate Redirects vs Timed Refreshes
It is important to distinguish between two common uses:
Immediate Redirects (0 seconds)
- Often used to move users to a new URL
- Should be handled using server-side HTTP redirects instead
- Meta refresh is not recommended for this purpose
Delayed Refreshes or Redirects
- Introduce a time-based change
- Must comply with SC 2.2.1 Timing Adjustable
- Must not cause an unexpected change of context under SC 3.2.5
Common Accessibility Failures
Timed refreshes fail accessibility requirements when:
- Users cannot pause, stop, or extend the refresh
- A redirect occurs without a user request
- Focus is reset unexpectedly during interaction
- Screen reader users are forced to restart reading
- Content updates interrupt form entry or navigation
The problem is loss of control, not the refresh mechanism itself.
Who This Helps
Ensuring user control over timed changes supports:
- Screen reader users
- Keyboard-only users
- Users with cognitive or learning disabilities
- Users who read slowly or require more time
- Users with attention or memory impairments
Stable, user-driven interaction benefits all users.
How to Fix the Problem
Prefer Server-Side Redirects
If the goal is navigation to another page, use HTTP redirects instead of meta refresh.
Avoid Automatic Refresh Without Control
Do not refresh or redirect content automatically unless users can:
- Pause the refresh
- Extend the time
- Turn it off
Use JavaScript Responsibly
If content must update dynamically:
- Use JavaScript rather than meta refresh
- Provide visible, accessible controls for timing
- Do not reset focus unexpectedly
Rule Description
Timed page refreshes or redirects must not occur without user control. Any time-based change must allow users to pause, stop, or adjust timing and must not cause unexpected changes of context.
The Algorithm
- Identify any automatic refresh or redirect behaviour
- Determine whether the change is time-based
- Check whether users can:
- Pause the change
- Adjust the timing
- Prevent it entirely
- Verify that no change of context occurs without user request
- If users lack control, the criterion fails
How to Test This
- Observe whether the page refreshes or redirects automatically
- Confirm users are informed before any timed change
- Verify controls exist to pause or stop the behaviour
- Check that focus and reading position are preserved
- Test with keyboard navigation and a screen reader
Wrapping Up
Timed refreshes are not inherently inaccessible, but uncontrolled timing is. WCAG does not ban meta refresh or automatic updates. It requires that users remain in control of time-based behaviour and are not subjected to unexpected changes of context. If content refreshes, redirects, or updates without user consent or adjustment, it fails accessibility requirements, not because of the technique used, but because it removes user agency.
Accessibility is not about forbidding tools.
It is about ensuring users decide when content changes.
