# agent screenshot diff flagged intentional redesigns as violations - how to fix it

## TL;DR

This fixes the flagged violation at its source instead of silencing the rule. The agent's screenshot diff flagged intentional redesigns as violations because the baseline was stale. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

## The error, verbatim

```text
agent screenshot diff flagged intentional redesigns as violations
```

## Fix it step by step

### Step 1

Regenerate the visual baseline from the approved branch before the agent diffs.

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

### Step 2

Scope diffs to the PR's changed routes instead of the whole site.

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

### Step 3

Require human sign-off on baseline updates; the agent should never silently re-baseline.

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

### Step 4

Re-run the diff against the fresh baseline.

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

- Screenshot diffs detect change, not violations; pair them with axe for the actual a11y verdict.
- 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; baseline pinned per release branch.

## Variant phrasings

### agent screenshot diff flagged redesign as violations

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

## Why it happens

The agent's screenshot diff flagged intentional redesigns as violations because the baseline was stale. 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_dPc5vH_4S1hmc4FIyx2ZxQ