skills.rest
aadorian
aadorianCOMMUNITY
Explore all skills by this author →
GitHub

accessibility

Review VS Code UI features for accessibility requirements like ARIA labels and keyboard operability.

Updated Mar 28, 2026
Search Tags:#vscode#accessibility#screen reader#keyboard navigation#aria#copilot skills#accessible view
One-click install
npx skills add https://github.com/aadorian/VSCode_Readme --skill accessibility-aadorian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/aadorian/VSCode_Readme/tree/main/education/engineering-tooling/github/copilot-skills/accessibility
Command: npx skills add https://github.com/aadorian/VSCode_Readme --skill accessibility-aadorian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design and update VS Code features so they remain usable for screen reader users, keyboard users, and anyone relying on accessibility settings or announcements.

Core Features & Use Cases

  • Accessibility Help Dialogs: Document the feature’s actions, keybindings, and screen reader guidance.
  • Accessible Views: Provide plain-text read-only representations of rich UI content when visual output is not directly accessible.
  • Verbosity and Announcements: Add the settings, focus handling, ARIA labels, live-region messages, and signals needed for clear, discoverable interactions.
  • Use Case: You are adding a new chat panel, editor overlay, or custom widget and need to make sure it has the required accessibility behavior from the start.

Quick Start

Use the accessibility skill to review a VS Code feature and identify the help dialog, accessible view, verbosity setting, keyboard navigation, and ARIA updates it needs.

Frequently Asked Questions about accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make a VS Code extension accessible for screen reader users?▼

Make VS Code extensions accessible by adding accessibility help dialogs, accessible views for visual content, verbosity settings, localized ARIA labels, keyboard operability, and focus restoration to interactive surfaces.

What is an accessible view in VS Code and when do I need one?▼

An accessible view in VS Code provides a plain-text, read-only representation of rich UI content when visual output is not directly accessible. You need one for panels, editors, or custom widgets with graphical information.

How do I add accessibility help dialogs to a new chat panel or custom widget?▼

Add accessibility help dialogs to document the feature's actions, keybindings, and screen reader guidance. This ensures clear, discoverable interactions for keyboard and screen reader users navigating new chat panels or widgets.

Why does my VS Code feature need verbosity settings and ARIA labels?▼

VS Code features need verbosity settings and localized ARIA labels to provide live-region messages and focus handling, ensuring clear announcements and discoverable interactions for users relying on accessibility settings.

Does my VS Code walkthrough or notification require keyboard operability and focus restoration?▼

Yes, new and updated interactive surfaces in VS Code, including walkthroughs, notifications, and dialogs, require keyboard operability and focus restoration to remain usable for keyboard-only and screen reader users.

What's the best way to review a VS Code feature for accessibility compliance?▼

Review a VS Code feature for accessibility by identifying the required help dialog, accessible view, verbosity setting, keyboard navigation, and ARIA updates it needs from the start to ensure full screen reader support.

Related Skills

Explore More Software Engineering Skills→
joshsmithxrmjoshsmithxrm
5

ext-verify

Automate VS Code extension webview UI tests with Playwright Electron.

Community
Advanced
leboncoinleboncoin
92

check-accessibility

Automate WCAG 2.1 AA accessibility testing of Spark UI components with Playwright.

Official
Intermediate
darwinboaventuradarwinboaventura

accessibility

Implement accessible UI guidelines for VS Code interactive surfaces.

Community
Advanced
Community-AccessCommunity-Access
387

Keyboard Navigator

Audit keyboard navigation and focus management against WAI-ARIA and WCAG standards.

Official
Advanced