# axe-core bypass error: no skip link or bypass block - how to fix it

## TL;DR

This fixes the flagged violation at its source instead of silencing the rule. The page has no skip link or other bypass block, so keyboard users must tab through the entire nav on every page. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

## The error, verbatim

```text
axe-core bypass error: no skip link or bypass block
```

## Fix it step by step

### Step 1

Add a skip link as the first focusable element that jumps to the main content region.

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

### Step 2

Style it to appear on focus; visually-hidden-until-focused is the standard pattern.

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

### Step 3

Alternatively, provide a proper heading structure and landmarks so assistive tech can jump by section.

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

### Step 4

Tab from the address bar and confirm the skip link appears first and moves focus to main.

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 points at a non-focusable target does nothing; give the target tabindex -1.
- 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 bypass, WCAG 2.4.1).

## Variant phrasings

### axe bypass: page has no skip link or bypass block

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

## Why it happens

The page has no skip link or other bypass block, so keyboard users must tab through the entire nav on every page. 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_CWdGcqTEvEJWd4Uxi3md1Q