Skill

ui-a11y

Audits StyleSeed-based UI components or pages for WCAG 2.2 AA issues including contrast, touch targets, focus indicators, and semantics, applying safe fixes.

Html

Css

accessibility

frontend

npx claudepluginhub sickn33/antigravity-awesome-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Part 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.

SKILL.md

Similar Skills

ui-a11y

32.8k

Audits StyleSeed-based UI components or pages for WCAG 2.2 AA issues including contrast, touch targets, focus indicators, and semantics, applying safe fixes.

antigravity-awesome-skills

accessibility-review

Reviews web UI components, pages, and code for WCAG 2.1/2.2 AA accessibility issues like color contrast, keyboard navigation, ARIA, and semantics. Prioritizes and fixes critical problems one at a time.

2 files

design-accessibility

Applies WCAG AA and ARIA best practices for screen readers, keyboard navigation, focus management, semantic HTML, and color contrast in user-facing interfaces or accessibility audits.

5 files7 tools

ravn-ai-toolkit

Stats

Stars36383

Forks5961

Last CommitApr 13, 2026

Used By3 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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.