accessibility Skill
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. Published by microsoft in vscode.
What is accessibility Skill?
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. Published by microsoft in vscode. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use accessibility Skill
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode
- Skill file: .github/skills/accessibility/SKILL.md
What it does
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.
Skill instructions
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): 1. An Accessibility Help Dialog — opened via the accessibility help keybinding when the feature has focus. 2. An Accessible View — a plain-text read-only editor that presents the feature's content to screen reader users (when
Explore related resources
Frequently asked questions
What is accessibility?
accessibility is a open-source AI agent skill with Copy skill directory. Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI.
Who is accessibility best for?
accessibility is best for reusing agent instructions, scripts, and references, design and media workflows.
How do I install accessibility?
Install or run accessibility using Copy skill directory. Check accessibility for the latest setup command.
Is accessibility actively maintained?
accessibility may need a closer maintenance check before production use.
Auto-fetched from GitHub.
