Accessibility Wiki

Don’t auto-refresh or redirect the page on a timer

Rule meta-refresh · Document, language & navigation · impact serious · Static + live

↩ Back to the rules index · WCAG cross-reference

Why it matters

A <meta http-equiv="refresh"> that reloads or redirects the page after a delay is a time limit the user cannot turn off, adjust, or extend. People using screen readers or who read slowly can lose their place or be moved away mid-task. Per SC 2.2.1, an instant (0-second) redirect to another URL is exempt (perceived as plain navigation), as are delays longer than 20 hours. A 0-second refresh with no target URL still fails: it reloads the same page in an endless loop.

How to fix

Remove the timed meta refresh. If you must redirect, do it server-side (HTTP 3xx) with no delay, or give the user a manual control to continue.

Example

✕ Fails
<head><meta http-equiv="refresh" content="30"></head>
✓ Passes
<head><meta charset="utf-8"></head>

Example

✕ Fails
<head><meta http-equiv="refresh" content="0"></head>
✓ Passes
<head><meta http-equiv="refresh" content="0; url=https://example.com/next"></head>

WCAG success criteria

2.2.1 Timing Adjustable — Level A

When a time limit is set by the content, users must be able to turn it off, adjust it, or extend it. An automatic page refresh or timed redirect (meta refresh) is a time limit users cannot control.

Understanding 2.2.1

Standards

This rule contributes to the following standards:

WCAG A EN 301 549 Section 508 Trusted Tester

Standard Criteria
Section 508 1194.22(p)
EN 301 549 9.2.2.1
Trusted Tester v5 8.a

References

Generated from the EqualWeb accessibility engine’s rule metadata. Back to top ↑