ss-a11y

Audits components and pages for WCAG 2.2 AA accessibility issues and applies fixes.

Updated May 26, 2026
One-click install
npx skills add https://github.com/rmethodm/resumegen --skill ss-a11y-rmethodm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ss-a11y
Source: https://github.com/rmethodm/resumegen/tree/main/.agents/skills/ss-a11y
Command: npx skills add https://github.com/rmethodm/resumegen --skill ss-a11y-rmethodm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Accessibility defects like low color contrast, missing alt text, undersized touch targets, and missing ARIA labels are easy to miss during development and costly to fix later. This Skill statically audits a component or page against WCAG 2.2 AA criteria and applies fixes directly where possible. ## Core Features & Use Cases - WCAG 2.2 AA Audit: Checks perceivable, operable, understandable, and robust criteria including contrast ratios, touch target sizes, keyboard navigation, and semantic HTML. - Design Token Contrast Verification: Validates design system tokens like --foreground, --muted-foreground, --brand, and --destructive against minimum contrast ratios. - Auto-Fixes with Severity Report: Applies fixes directly where possible and reports remaining issues ranked Critical, Major, or Minor. - Use Case: Before shipping a new settings page, run the audit on the page file to catch 36px icon buttons that violate the 44px touch target minimum and form inputs missing programmatically associated error messages. ## Quick Start Ask the assistant to run an accessibility audit on a specific component or page file path and fix the issues it finds.

Frequently Asked Questions about ss-a11y

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

FAQPage Schema
How do I audit a React component for accessibility issues?▼

Run the audit against the component's file path. It checks WCAG 2.2 AA criteria including color contrast, touch target sizes, keyboard navigation, labels, and ARIA usage, then applies fixes directly and reports remaining issues by severity.

What accessibility standards does this audit check?▼

The audit targets WCAG 2.2 AA across four principles: perceivable (contrast ratios, text alternatives), operable (44px touch targets, keyboard access, reduced motion), understandable (labels, error association), and robust (semantic HTML, ARIA roles).

Does this work with Tailwind CSS and Radix UI components?▼

Yes, the audit assumes StyleSeed conventions with Tailwind utility classes and Radix UI components. It checks classes like min-h-11 for touch targets and focus-visible:ring utilities, and relies on Radix UI's built-in ARIA handling.

Can a static audit replace screen reader testing?▼

No, this is a static code audit, not a screen-reader simulation or runtime test. It catches code-level violations like missing alt text and low contrast, but manual testing with actual assistive technology is still required for full verification.

When should I not use this accessibility audit?▼

Skip it for general design system compliance reviews, Nielsen UX heuristic evaluations, or codebases that do not follow StyleSeed conventions with data-slot attributes and semantic tokens. It is scoped specifically to WCAG accessibility checks.