skills.rest
izzoa
izzoaCOMMUNITY
Explore all skills by this author →
GitHub

ss-a11y

Audit UI components for WCAG 2.2 AA accessibility issues and apply fixes.

22|1|Updated Jul 17, 2026
Search Tags:#accessibility#a11y#wcag#semantic html#aria#ui audit
One-click install
npx skills add https://github.com/izzoa/polyrouter --skill ss-a11y
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ss-a11y
Source: https://github.com/izzoa/polyrouter/tree/main/.agents/skills/ss-a11y
Command: npx skills add https://github.com/izzoa/polyrouter --skill ss-a11y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you audit a component or page for accessibility issues and apply practical fixes, reducing the risk of WCAG violations and making interfaces easier for everyone to use.

Core Features & Use Cases

  • Accessibility audit: Checks color contrast, touch targets, keyboard support, labels, semantic HTML, ARIA usage, and motion preferences.
  • Targeted fixes: Applies direct edits where possible to improve compliance and usability.
  • Use case: Use it when reviewing a UI component, form, modal, or page that needs a static accessibility pass before release.

Quick Start

Audit the specified file for accessibility issues and fix any clear violations.

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 component for WCAG 2.2 AA compliance?▼

Auditing a component for WCAG 2.2 AA compliance involves statically reviewing UI code for semantic HTML, ARIA usage, accessible labels, keyboard support, contrast checks, and reduced-motion handling to identify and apply direct fixes for violations.

What is included in a static accessibility audit for UI components?▼

A static accessibility audit includes checking UI code for color contrast, touch targets, keyboard support, accessible labels, semantic HTML, ARIA usage, and motion preferences to reduce WCAG violations and improve usability.

Can I use an automated audit to fix ARIA and semantic HTML issues?▼

Yes, an automated audit can fix ARIA and semantic HTML issues by applying targeted direct edits to component code where clear accessibility violations are detected during the static review process.

Does this accessibility review work with forms and interactive elements?▼

Yes, this accessibility review works with forms, modals, pages, and interactive elements built with StyleSeed conventions, verifying keyboard support and accessible labels to meet WCAG compliance standards.

What's the best way to handle reduced-motion preferences in UI components?▼

Handling reduced-motion preferences requires verifying during your accessibility audit that motion preference checks are implemented in UI components, ensuring WCAG compliance and preventing usability issues for motion-sensitive users.

When should I run an accessibility audit on my UI code?▼

You should run an accessibility audit on your UI code when reviewing a component, form, modal, or page that needs a static accessibility pass before release to ensure it meets WCAG 2.2 AA standards.

Related Skills

Explore More Software Engineering Skills→
izzoaizzoa
22

ss-component

Generate StyleSeed UI components with project conventions for structure, styling, typing, and accessibility.

Community
Intermediate
esneiderbravoesneiderbravo
1

accessibility-standards

Audit UI accessibility for WCAG 2.2 AA compliance with automated and manual checks.

Community
Intermediate
dragoscirjandragoscirjan

lang-html

Enforce semantic HTML, WCAG 2.1 AA accessibility, and keyboard navigability.

Community
Basic
matteocervellimatteocervelli
25

accessibility-checker

Identify and report WCAG 2.1 Level AA accessibility violations on web pages.

Community
Advanced