# agent scanned desktop viewport only: missed mobile target-size failures - how to fix it

## TL;DR

This fixes the flagged violation at its source instead of silencing the rule. The agent scanned at desktop viewport only and missed mobile target-size failures. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

## The error, verbatim

```text
agent scanned desktop viewport only: missed mobile target-size failures
```

## Fix it step by step

### Step 1

Scan at a mobile viewport too, e.g. 390 by 844, as a second pass.

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

### Step 2

Compare violation sets across viewports; target-size rules differ by layout.

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

### Step 3

Report per-viewport results; a desktop pass is not a mobile pass.

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

### Step 4

Add the mobile pass to the agent's standard scan script.

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

- Responsive layouts hide and reveal different violations per breakpoint.
- 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; axe target-size at mobile viewport.

## Variant phrasings

### agent scanned desktop viewport only missed mobile target size

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

## Why it happens

The agent scanned at desktop viewport only and missed mobile target-size failures. 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_UIzJnK7jwhNc2nmOYXki_w