# agent skip-link injection broke the sticky header layout - how to fix it

## TL;DR

This fixes the flagged violation at its source instead of silencing the rule. The agent's injected skip link broke the sticky header layout by pushing content down. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

## The error, verbatim

```text
agent skip-link injection broke the sticky header layout
```

## Fix it step by step

### Step 1

Position the skip link as fixed at the top with a high z-index so it overlays instead of pushing layout.

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

### Step 2

Offset it below the sticky header height so it does not cover the header on focus.

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

### Step 3

Test with the header stuck and unstuck; the link must appear without shifting content.

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

### Step 4

Re-run axe bypass to confirm the link still works.

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 skip link that breaks layout gets deleted by the next designer; make it layout-neutral.
- 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 with axe bypass.

## Variant phrasings

### agent skip link injection broke sticky header layout

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

## Why it happens

The agent's injected skip link broke the sticky header layout by pushing content down. 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_EVwAMoWnYPknD5BUnAKuXg