skills.rest
malwarebo
malwareboCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility

Implement accessibility features for VS Code UI components with ARIA compliance.

5|1|Updated Mar 15, 2026
Search Tags:#ui#vscode#accessibility#screen reader#keyboard navigation#aria
One-click install
npx skills add https://github.com/malwarebo/nyrve --skill accessibility-malwarebo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/malwarebo/nyrve/tree/main/.github/skills/accessibility
Command: npx skills add https://github.com/malwarebo/nyrve --skill accessibility-malwarebo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that new and updated interactive user interfaces within VS Code are fully accessible to users with disabilities, particularly those relying on screen readers and keyboard navigation.

Core Features & Use Cases

  • Accessibility Help Dialogs: Provides users with information on how to operate a feature via keyboard and screen reader.
  • Accessible Views: Offers a plain-text representation of rich UI content for screen reader users.
  • Keyboard Navigation & ARIA: Guarantees that all interactive elements are keyboard-operable and properly announced by assistive technologies.
  • Use Case: When developing a new code completion panel, this Skill ensures it has a help dialog, an accessible text view, and that all interactive elements are properly labeled and navigable with the keyboard.

Quick Start

Ensure the new feature's interactive UI includes an accessibility help dialog, an accessible view if content is rich, and adheres to keyboard navigation and ARIA standards.

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 components accessible to screen reader users?▼

To make VS Code UI components accessible, implement plain-text accessible views for rich content and provide accessibility help dialogs explaining keyboard and screen reader operation.

What WAI-ARIA patterns are needed for keyboard navigation in VS Code extensions?▼

Keyboard navigation in VS Code requires interactive elements to be fully operable via keyboard and properly labeled using WAI-ARIA patterns to ensure assistive technologies announce them correctly.

When do I need an accessibility help dialog for a new VS Code feature?▼

An accessibility help dialog is needed when developing new interactive VS Code UI features, providing users with information on how to operate the feature via keyboard and screen reader.

How do I add a screen reader accessible view for rich UI content in VS Code?▼

Add a screen reader accessible view by offering a plain-text representation of rich UI content, ensuring screen reader users can perceive and navigate the information effectively.

Can I use this approach to fix ARIA compliance for interactive VS Code panels?▼

Yes, this approach enforces adherence to WAI-ARIA patterns and best practices, ensuring interactive VS Code panels have properly labeled and navigable elements for assistive technologies.

What verbosity settings are required for screen reader announcements in VS Code UI?▼

Screen reader announcements require configurable verbosity settings to ensure inclusivity, allowing users to control the level of information spoken when navigating VS Code UI components.

Related Skills

Explore More Software Engineering Skills→
joshsmithxrmjoshsmithxrm
5

ext-verify

Automate VS Code extension webview UI tests with Playwright Electron.

Community
Advanced
fcsonlinefcsonline
49

accessibility

Apply WCAG 2.1 AA accessibility patterns to the DroneRoute UI.

Community
Intermediate
pdovhomiljapdovhomilja

Frontend Accessibility

Apply semantic HTML, ARIA, keyboard navigation, and color contrast to frontend interfaces.

Community
Basic
ripgraphicsripgraphics

accessibility-expert

Diagnose web accessibility violations and suggest WCAG 2.1/2.2 fixes.

Community
Advanced