Skip Link

The "jump to main content" link that satisfies WCAG 2.4.1 (Bypass Blocks): an `sr-only` anchor that pops into the top-left corner the moment it takes focus, letting a keyboard user step past the header and nav in one Tab.

a11yserver320pxuiv1.1.0

Preview

Skip Link — live renderprimitives-skiplink--default

Rendered from the story the storybook (a11y) CI gate runs axe against — the preview can't show something that hasn't been verified.

Install

Two equivalent paths — the URL works in any shadcn-CLI setup; the alias works once you've registered @interlace in your components.json.

Via shadcn URL
npx shadcn@latest add https://ds.interlace.tools/r/skip-link.json
With the @interlace alias
npx shadcn@latest add @interlace/skip-link

Behavior

What this component does — the keyboard path, the measured colour, the text equivalent and the states it can be in. Every figure below is read out of the test or the source that enforces it by scripts/build-behavior-map.mjs, so nothing here can outlive the gate that keeps it true.

4 steps, 1 key press — replayed on every PR by the play function of KeyboardFlow. Axe cannot press a key, so this — not the a11y scan — is what proves the component is operable without a mouse.

  1. 1At rest the link is clipped out of sight
  2. 2The skip link is the first tab stop
  3. 3Focus makes it visible (not clipped to 1px)
  4. 4Its target exists and can receive focusEnter

Every semantic colour pair this component's own source uses, measured against the shipped hexes in all 4 theme × scheme combinations. The tightest is ring on background at 8.39:1 (harbor · light), against a floor of 3:1.

Measured WCAG contrast ratios per token pair and theme
PairinterlacelightinterlacedarkharborlightharbordarkFloor
ring on backgroundfocus ring (SC 2.4.13)8.80:111.79:18.39:110.03:13.0:1SC 1.4.11
ring on cardfocus ring inside a card8.80:110.92:18.86:19.10:13.0:1SC 1.4.11
foreground on backgroundbody copy19.65:116.97:117.74:116.19:14.5:1SC 1.4.3

Text pairs are held to 4.5:1 (WCAG 2.2 SC 1.4.3); borders, rings and chart axes to 3:1 (SC 1.4.11 non-text). Bold is the worst cell in the row — the one a brand fork has to keep an eye on.

Where it renders, how narrow it survives, and whether its lines are inside the coverage gate — three answers a consumer needs before the paste, not after the bug.

Render boundary
server component

Renders during SSR / RSC with no hydration cost. It can be imported from a server component without pulling the page into the client.

Minimum viewport
MIN_VIEWPORT = 320

Declared, not assumed. Below 320 CSS px the preflight contract draws a dev-mode outline — how to switch it on.

Coverage gate
100% × 4

Inside the v8 gate: lines 100, statements 100, functions 100, branches 100. A threshold under 100 only records how much you stopped caring, so there isn't one.

History

This component is at v1.1.0, first shipped in @interlace/ui 1.0.0. The version is stamped as a banner into the file the install writes, so the copy in your tree says which one you have — compare it with the number above before deciding whether to re-run the install.

No release note names this component yet. It shipped with the release above and has not changed since — see the full changelog for what moved elsewhere in the DS.

Import

2 named exports — pull the parts you need.

Public API
import { MIN_VIEWPORT, SkipLink } from '@/components/ui/skip-link';

Anatomy

Extracted from the primitive's JSDoc header. The source is the only documentation that can't drift.

SkipLink                          (anchor — data-min-viewport=320)
    └─ children                     (default: "Skip to main content")

API reference

Parsed from the type declarations in the source — the same file the install writes into your tree, so this table can't drift from the component you get.

SkipLinkProps

Also accepts every <a> attribute.

PropTypeDescription
hrefstringHash target for the skip action. Defaults to `#main` — pair with a `<main id="main" tabIndex={-1}>` so focus moves into the content region, not just the scroll position.

Accessibility

Every story for this component is rendered headlessly and checked with axe-core (wcag2aa, wcag22aa, best-practice, ACT) on every PR. That gate has no continue-on-error, so what ships has zero known violations.

What follows is what static analysis can see. Axe cannot press a key and never sees an overlay open, so the operable-without-a-mouse claim lives in Behavior instead, where the keyboard path is replayed step by step.

Focus + keyboard behaviour
Native element semantics — no interaction layer to get wrong.
Focus ring (WCAG 2.2 SC 2.4.13)
Inherited from the preflight focus contract shipped in @interlace/theme.
Reduced motion
No animation to gate.
ARIA in the source
None — semantics come from the element or the Base UI primitive rather than hand-written ARIA.

Examples

3 more states from the same story file.

R-rule compliance

Every primitive in @interlace/ui models to the portable 26-rule floor enforced by the componentApi ESLint preset. The cells below pin exactly where each rule applies in this file.

RuleConceptWhere
R4Extends native el`React.ComponentProps<'a'> & SkipLinkProps`
R6data-slot on root`data-slot="skip-link"`
R7className merged + ...rest`cn(BASE, className)` + `{...props}`
R8No isXxxn/a — no boolean variants
R14Declares min viewport`data-min-viewport={String(MIN_VIEWPORT)}` + exported const
R18Tailwind onlyZero inline `style`; utility classes only
R19Tokens onlybg-background / text-foreground / focus-visible:ring-ring
R20AA contrastVisible state uses semantic tokens that clear AA / AAA
R25Server componentNo hooks → no `'use client'`
R26A11y from native el`<a href>` is the native element; focus + activation inherit

Minimum viewport

This primitive declares MIN_VIEWPORT = 320 CSS px (DESIGN_PRINCIPLES #14). When mounted in a container narrower than this, the preflight contract draws a dev-mode outline so the regression is visible during local development.

Opt-in to the dev-mode warning
<body data-interlace-dev>...</body>

Add the data-interlace-dev attribute to the body in development builds only — preflight then outlines any primitive whose container is below its declared data-min-viewport.

Dependencies

Base UI primitive
Native / no Base UI dependency
Lucide icons
none
NPM dependencies
none
Registry dependencies

Source

The full implementation — components/ui/skip-link.tsx once installed.

92 lines · TypeScript
import * as React from 'react';

// @interlace/skip-link v1.1.0 — Interlace design system.
// Docs, props and live preview: https://ds.interlace.tools/c/skip-link
// What changed since: https://ds.interlace.tools/c/skip-link#history
// Generated banner — keep it, the upgrade diff reads this version.

/**
 * @interlace/ui — SkipLink
 *
 * The "jump to main content" link that satisfies WCAG 2.4.1 (Bypass Blocks):
 * an `sr-only` anchor that pops into the top-left corner the moment it takes
 * focus, letting a keyboard user step past the header and nav in one Tab.
 *
 * It only earns that if it is the first focusable element in the document.
 * A mouse user never sees it.
 *
 * Pair this with a `<main id="main">` (or whichever target you point at).
 * The target MUST be focusable (set `tabIndex={-1}` on `<main>` so the skip
 * action moves focus into it, not just the scroll position).

…72 more lines…

Registry JSON

The raw registry record — what the shadcn CLI fetches.