# Skip Link

A skip link lets keyboard users bypass repeated interface blocks and move directly to an important page region.

- Type: artifact
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-19
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/skip-link/>)

## What it means

A skip link is an early navigation link targeting a meaningful destination, often the main content after repeated headers and menus. It reduces repeated traversal for keyboard users. Semantic landmarks help many assistive-technology users navigate, but they do not provide every keyboard user with the same direct shortcut.

## Why it matters

Tabbing through a large menu on every page makes even a simple reading task slow. A working skip link gives users control over repeated navigation without removing that navigation for people who need it.

## When to use it

Use it on pages with repeated blocks before primary content, especially large navigation structures. Keep the destination meaningful and the number of shortcuts modest. A simple page without repeated blocks may not need a dedicated skip link.

## How it works

1. Identify repeated blocks and the useful destination after them.
2. Place a clearly named link early in keyboard order.
3. Make the link visible when focused, with sufficient contrast.
4. Ensure activation moves the navigation position to the target, not merely the visual scroll.
5. Verify that the next Tab continues sensibly and that sticky headers do not hide the destination.

## A practical example

A documentation portal places “Skip to article” before its large header. A keyboard reader activates it and continues from the article rather than tabbing through twenty navigation links on every page. Testing reveals a sticky header obscures the target, which the team corrects.

## Where it breaks

A skip link does not repair illogical focus order or missing headings. Target behavior can vary by implementation, and a hidden link that never becomes visible is hard for sighted keyboard users to discover. Dynamic navigation can also invalidate target identifiers.

## Common mistakes

- Hiding the link from keyboard access as well as sight.
- Scrolling visually while leaving keyboard navigation at the header.
- Linking to a missing or duplicated destination identifier.

## Sources

1. [Understanding Success Criterion 2.4.1: Bypass Blocks](<https://www.w3.org/WAI/WCAG22/Understanding/bypass-blocks.html>) — W3C Web Accessibility Initiative · Standards guidance
2. [Skip Navigation Links](<https://webaim.org/techniques/skipnav/>) — WebAIM · Accessibility guidance

## Related topics

- [Keyboard Accessibility](<https://wiki.soroush.uk/topic/keyboard-accessibility/>)
- [Focus Order](<https://wiki.soroush.uk/topic/focus-order/>)
- [Semantic HTML](<https://wiki.soroush.uk/topic/semantic-html/>)
