accessibility

Standardize accessibility guidelines for VS Code UI features.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/DevFlex-AI/devonz-editor-web --skill accessibility-devflex-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/DevFlex-AI/devonz-editor-web/tree/main/.github/skills/accessibility
Command: npx skills add https://github.com/DevFlex-AI/devonz-editor-web --skill accessibility-devflex-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility guidelines for VS Code features — covers accessibility help dialogs, accessible views, verbosity settings, accessibility signals, ARIA alerts/status announcements, keyboard navigation, and ARIA labels/roles. Applies to both new interactive UI surfaces and updates to existing UI features. Use when creating new UI or updating existing UI features.

Core Features & Use Cases

  • Accessibility Help Dialog: ensures an accessible help surface with keyboard focus restoration and localizable content.
  • Accessible View: presents rich UI content as plain text for screen readers where needed (e.g., panels, terminals, notifications).
  • Accessibility Verbosity Setting: toggles whether accessibility hints are announced on focus.
  • Accessibility Signals and ARIA Announcements: supports audible cues and live region messages to inform users of changes.
  • Keyboard Navigation and ARIA Labels: enforces keyboard operability and proper ARIA roles/labels across interactive elements.
  • Workflow Guidance: intended for both creating new interactive UI and updating existing features to meet accessibility standards.

Quick Start

Open a new interactive UI surface and add an accessibility help dialog, an accessible view if needed, and a verbosity setting to guide screen reader users.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I make VS Code UI features accessible for screen readers?

Make VS Code features accessible by adding an accessibility help dialog with keyboard focus restoration, an accessible view for plain text rendering, verbosity settings, and proper ARIA roles and labels for screen readers.

What is an accessible view and when do I need it for VS Code extensions?

An accessible view presents rich UI content as plain text for screen readers. You need it when panels, terminals, or notifications contain complex visual layouts that require text conversion to be properly announced.

How do I add ARIA alerts and status announcements in VS Code?

Add ARIA alerts and status announcements in VS Code by utilizing accessibility signals for audible cues and ARIA live region messages to inform screen reader users of dynamic content changes.

Does my new VS Code interactive surface require keyboard navigation and ARIA labeling?

Yes, new interactive VS Code surfaces require full keyboard operability and proper ARIA roles and labels. You must also configure frontmatter requirements, provider registrations, and signal usage to satisfy compliance checks.

What are accessibility verbosity settings and how do they work?

Accessibility verbosity settings toggle whether accessibility hints are announced on focus. They allow developers to control the amount of descriptive information screen readers provide when users interact with UI elements.

Are these accessibility guidelines required for updating existing VS Code features?

Yes, these accessibility guidelines apply to both new interactive UI surfaces and updates to existing features, ensuring that modified UI elements maintain ARIA compliance, keyboard navigation, and proper screen reader compatibility.