Accessibility

This is the primary accessibility skill for VS Code development work, and it's required for any new feature or UI contribution. It walks you through the three core components you need when adding interactive surfaces: an accessibility help dialog that documents keyboard shortcuts and screen reader usage, an accessible view that presents visual content as plain text, and a verbosity setting. It also covers the broader strokes like ARIA announcements, keyboard navigation, and keeping existing help dialogs updated when you modify features. The guidance is prescriptive and assumes you'll implement accessibility by default, not as an afterthought. If you're building or updating anything users interact with in VS Code, you'll need this.

skills.sh installs: 3.2K
GitHub stars: 195.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add microsoft/vscode --skill accessibility --agent claude-code

Installs into .claude/skills of the current project.

Files

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):

SKILL.md on GitHub