Accessibility
microsoft/vscodeEvery new feature in VS Code needs to be accessible. This means people who use screen readers or only a keyboard can still use it. Accessibility is required for all new work and updates to existing UI.
This skill covers help dialogs, accessible views, keyboard navigation, and ARIA labels. It also includes verbosity settings and signals. You must add these when building new panels, views, or widgets.
Updates to existing features also need care. You must update the help dialog so screen reader users know about new commands. This makes sure everyone can work with VS Code.
Add Accessibility skill to your workflow
Global
mkdir -p ~/.claude/skills/accessibilityProject
mkdir -p .claude/skills/accessibilitySource Repository
More Accessibility & Localization Claude Code Skills
Accessibilityaddyosmani/web-quality-skills
Audit and improve web accessibility following WCAG 2.2 guidelines for inclusivity
Fixing Accessibilityibelick/ui-skills
Audit and fix HTML accessibility issues for a more inclusive web
Accessibility Compliancewshobson/agents
Build inclusive interfaces that everyone can use with ease and confidence
Wcag Audit Patternswshobson/agents
Audit websites for WCAG 2.2 compliance and fix accessibility violations
Next Intl Add Languagegithub/awesome-copilot
Easily add a new language to your Next.js internationalized app
Vscode Ext Localizationgithub/awesome-copilot
Localize VS Code extensions correctly for all languages using official best practices
Flutter Improving Accessibilityflutter/skills
Make your Flutter app usable for everyone with accessibility features
Screen Reader Testingwshobson/agents
Test websites with screen readers for full accessibility and user inclusion