# agent infinite-scroll crawler never reached the footer - how to fix it

## TL;DR

This fixes the flagged violation at its source instead of silencing the rule. The agent's infinite-scroll crawler never reached the footer, so footer violations went unscanned. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

## The error, verbatim

```text
agent infinite-scroll crawler never reached the footer
```

## Fix it step by step

### Step 1

Add a footer sentinel: the crawl is not done until the footer landmark is present in the DOM.

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

### Step 2

Scroll until no new content loads for N consecutive scrolls, then assert the footer exists.

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

### Step 3

If the footer never appears, flag the page as unscannable instead of reporting a pass.

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

### Step 4

Re-run the crawl and confirm footer landmarks appear in the scan results.

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

- Infinite scroll without a termination check is a coverage hole.
- 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

Agent workflow guardrail; verify footer landmark in axe results.

## Variant phrasings

### agent infinite scroll crawler never reached footer

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

## Why it happens

The agent's infinite-scroll crawler never reached the footer, so footer violations went unscanned. 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_2qaZdJaN2BJDQt_7iBe73g