skills.rest
OM-bit-hub
OM-bit-hubCOMMUNITY
Explore all skills by this author →
GitHub

a11y-design

Audit UI screens for WCAG 2.1 AA accessibility compliance.

Updated Aug 23, 2026
Search Tags:#design#accessibility#a11y#audit#ui-design#wcag-2.1
One-click install
npx skills add https://github.com/OM-bit-hub/daily_tracker --skill a11y-design-om-bit-hub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a11y-design
Source: https://github.com/OM-bit-hub/daily_tracker/tree/main/.agents/skills/designer/a11y-design
Command: npx skills add https://github.com/OM-bit-hub/daily_tracker --skill a11y-design-om-bit-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessible design is essential to ensure inclusivity and usability. This Skill provides structured guidance, checklists, and patterns to design interfaces that meet WCAG 2.1 AA standards.

Core Features & Use Cases

  • WCAG-compliant design guidelines for color contrast, keyboard navigation, ARIA landmarks, headings, and form labeling.
  • Step-by-step process for accessibility audits, design patterns, and common anti-patterns.
  • Use cases include auditing existing pages, wireframing accessible interfaces, and creating accessible components from scratch.

Quick Start

Audit a UI screen for WCAG 2.1 AA compliance and implement color contrast, keyboard navigation, and proper ARIA patterns.

Frequently Asked Questions about a11y-design

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

FAQPage Schema
How do I audit a UI screen for WCAG 2.1 AA compliance?▼

Yes, you can wireframe accessible interfaces and create accessible components from scratch by applying WCAG 2.1 AA guidelines for color contrast, keyboard navigation, ARIA landmarks, and proper form labeling.

How do I ensure proper keyboard focus management and ARIA roles in web applications?▼

WCAG 2.1 AA accessible design covers critical patterns including color contrast compliance, keyboard focus management, ARIA role usage, heading hierarchy, form labeling and errors, skip navigation, and live region messaging for inclusive dashboards and content.

What is the best way to fix form labeling and error accessibility issues?▼

Yes, this accessibility audit approach supports dashboards, forms, navigation, and content across web applications by embedding WCAG 2.1 AA patterns for color contrast, keyboard focus management, and live region messaging.

What common accessibility anti-patterns should I avoid in UI design?▼

You do not need any specific dependencies to audit UI for WCAG 2.1 AA compliance, as this accessibility design guidance applies to standard UI design and frontend development workflows without external component requirements.

Related Skills

Explore More Design & Creative Skills→
SufficientDaikonSufficientDaikon
8

design-review

Review design artifacts using heuristic evaluation and WCAG 2.1 AA criteria.

Community
Advanced
peopleforresterpeopleforrester
3

accessibility-checker

Audit web content for WCAG 2.1 AA accessibility issues and output a prioritized remediation report.

Community
Basic
pelcherspelchers

ensuring-accessibility

Implement WCAG 2.1 AA-compliant accessibility patterns for web interfaces.

Community
Advanced
aroidoaroido

accessibility-audit

Audit web components for WCAG 2.1 AA accessibility issues.

Official
Intermediate