ui-a11y

Audit StyleSeed-based UI components and Toss mobile patterns for accessibility issues and generate structured reports with severity and fixes.

25|6|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/KRISHNA0R/PORTFOLIOv2 --skill ui-a11y-krishna0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-a11y
Source: https://github.com/KRISHNA0R/PORTFOLIOv2/tree/main/.agents/skills/ui-a11y
Command: npx skills add https://github.com/KRISHNA0R/PORTFOLIOv2 --skill ui-a11y-krishna0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits UI components and pages for accessibility issues and provides practical fixes.

Core Features & Use Cases

  • Automated accessibility auditing for UI components and pages
  • Prioritized issues with actionable fixes and guidance
  • Suitable for StyleSeed-based UIs and Toss mobile patterns

Quick Start

Run an accessibility audit on a UI component or page to generate an actionable fix plan.

Frequently Asked Questions about ui-a11y

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

FAQPage Schema
How do I audit my UI components for WCAG 2.2 AA accessibility issues?

You can audit UI components for WCAG 2.2 AA accessibility issues by running an automated audit that identifies perceivable, operable, understandable, and robust concerns. It generates a structured report with issue severity, safe autofixes, manual review notes, and a risk summary.

What is the best way to fix accessibility issues safely in a frontend UI?

The best way to fix accessibility issues safely is to use a structured audit report that prioritizes issues by severity and provides actionable fixes. This separates safe autofixes from manual review notes to ensure secure engineering implementation.

Can I use this accessibility audit with StyleSeed-based UIs and Toss mobile patterns?

Yes, you can use this accessibility audit with StyleSeed-based UIs and Toss mobile patterns. It identifies perceivable, operable, understandable, and robust accessibility concerns specific to these frontend structures.

What does an automated WCAG accessibility report include for engineering implementation?

An automated WCAG accessibility report includes prioritized issues with actionable fixes, safe autofixes, manual review notes, and a risk summary. This structured output is specifically designed to guide engineering implementation.

How do I identify perceivable and operable accessibility concerns in my web application?

To identify perceivable and operable accessibility concerns in your web application, run an automated audit against WCAG 2.2 AA standards. This evaluates your UI components and generates a prioritized, actionable fix plan.