How do I install the UI A11Y skill?

Run npx skillmds@latest add mmehdi0606/ui-a11y in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is UI A11Y safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with UI A11Y?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is UI A11Y free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published UI A11Y?

MMEHDI0606 (@mmehdi0606) published this skill. Their other Agent Skills are listed on their SkillMD profile.

UI A11Y by mmehdi0606 — Agent Skill

Name: UI A11Y
Rating: 4.2 (5 reviews)
Author: MMEHDI0606

File contents

UI Accessibility Audit

Overview

Part of StyleSeed, this skill audits components and pages for accessibility issues with an emphasis on the Toss seed's mobile UI patterns. It combines WCAG 2.2 AA checks with practical code fixes for touch targets, focus states, contrast, labels, and reduced motion.

When to Use

Use when reviewing a page or component for accessibility regressions
Use when a StyleSeed UI looks polished but has uncertain keyboard or contrast behavior
Use when adding new interactive controls to a mobile-first screen
Use when you want a prioritized list of issues and fixable items

Audit Areas

Perceivable

text contrast
non-text contrast for controls and graphics
alt text for images
labels for meaningful icons
no information conveyed by color alone

Operable

touch targets at least 44x44px
keyboard reachability for all interactive controls
logical tab order
visible focus indicators
reduced-motion support for nonessential animation

Understandable

visible labels or aria-label on inputs
error text associated with the correct field
clear wording for errors and validation
document language set appropriately

Robust

semantic HTML where possible
correct use of ARIA when semantics alone are insufficient
no faux buttons or links without the right roles and behavior

Output

Return:

Issues found, grouped by severity
Safe autofixes that can be applied directly
Items that need manual review or product judgment
A short summary of the accessibility risk level

Best Practices

Fix semantics before layering on ARIA
Use the design system tokens only if they still meet contrast requirements
Treat touch target failures as real usability defects, not polish issues
Prefer partial, verified fixes over speculative accessibility changes

Additional Resources

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

---name: ui-a11ydescription: Audit a StyleSeed-based component or page for WCAG 2.2 AA issues and apply practical accessibility fixes where the code makes them safe.---# UI Accessibility Audit## OverviewPart of [StyleSeed](https://github.com/bitjaru/styleseed), this skill audits components and pages for accessibility issues with an emphasis on the Toss seed's mobile UI patterns. It combines WCAG 2.2 AA checks with practical code fixes for touch targets, focus states, contrast, labels, and reduced motion.## When to Use- Use when reviewing a page or component for accessibility regressions- Use when a StyleSeed UI looks polished but has uncertain keyboard or contrast behavior- Use when adding new interactive controls to a mobile-first screen- Use when you want a prioritized list of issues and fixable items## Audit Areas### Perceivable- text contrast- non-text contrast for controls and graphics- alt text for images- labels for meaningful icons- no information conveyed by color alone### Operable- touch targets at least 44x44px- keyboard reachability for all interactive controls- logical tab order- visible focus indicators- reduced-motion support for nonessential animation### Understandable- visible labels or `aria-label` on inputs- error text associated with the correct field- clear wording for errors and validation- document language set appropriately### Robust- semantic HTML where possible- correct use of ARIA when semantics alone are insufficient- no faux buttons or links without the right roles and behavior## OutputReturn:1. Issues found, grouped by severity2. Safe autofixes that can be applied directly3. Items that need manual review or product judgment4. A short summary of the accessibility risk level## Best Practices- Fix semantics before layering on ARIA- Use the design system tokens only if they still meet contrast requirements- Treat touch target failures as real usability defects, not polish issues- Prefer partial, verified fixes over speculative accessibility changes## Additional Resources- [StyleSeed repository](https://github.com/bitjaru/styleseed)- [Source skill](https://github.com/bitjaru/styleseed/blob/main/seeds/toss/.claude/skills/ui-a11y/SKILL.md)## Limitations- Use this skill only when the task clearly matches the scope described above.- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Frequently asked questions

UI A11Y