Avoid timed refresh/redirects under 20 hours

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 time limits can cause loss of data and disorientation, especially for users who need more time.

How to fix this issue

Avoid timed redirects. If time limits exist, provide a way to turn off, adjust, or extend them with clear notice.

Automated detection · Manual review recommended

Developer guidance

Ban `meta refresh` in linting. Provide a reusable countdown/extend pattern for timeouts.


Code examples

Incorrect Implementation

<meta http-equiv="refresh" content="5; url=/dashboard">

Correct Implementation

<!-- Avoid timed redirects; show a link or button instead -->
eu icon getwcag

Trusted by organizations across Europe working toward WCAG and EAA conformance