skills.rest
sigitpoerwo
sigitpoerwoCOMMUNITY
Explore all skills by this author →
GitHub

accessibility

Enforce accessibility guidelines for VS Code interactive UI surfaces.

Updated Mar 29, 2026
Search Tags:#vscode#accessibility#screen-reader#aria#keyboard-navigation#inclusive-design
One-click install
npx skills add https://github.com/sigitpoerwo/repoworkspace_zahra --skill accessibility-sigitpoerwo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/sigitpoerwo/repoworkspace_zahra/tree/main/skills/02-PERLU-SETUP/butuh-belajar/accessibility
Command: npx skills add https://github.com/sigitpoerwo/repoworkspace_zahra --skill accessibility-sigitpoerwo

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 features. Use when creating new UI or updating existing UI features.

Core Features & Use Cases

  • Establishes standardized patterns for adding accessibility help dialogs, accessible views, and verbosity settings to new features.
  • Ensures keyboard navigation, ARIA labeling, and live region announcements are consistently implemented across UI components.
  • Enables teams to design inclusive experiences for panels, dialogs, widgets, and notifications within VS Code.

Quick Start

Enable accessibility guidelines in your VS Code features by auditing for help dialogs, accessible views, and ARIA support during development.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I add ARIA attributes and screen-reader announcements to a VS Code feature?▼

To add screen-reader announcements and ARIA attributes in VS Code, apply standardized frontmatter-driven metadata and runtime integration points to ensure live regions correctly announce UI state changes.

What is the best way to implement keyboard navigation for new VS Code UI surfaces?▼

The best way to implement keyboard navigation is to follow standardized accessibility guidelines that enforce consistent focus management and keyboard operability across new interactive panels, dialogs, and widgets.

How do I set up accessibility help dialogs and verbosity settings in VS Code?▼

Set up accessibility help dialogs and verbosity settings by using established patterns that define localized help content and runtime integration hooks for new interactive UI surfaces.

Do I need to update ARIA labels when modifying existing VS Code panels?▼

Yes, you need to update ARIA labels, roles, and keyboard navigation when modifying existing VS Code panels to ensure inclusive design and maintain screen-reader compatibility.

Can I use these accessibility guidelines for both new and updated VS Code widgets?▼

Yes, you can apply these accessibility guidelines to both new interactive UI surfaces and updates to existing widgets, ensuring consistent ARIA support and keyboard navigation.

Why are screen-reader live regions not working in my VS Code extension UI?▼

Screen-reader live regions may not work if ARIA alerts and status announcements lack proper runtime integration points, requiring standardized frontmatter metadata to trigger announcements.

Related Skills

Explore More Software Engineering Skills→
DevFlex-AIDevFlex-AI

accessibility

Standardize accessibility guidelines for VS Code UI features.

Community
Basic
Ms1blackMs1black

vscode-accessibility

Implement ARIA roles, labels, and focus management in VS Code extension UIs.

Community
Advanced
darwinboaventuradarwinboaventura

accessibility

Implement accessible UI guidelines for VS Code interactive surfaces.

Community
Advanced
sanky369sanky369
29

accessibility-excellence

Audit web applications for WCAG compliance and accessibility gaps.

Community
Basic