accessibility

Implement WCAG principles, keyboard navigation, and screen reader support in terminal applications.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/baphled/dotopencode --skill accessibility-baphled
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/baphled/dotopencode/tree/main/skills/accessibility
Command: npx skills add https://github.com/baphled/dotopencode --skill accessibility-baphled

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that terminal applications are usable by everyone, including individuals with disabilities, by adhering to accessibility standards and best practices.

Core Features & Use Cases

  • WCAG Compliance: Integrates Web Content Accessibility Guidelines principles into TUI development.
  • Keyboard Navigation: Focuses on making all features navigable via keyboard.
  • Screen Reader Support: Ensures compatibility with screen readers for visually impaired users.
  • Color Contrast: Verifies sufficient color contrast ratios for readability.
  • Use Case: When developing a new command-line interface tool, use this skill to audit its keyboard navigation flow and screen reader output to ensure it's usable by a wide range of users.

Quick Start

Use the accessibility skill to check keyboard navigation for the new CLI tool.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I make terminal applications accessible for users with disabilities?

Making terminal applications accessible involves implementing WCAG principles, ensuring full keyboard navigation, adding screen reader support, and verifying sufficient color contrast ratios for readability.

How do I test color contrast and keyboard navigation in a TUI?

Testing color contrast and keyboard navigation in a TUI requires auditing the application's focus flow and verifying that contrast ratios meet WCAG standards for visual readability.

Does WCAG compliance apply to command-line interface tools?

WCAG compliance applies to command-line interface tools by adapting universal design principles to terminal environments, ensuring features remain usable via keyboard and screen readers.

What is the best way to audit screen reader compatibility for TUIs?

The best way to audit screen reader compatibility for TUIs is to evaluate the application's output structures against assistive technology expectations, ensuring visually impaired users receive accurate feedback.

Can I use inclusive design principles for new command-line interface development?

You can apply inclusive design principles during new command-line interface development to build features that are navigable by keyboard and usable by diverse user groups from the start.

Why does my CLI tool fail keyboard navigation audits?

CLI tools fail keyboard navigation audits when interactive elements lack logical focus order or trap keyboard input, preventing users from accessing all features without a mouse.