design-accessibility-auditor

Audit designs and UI components for WCAG 2.1 compliance with specific fixes.

181|30|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/curiositech/some_claude_skills --skill design-accessibility-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-accessibility-auditor
Source: https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/design-accessibility-auditor
Command: npx skills add https://github.com/curiositech/some_claude_skills --skill design-accessibility-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need for accessible digital products by auditing designs for WCAG 2.1 compliance, ensuring that color contrast, touch targets, and focus indicators meet accessibility standards.

Core Features & Use Cases

  • Color Contrast Auditing: Verifies color palettes against WCAG contrast ratios for text and UI elements.
  • Component Accessibility Checks: Assesses interactive components like buttons, links, and form inputs for keyboard support, touch target size, and focus indicators.
  • Actionable Fixes: Provides specific, calculated recommendations to resolve identified accessibility violations.
  • Use Case: Before handing off a new UI design to development, use this Skill to audit all color combinations and interactive elements to ensure they meet WCAG 2.1 AA standards, preventing costly rework later.

Quick Start

Audit the provided design assets for WCAG 2.1 accessibility compliance and suggest fixes for any violations found.

Frequently Asked Questions about design-accessibility-auditor

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

FAQPage Schema
How do I check if my UI design meets WCAG 2.1 contrast ratio requirements?

To check WCAG 2.1 contrast ratio compliance, audit your color palettes and UI components against standard accessibility thresholds for text and interactive elements to identify violations and apply calculated contrast fixes.

What is the best way to audit interactive components for accessibility compliance?

Auditing interactive components for accessibility compliance involves assessing buttons, links, and form inputs for adequate touch target size, visible focus indicators, and screen reader support to ensure full WCAG 2.1 technical compliance.

Can I get specific fixes for WCAG 2.1 violations found in my color palette?

Yes, auditing color palettes for WCAG 2.1 violations generates specific, calculated recommendations to resolve contrast issues, ensuring text and UI elements meet required accessibility standards before development handoff.

Does accessibility auditing check keyboard support and focus indicators for form inputs?

Yes, accessibility auditing checks form inputs and interactive UI elements for keyboard support and visible focus indicators, providing actionable fixes to meet WCAG 2.1 AA standards for screen reader and keyboard navigation.

When should I run a WCAG 2.1 accessibility audit on my UI components?

Run a WCAG 2.1 accessibility audit on UI components before handing off new designs to development, ensuring color contrast, touch targets, and focus indicators meet compliance standards and preventing costly rework later.

What are the limitations of using a design accessibility auditor for UI compliance?

A design accessibility auditor focuses strictly on technical WCAG 2.1 compliance for contrast, touch targets, and screen reader support, meaning it does not evaluate aesthetic harmony or create comprehensive design systems.