Avoid timed refresh/redirects
WCAG 2.2.4
Interruptions Accessibility isn’t only about avoiding violations — it’s about ensuring your product can be used confidently by everyone. This guide explains the principle of this rule, shows what goes wrong in real-world code, and provides a verified fix that meets WCAG and the European Accessibility Act (EAA).
Why this matters and how to fix it
Why this matters
Unexpected updates and redirects interrupt users and can break assistive technology workflows.
How to fix this issue
Avoid automatic refresh. Use non‑intrusive notifications and let users choose when to update.
Automated detection · Manual review recommended
Developer guidance
Centralize update banners with a standard component; never trigger auto refresh in production code.
Code examples
Incorrect Implementation
<meta http-equiv="refresh" content="600; url=/news">
Correct Implementation
<!-- Do not use meta refresh; provide manual refresh -->
Trusted by organizations across Europe working toward WCAG and EAA conformance