A skip link is usually the first link on a page, often reading "Skip to main content", and hidden until it takes focus. It lets a keyboard user jump past the header and navigation instead of tabbing through every menu item on every page. It is one way to satisfy the bypass blocks rule and it is not the rule. What the standard asks for is a mechanism, and proper landmarks or a proper heading structure each satisfy it on their own, so a well-built page can conform with no skip link anywhere. Where the link still earns its place is with sighted keyboard users. Nothing in a stock browser gives them the heading and landmark jumps a screen reader user has, so without a skip link they tab the whole menu on every page view.
In practice
Eight documented routes satisfy that mechanism and only three of them are links. One jumps to the main content, one jumps past a block in the middle of a page, and one offers a set of links to each area. The other five group the block instead. ARIA landmarks marking the regions, a heading at the start of each section, headings tagged inside a PDF, a title on an iframe, or an expandable menu the user can collapse. So the audit question is never whether you have a skip link. It is whether there is any way past the repeated block, and then whether the route you have actually works.
The test everybody gives is wrong, and it fails conforming pages. "Load a page, press Tab once, a skip link should appear" assumes the skip link is the first focusable element, which nothing requires. It also reports a failure on a page that conforms through headings or landmarks instead. A cookie banner or a language switcher ahead of it does not break anything either.
Skip links are rare, and the ones that exist are often broken. In February 2026, about one home page in six across the top million had one, up slightly on the year before, and one in ten of those was broken. Either hidden in a way that made it unreachable, or pointing at a target that was not on the page. So if you already have one, the check is worth running rather than assuming.
Two carve-outs settle recurring arguments. Where a set of navigation links sits at the bottom of a page, browsers already offer a keyboard shortcut back to the top, and W3C says a skip link there may be unnecessary. And small repeated things are not blocks. A "Read more" link repeating down a listing page is not a block of content for this rule's purposes.
Federal document work gets a pass entirely. Bypass blocks is one of exactly four criteria the Section 508 standards waive for non-web documents and non-web software, so a PDF has no skip obligation.
Why it matters
The honest picture is more complicated than the way this fix is usually sold. Asked to pick the most problematic of twelve things, screen reader users put missing skip links last, and have done for fourteen years. That makes sense once you know seven in ten of them start a long page by moving through the headings, which is a better bypass mechanism they already have. What the survey does not measure is sighted keyboard-only users, who get no heading navigation from a stock browser, so the link may matter a great deal to a group nobody has counted. The rule does not exist for tidiness. Making somebody press a key forty times before reaching the content, on every page view, costs time, and for some people it causes real physical pain.
The check that works
Tab from the top of a fresh page and count the presses before you reach the main content. There is no pass mark in the rule, so the count is a signal rather than a verdict. A handful of presses tells you something is bypassing the navigation, and then the question is which mechanism it was and whether it works. Forty tells you to look for landmarks and headings before you reach for a skip link, because a page with neither has a bigger problem than this one.
Where this shows up on the site
Related terms
- Keyboard accessibilityKeyboard accessibility means every piece of functionality on the page can be operated through a keyboard interface.
- LandmarkA landmark is a named region of a page that assistive technology can list and jump straight to, and there are eight of them.
- FocusFocus is the one place on a page that is currently taking keyboard input.
- Heading structureHeading structure is the h1 to h6 outline of a page, and for screen reader users it is the map.
- Bypass blocksBypass blocks is rule 2.4.1, and it asks for one thing at Level A.
Knowing the word is the easy part.
Find out where your own site stands. The free scan checks 10 pages in a real browser against all 90 supported automated rules, separates 27 best-practice checks from its WCAG findings, and names the rule behind every result.