# Skip Link Coverage: The Metric Nobody Tracks Until the Complaint Arrives

Source: https://complymetric.com/blog/2026-11-09-skip-link-coverage-metric.html

A keyboard user opens your site, presses Tab, and lands on the navigation. They press Tab again, and they are still in the navigation. And again. And again. By the time they reach the main content, they have pressed Tab twenty times, and they have done that on every page. A skip link is the mechanism that lets them bypass the repeated block and jump straight to the content, and it is the cheapest accessibility fix on a website. Most teams do not measure it, because most teams do not test with a keyboard.

WCAG 2.2 success criterion 2.4.1, Bypass Blocks, requires a mechanism to bypass blocks of content that are repeated on multiple pages. A skip link is the standard mechanism, and it is a Level A criterion, which means it is the baseline, not a nice-to-have. The link must be visible when it receives keyboard focus, it must move focus to the main content, and it must be the first focusable element on the page.

## Why nobody tracks it

Skip link coverage is not a metric that appears in automated accessibility dashboards, because automated tools check for the presence of a skip link, not whether it works. A skip link that is present but does not move focus, or that moves focus to a container that is not focusable, or that is hidden when it receives focus, will pass an automated check and fail a real user. The gap between presence and function is the gap that causes the complaint.

The complaint is how most teams find out. A user with a motor impairment, or a screen reader user, or a power user who navigates by keyboard, contacts support and says they cannot use the site, and the support team escalates it to engineering, and engineering discovers that the skip link was never tested with a keyboard. The cost of the fix is one link and one focus target. The cost of the complaint is a lost customer and a compliance risk.

## How to measure it, properly

Measure by page template, not by page. A site with 1,000 pages and 5 templates has 5 skip links to test, not 1,000. Test each template with a keyboard: press Tab once, confirm the skip link is the first focusable element, confirm it is visible when focused, activate it, and confirm focus moves to the main content and the content is announced by a screen reader. That is a five-minute test per template, and it is the only test that matters.

Measure the failure modes, not just the presence. A skip link that is present but not visible on focus is a failure. A skip link that moves focus to a div without a tabindex is a failure, because focus does not land. A skip link that is the second focusable element, after a cookie banner or a chat widget, is a failure, because the user has to tab past the thing the skip link exists to bypass. Each of these is a distinct defect, and each has a distinct fix.

Put the test in the release process. A skip link is a one-line HTML element, and a regression is usually a template change that removes it or a CSS change that hides it. A keyboard test in the release checklist, run on every template change, catches the regression before it ships, and it takes five minutes. The alternative is finding out from a complaint, which takes weeks and costs a customer.

Skip link coverage is the metric nobody tracks until the complaint arrives. Track it before the complaint, and the complaint never arrives.

Keep reading: [Redundant Entry: The WCAG 2.2 Metric That Exposes Checkout Rework](2026-11-08-redundant-entry-metric-checkout-forms.md), [Accessible Authentication: The Metric Behind Passwordless Login](2026-11-08-accessible-authentication-metric-passwordless.md), [Keyboard trap incidents: the accessibility metric that should always read zero](2026-11-04-keyboard-trap-incident-rate-metric.md).

## Frequently asked questions

### What is a skip link?

A link that lets keyboard and screen reader users bypass repeated blocks like navigation and jump straight to the main content. It is the standard mechanism for WCAG 2.4.1, Bypass Blocks, a Level A criterion.

### Why do automated accessibility tools miss skip link failures?

They check for the presence of a skip link, not whether it works. A link that does not move focus, moves focus to a non-focusable container, or is hidden when focused will pass an automated check and fail a real user.

### How do I test a skip link?

Press Tab once, confirm the skip link is the first focusable element and visible when focused, activate it, and confirm focus moves to the main content and is announced by a screen reader. Five minutes per page template.

### Where should a skip link be on the page?

It must be the first focusable element on the page. If a cookie banner or chat widget comes first, the user has to tab past the thing the skip link exists to bypass.