Rule
Timed page refresh
The page must not use a timed refresh.
- Rule
meta-refresh- WCAG 2.2
- 2.2.1 Timing Adjustable (opens in a new tab) (Level A)
- Severity
- Critical
What it checks
Looks at every <meta http-equiv="refresh">. The delay and the destination are read the way the browser reads them, so a directive the browser would ignore, such as content="+5", is ignored here too.
A refresh or redirect after a delay of up to 20 hours fails, because a meta refresh offers no way to turn the limit off, adjust it or extend it. A delay of zero with no destination fails as well: the page reloads itself over and over. An instant redirect to another address passes, and so does a delay longer than 20 hours, which the criterion allows.
The criterion also excuses a limit that is part of a real-time event or is essential. The tag cannot show either, so the finding assumes neither applies.
Example
Fails
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="refresh" content="60">
<title>Live scores</title>
</head>
<body>
<h1>Live scores</h1>
</body>
</html>
Passes
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="refresh" content="0; url=/scores/">
<title>Live scores</title>
</head>
<body>
<p><a href="/scores/">Live scores have moved</a></p>
</body>
</html>
The engine is tested against both examples.
How to fix it
Remove the timed refresh and update the content in place, or let people ask for an update. To move a page, redirect on the server or instantly with content="0; url=/new/".
Check your own pages
This rule runs in every pour audit: the browser extension, the bookmarklet, the command line and the editor. Get pour, free.