accessibility
Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/microsoft/vscode /tmp/vscode && ln -s /tmp/vscode/.github/skills/accessibility ~/.claude/skills/accessibilityFrom README
When to Use This Skill Use this skill for any VS Code feature work that introduces or changes interactive UI. Use this skill by default for new features and contributions, including when the request does not explicitly mention accessibility. Trigger examples: "add a new feature" "implement a new panel/view/widget" "add a new command or workflow" "new contribution in workbench/editor/extensions" "update existing UI interactions" Do not skip this skill just because accessibility is not named in the prompt. When adding a new interactive UI surface to VS Code — a panel, view, widget, editor overlay, dialog, or any rich focusable component the user interacts with — you must provide three accessibility components (if they do not already exist for the feature): An Accessibility Help Dialog — opened via the accessibility help keybinding when the feature has focus.