skills.rest
zivtech
zivtechOFFICIAL
Explore all skills by this author →
WebsiteGitHub

a11y-planner

Generate accessibility design plans for software components using WCAG 2.2 and ARIA.

1|Updated Mar 2, 2026
Search Tags:#design#planning#accessibility#ARIA#WCAG#code
One-click install
npx skills add https://github.com/zivtech/harsh-critic --skill a11y-planner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a11y-planner
Source: https://github.com/zivtech/harsh-critic/tree/main/a11y-planner/.claude/skills/a11y-planner
Command: npx skills add https://github.com/zivtech/harsh-critic --skill a11y-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps to design accessibility upfront, preventing bugs during code implementation.

Core Features & Use Cases

  • Accessibility Design Planning: Develops accessibility specifications for code and interfaces.
  • Compliance with Standards: Ensures adherence to WCAG 2.2 and WAI-ARIA Authoring Practices Guide.
  • Use Case: Before starting a new feature development, use this Skill to map out the accessibility plan, reducing the chance of post-implementation bugs.

Quick Start

Run 'a11y-planner --target="newFeatureComponent"' to create an accessibility design plan for your feature.

Frequently Asked Questions about a11y-planner

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

FAQPage Schema
How do I plan accessibility for new software components before coding?▼

To plan accessibility upfront, generate a design specification covering semantic structure, ARIA patterns, and content strategy for your feature. This protocol minimizes accessibility issues early in the software development lifecycle.

What is accessibility design planning for code implementation?▼

Accessibility design planning creates early-stage specifications for software interfaces to prevent post-implementation bugs. It maps out semantic structure and ARIA patterns before development begins, ensuring compliance with WCAG 2.2 standards.

Do I need to know WCAG and ARIA to use an accessibility planner?▼

Yes, utilizing an accessibility planner requires existing knowledge of WCAG 2.2 and WAI-ARIA Authoring Practices Guide. The tool uses this domain knowledge to produce compliant semantic structure and content strategy designs.

How do I create an ARIA pattern design plan for a feature component?▼

Create an ARIA pattern design plan by targeting your new feature component to generate an accessibility specification. The output encompasses semantic structure, ARIA patterns, and content strategy to guide compliant code implementation.

What's the best way to reduce accessibility bugs during software development?▼

The best way to reduce accessibility bugs is designing accessibility upfront before writing code. Creating an early-stage implementation plan for semantic structure and ARIA patterns prevents post-implementation compliance issues.

When should I not use upfront accessibility planning for software?▼

Upfront accessibility planning is not suitable for undocumented legacy code refactoring without targeting a specific component. It requires a defined target feature and foundational knowledge of WCAG 2.2 to generate valid semantic and ARIA specifications.

Related Skills

Explore More Software Engineering Skills→
Higashi-KotaHigashi-Kota

a11y

Audits UI components for WCAG 2.2 AA and ARIA compliance.

Community
Intermediate
BigPapiCBBigPapiCB
2

accessibility

Identify and enforce WCAG compliance, ARIA patterns, and keyboard operability in UI components.

Community
Advanced
Higashi-KotaHigashi-Kota

ui-component

Build accessible React UI components with design tokens and ARIA patterns.

Community
Advanced
travisjneumantravisjneuman
88

accessibility-a11y

Ensure WCAG 2.2 compliance with ARIA patterns and keyboard navigation.

Community
Intermediate