Context Menu

Preview

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.

npx shadcn@latest add https://ds.interlace.tools/r/context-menu.json

npx shadcn@latest add @interlace/context-menu

Import

14 named exports — pull the parts you need.

import { ContextMenu, ContextMenuCheckboxItem, ContextMenuCompose, ContextMenuContent, ContextMenuGroup, ContextMenuItem, ContextMenuLabel, ContextMenuPortal, ContextMenuRadioGroup, ContextMenuRadioItem, ContextMenuSeparator, ContextMenuShortcut, ContextMenuTrigger, MIN_VIEWPORT } from '@/components/ui/context-menu';

Anatomy

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

ContextMenu                       (Root — Base UI manager)
    ├─ ContextMenuTrigger          (the right-clickable surface)
    └─ ContextMenuContent          (wraps Portal + Positioner + Popup
                                    internally — do NOT nest it in
                                    ContextMenuPortal, that portals twice)
        ├─ ContextMenuGroup → ContextMenuLabel + ContextMenuItem
        ├─ ContextMenuItem
        ├─ ContextMenuSeparator
        ├─ ContextMenuCheckboxItem
        └─ ContextMenuRadioGroup → ContextMenuRadioItem
`ContextMenuPortal` is exported only for the `container=` override (render
the popup into a specific node instead of `document.body`); it is not part
of the normal tree. `ContextMenuLabel` is `Menu.GroupLabel` and MUST sit
inside a `ContextMenuGroup` — outside one it throws on open.

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.

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

Owned by @base-ui/react/context-menu — focus trapping, dismissal and typeahead come from the headless primitive, not from us.

Focus ring (WCAG 2.2 SC 2.4.13)

Not focusable — no focus indicator required.

Reduced motion

No animation to gate.

ARIA in the source

• role="group"
• role="menu"

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.

Dependencies

Base UI primitive

@base-ui/react/context-menu

Lucide icons

• CheckIcon
• CircleIcon

NPM dependencies

• @base-ui/react
• lucide-react

Registry dependencies

• @interlace/theme
• @interlace/cn

Source

The full implementation — components/ui/context-menu.tsx once installed.

'use client';

import * as React from 'react';

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

/**
 * @interlace/ui — ContextMenu
 *
 * Right-click / long-press menu. Wraps `@base-ui/react/context-menu`
 * (same Menu compositional API as DropdownMenu, just with a Root that
 * handles right-click / long-press / Shift+F10 as the open gesture).
 *
 * For the standard click-button-to-open pattern, use `DropdownMenu`.
 * Use ContextMenu only when consumers expect a true OS-level
 * right-click affordance (file lists, editor canvases, image grids).
 *

…437 more lines…

Registry JSON

The raw registry record — what the shadcn CLI fetches.