What This Rule Checks
Meta refresh tags can automatically redirect users to another page after a set period. This can cause significant issues for users who rely on assistive technologies, as they may not have enough time to read or interact with the page before being redirected. For users with cognitive disabilities or those using screen readers, automatic redirects create confusion and interrupt the user experience. Providing manual control over redirects ensures that all users can interact with content at their own pace.
Who Is Affected
This issue primarily affects: Blind users, who rely entirely on screen readers or braille displays to navigate and interact with content; Deafblind users, who rely on braille displays and cannot access visual or auditory content; Mobility users, who navigate using keyboards, switches, voice control, or other assistive input devices.
Why This Matters
Timed redirects disorient screen reader users who may not have finished reading the page. Users with cognitive disabilities need more time to process content. WCAG 2.2.1 (Timing Adjustable) and 3.2.5 (Change on Request) address this.
How to Fix
To avoid accessibility issues, eliminate the use of <meta http-equiv=”refresh”> tags for redirects. Instead, provide clear instructions or buttons that users can click to initiate the redirection.
Code Examples
<!-- Auto-redirect after 30 seconds -->
<meta http-equiv="refresh" content="30;url=/new-page">
Copy
<!-- Server-side redirect (HTTP 301/302) -->
<!-- No meta refresh needed -->
<!-- If client-side redirect is necessary, use JavaScript with warning -->
<script>
// Show warning, then redirect after user acknowledgment
if (confirm("This page has moved. Redirect now?")) {
window.location.href = "/new-page";
}
</script>
Copy
Common Mistakes to Avoid
- Using meta refresh for page redirects instead of server-side HTTP redirects.
- Setting refresh intervals that are too short for users to read the content.
- Not providing a way for users to cancel or extend the refresh timer.
Tip: Page-level metadata and settings affect the entire browsing experience. Language declarations, viewport settings, and page titles are foundational to accessibility and affect every user on every page load.
Related WCAG Criteria
- 2.2.1: Timing Adjustable