skills.rest
colajacquin-e
colajacquin-eCOMMUNITY
Explore all skills by this author →
GitHub

accessibility

Implement accessibility help dialogs, accessible views, and verbosity controls for VS Code UI.

Updated Mar 18, 2026
Search Tags:#ui#accessibility#a11y#screen-reader#aria#keyboard-navigation#assistive-tech
One-click install
npx skills add https://github.com/colajacquin-e/ephcode --skill accessibility-colajacquin-e
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/colajacquin-e/ephcode/tree/main/.github/skills/accessibility
Command: npx skills add https://github.com/colajacquin-e/ephcode --skill accessibility-colajacquin-e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility challenges in UI require consistent, reusable patterns to ensure screen readers, keyboard navigation, and ARIA semantics work across features. This skill provides a structured approach with a help dialog, an accessible view, and a verbosity setting to guide and empower both developers and users.

Core Features & Use Cases

  • Accessibility Help Dialog: guides screen reader users and explains keyboard shortcuts and interactions for new or updated UI.
  • Accessible View: presents rich visual content as plain text for screen readers when applicable.
  • Accessibility Verbosity Setting: allows users to toggle hints about accessibility features and help dialog availability.
  • Signals and ARIA Messaging: standardizes announcements and live regions for dynamic changes.

Quick Start

Enable an accessibility framework for a new interactive UI surface and provide a help dialog, an accessible view when needed, and a verbosity setting to announce accessibility options.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I make a new VS Code panel accessible for screen readers?▼

To make VS Code panels accessible, integrate an Accessibility Help dialog, an Accessible View for rich content, and ARIA messaging. This ensures keyboard operability and screen-reader visibility for new interactive UI surfaces.

How do ARIA live regions work for dynamic UI updates in VS Code?▼

ARIA live regions standardize announcements for dynamic changes in VS Code features. By registering signals and ARIA messaging, screen readers receive real-time updates when interactive UI content changes.

What is an accessibility verbosity setting and when do I need it?▼

An accessibility verbosity setting allows users to toggle hints about accessibility features and help dialog availability. It is needed when introducing interactive UI to ensure screen reader users can discover available support.

Does VS Code have a standard way to present visual content as plain text for assistive tech?▼

Yes, the Accessible View presents rich visual content as plain text for screen readers. It is applied when a VS Code feature introduces or updates interactive UI with complex visual elements.

What is the best way to implement keyboard navigation for VS Code dialogs?▼

The best way to implement keyboard operability is using a structured framework that requires an Accessibility Help dialog and ARIA attributes. This ensures keyboard navigation works across new panels and dialogs.

Related Skills

Explore More Software Engineering Skills→
darwinboaventuradarwinboaventura

accessibility

Implement accessible UI guidelines for VS Code interactive surfaces.

Community
Advanced
sigitpoerwosigitpoerwo

accessibility

Enforce accessibility guidelines for VS Code interactive UI surfaces.

Community
Intermediate
Omar-CcOmar-Cc

accessibility

Audit web interfaces against WCAG 2.2 criteria and resolve accessibility issues.

Community
Advanced
esneiderbravoesneiderbravo
1

accessibility-standards

Audit UI accessibility for WCAG 2.2 AA compliance with automated and manual checks.

Community
Intermediate