accessibility

Implement accessibility help dialogs, accessible views, and ARIA support for VS Code UI features.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/voidful/Aixlarity --skill accessibility-voidful
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/voidful/Aixlarity/tree/main/aixlarity-ide/.github/skills/accessibility
Command: npx skills add https://github.com/voidful/Aixlarity --skill accessibility-voidful

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New VS Code UI features often ship without screen reader support, keyboard navigation, or proper ARIA semantics, leaving assistive technology users unable to discover or operate them. This Skill provides the required patterns and checklists to make every new or updated interactive UI surface accessible. ## Core Features & Use Cases - Accessibility Help Dialogs: Create IAccessibleViewImplementation providers with localized help text, dynamic keybinding resolution, and focus restoration on close. - Accessible Views & Verbosity Settings: Expose rich visual content as plain-text read-only editors and register AccessibilityVerbositySettingId configuration entries. - Signals, ARIA, and Keyboard Support: Play accessibility signals, use alert()/status() live regions correctly, and enforce keyboard navigation, ARIA roles, and labels. - Use Case: When adding a new panel or widget to the VS Code workbench, follow the included checklist to register the help dialog, accessible view, verbosity setting, and ARIA attributes before shipping. ## Quick Start Use the accessibility skill to add an accessibility help dialog, accessible view, and verbosity setting for my new workbench panel.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I add an accessibility help dialog to a VS Code feature?

Create a class implementing IAccessibleViewImplementation with type AccessibleViewType.Help, return an AccessibleContentProvider with localized help text from getProvider(), and register it via AccessibleViewRegistry.register() in the feature's contribution file.

When does a VS Code feature need an accessible view?

An accessible view is required when the feature renders rich or visual content that screen readers cannot read directly, such as chat responses, notifications, or terminal output. Purely keyboard-driven input fields only need a help dialog.

What is the difference between aria alert() and status() in VS Code?

alert() uses an assertive live region that interrupts screen reader speech for urgent information like errors. status() uses a polite live region queued after current speech, preferred for progress updates and non-urgent state changes.

How do I add an accessibility verbosity setting in VS Code?

Add an entry to the AccessibilityVerbositySettingId enum in accessibilityConfiguration.ts, register the configuration property with baseVerbosityProperty for a boolean defaulting to true, and reference the key in your content providers.

Can I register a new accessibility signal for my feature?

Use an existing AccessibilitySignal static member when one fits your event. If none fits, coordinate with the accessibility maintainer before registering a new signal rather than adding one unilaterally.