# axe-core meta-refresh error: timed refresh fails accessibility - how to fix it

## TL;DR

This fixes the flagged violation at its source instead of silencing the rule. A meta refresh reloads or redirects the page on a timer, yanking control away from the user. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

## The error, verbatim

```text
axe-core meta-refresh error: timed refresh fails accessibility
```

## Fix it step by step

### Step 1

Remove the meta refresh tag from the page head.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 2

For redirects, use a server-side redirect (3xx) instead of a timed client refresh.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 3

If content must update, offer a manual refresh button the user controls.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 4

Re-run axe to confirm.

Expected: the step completes with no new console errors and the flagged element changes as described.

## When to use this skill

- Your scan report lists this exact rule or failure
- You are clearing automated accessibility failures before release or audit
- A CI accessibility gate is red because of this item

## When NOT to use this skill

- A 0-second redirect is still flagged; do it server-side.
- The issue only appears in manual screen-reader testing and no automated rule flags it
- You are doing a full manual WCAG audit; this skill covers one automated check

## Compatibility

axe-core 4.8+ (rule meta-refresh, WCAG 2.2.1 / 3.2.5).

## Variant phrasings

### axe meta-refresh: timed refresh fails accessibility

Same underlying issue and the same fix. Searchers phrase it different ways; the remediation does not change.

## Why it happens

A meta refresh reloads or redirects the page on a timer, yanking control away from the user. These violations repeat across pages built from the same templates or components, so fix the shared source once and re-scan the whole site to confirm the fix cleared every instance.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_2chxzBDTqE4CLhRsXA0tsw