What are skip links and what are they for?

Skip links are hidden or visible jump links placed at the beginning of a web page that allow keyboard and screen reader users to bypass repeated navigation elements such as the main menu and jump directly to the main content. They significantly improve the efficiency of keyboard navigation.

Do skip links have to be visible?

No. Skip links can be visually hidden and only become visible when focused via the keyboard. They must, however, be reachable and functional for keyboard users. Visible skip links are considered best practice as they are immediately apparent to sighted keyboard users as well.

Where on the page should skip links be placed?

Skip links should be placed at the very beginning of the HTML document, before the main menu and other navigation elements. This makes the link the first focusable element on the page when someone navigates using the Tab key.

Is one skip link enough for a complex website?

For most websites, a single skip link to the main content is sufficient. Complex pages with multiple content areas, search fields, or sidebars may offer additional skip links, for example to the main content, search, and navigation. Too many skip links, however, can be counterproductive.

Skip Links

Q: Are skip links required by WCAG?

Yes. WCAG 2.4.1 (Bypass Blocks, Level A) requires that a mechanism exists to bypass blocks of content that are repeated across multiple pages. Skip links are the most common and direct way to satisfy this criterion.

19.06.2026

Skip Links – Jump Directly to the Main Content for Better Accessibility

Skip links are jump links placed at the beginning of a web page that allow users to bypass repeated elements such as the main menu and jump directly to the main content. For people navigating a website by keyboard or screen reader, they make the difference between an efficient and a laborious experience: without a skip link, every page load requires tabbing through all menu items, language selectors, and other recurring elements before the actual content becomes accessible.

Skip links are one of the most fundamental yet frequently overlooked measures for keyboard accessibility. They are technically straightforward to implement but have a significant impact on the accessibility of a website for all users who do not use a mouse. Voice control software also benefits from correctly implemented skip links.

The European Accessibility Act (EAA) has required many businesses across the EU to meet WCAG 2.1 Level AA since 28 June 2025. Skip links are addressed by WCAG 2.4.1 as a Level A requirement, meaning they belong to the baseline of accessibility compliance.

Skip Links at a Glance

✓ Definition: Jump links at the top of the page to bypass repeated navigation elements
✓ WCAG criterion: 2.4.1 – Bypass Blocks, Level A (legal minimum requirement)
✓ Target groups: Keyboard users, screen reader users, voice control users
✓ Visibility: Can be visually hidden and revealed on keyboard focus
✓ Placement: First focusable element in the HTML, before the main menu

Why Skip Links Are Essential for Navigation

Imagine navigating a website exclusively by keyboard. On every new page, you first have to tab through the entire main menu, perhaps 10, 15, or 20 elements, before reaching the main content. This is not only inefficient but effectively excludes people with motor impairments when there is no way to bypass these recurring elements.

A skip link solves this problem directly: as the first focusable element at the top of the page, it offers the possibility to jump straight to the main content with a single keystroke. The link is typically hidden visually and only becomes visible when focused with the Tab key. For sighted keyboard users, it should then be displayed clearly and prominently.

Technical Implementation of Skip Links

Implementing a skip link is technically straightforward. The link is placed as the first element inside the <body> tag and points to the ID of the main content area. The accessible link text should clearly describe its destination, for example "Skip to main content" or "Bypass navigation". The target element must be reachable via id and, if necessary, made focusable with tabindex="-1" so that focus is correctly set when the link is activated.

✓ Position: First element inside <body>, before header and menu
✓ Target ID: Points to id="main-content" or equivalent landmark region
✓ Visible on focus: CSS :focus reveals the link, typically as a coloured banner in the top left
✓ Link text: Clear and descriptive, e.g. "Skip to main content" or "Bypass navigation"

Skip Links and WCAG Operability

Skip links are part of the WCAG principle of Operability and fall under guideline 2.4 "Navigable". The associated criterion 2.4.1 is one of the few Level A criteria that directly address the efficiency of navigation. It requires that a mechanism exists for users to bypass blocks of content that are repeated across multiple pages.

Skip links are the most direct way to satisfy this criterion. WCAG also accepts clearly structured landmark regions (main, nav, aside) in combination with a screen reader as an alternative. In practice, implementing both together provides the most robust solution, as skip links also benefit sighted keyboard users who do not use a screen reader.

Common Mistakes When Implementing Skip Links

Skip links are technically simple but are still frequently implemented incorrectly. The most common problems:

✓ Link not focusable: If the skip link is hidden using display: none instead of a CSS clip technique, it cannot be reached by keyboard users
✓ Target not focusable: If the target element (e.g. <main>) has no tabindex, the browser may not correctly set focus when the link is activated
✓ No visible focus indicator: The link does not appear visually on focus, making it invisible to sighted keyboard users
✓ Non-descriptive link text: Generic texts like "Click here" do not communicate where the link leads

SiteCockpit Solution

easyMonitoring: Detect missing skip links and WCAG 2.4.1 violations

easyMonitoring automatically checks your website for missing or broken skip links and further violations of WCAG 2.4 (Navigable): non-focusable skip link targets, missing landmark regions, and insufficient focus indicators. You receive a score from 0 to 100, plus a detailed report with exact locations and concrete guidance on how to fix each issue.

Discover easyMonitoring →

Frequently Asked Questions about Skip Links

Do regular users ever see skip links?

Usually not, as skip links are hidden by default and only appear when focused via the Tab key. This is intentional: they do not disrupt the visual design but remain immediately accessible to keyboard users. Some websites display skip links permanently, which is considered best practice as it immediately signals to sighted keyboard users that accessibility has been considered.

Do I need skip links if I already use ARIA landmarks?

ARIA landmarks such as <main>, <nav>, and <aside> allow screen reader users to jump directly to page regions. They do not, however, replace a skip link for sighted keyboard users who do not use a screen reader. Both measures complement each other and together provide the broadest coverage for all keyboard users.

How many skip links should a website have?

For most websites, a single skip link to the main content is sufficient. Complex pages with multiple important areas, such as a prominent search field or a long sidebar, may offer additional skip links. As a rule of thumb: as few as necessary, but enough that all key content areas are directly reachable without having to tab through the menu every time.

Do skip links work in single-page applications (SPAs)?

In SPAs, particular care is required. Since page content is loaded dynamically without a full page reload, focus must be actively managed on route changes. Skip links must be available again as the first focusable element after each navigation event. Without explicit focus management, keyboard users lose their orientation when the page content changes.

Does your website have working skip links?

Have your website automatically checked for missing skip links and other WCAG navigation violations. easyMonitoring delivers a detailed report with precise locations so you can fix issues efficiently.

Try for free

External Sources

Discover all lexicon entries