home / skills / shaul1991 / shaul-agents-plugin / ux-ui-a11y

ux-ui-a11y skill

safe

This skill helps assess and improve web accessibility by auditing WCAG compliance, keyboard navigation, color contrast, and screen reader compatibility.

npx playbooks add skill shaul1991/shaul-agents-plugin --skill ux-ui-a11y

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

514 B

---
name: ux-ui-a11y
description: 접근성 검사 에이전트. 웹 접근성을 검사하고 개선합니다.
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
---

# UI Accessibility Agent

## 역할
웹 접근성을 검사하고 개선합니다.

## 담당 업무
- WCAG 준수 검사
- 스크린 리더 호환성
- 키보드 네비게이션
- 색상 대비 검사

## 트리거 키워드
접근성, a11y, accessibility, WCAG, 스크린리더

## 산출물 위치
- 접근성 리포트: `docs/accessibility/`

Overview

This skill is an accessibility inspection agent that tests and helps improve web UI accessibility. It automates checks for WCAG conformance, keyboard and screen reader compatibility, and color contrast issues. The skill produces actionable accessibility reports and remediation suggestions. Outputs are organized for easy review and follow-up implementation.

How this skill works

The agent crawls specified pages or components and runs a set of automated audits against WCAG success criteria, keyboard navigation flows, ARIA usage, and color contrast thresholds. It simulates keyboard-only interaction and inspects semantic structure for screen reader compatibility, flagging likely problems and providing code-level recommendations. Results are written to a structured accessibility report that highlights severity, reproducibility steps, and remediation guidance.

When to use it

Before release to validate WCAG compliance and reduce legal risk
During UI development sprints to catch accessibility regressions early
When onboarding a new design system or component library
Prior to accessibility audits or external reviews
To triage reported accessibility issues from users or QA

Best practices

Run the agent early and often in CI to detect regressions before deployment
Combine automated findings with manual testing (keyboard and screen reader)
Prioritize fixes by impact and severity; focus on navigation and perceivability first
Include design and product teams in remediation to ensure UX-consistent fixes
Document resolved issues and update component tests to prevent recurrence

Example use cases

Generate a sprint-end accessibility report for a public-facing marketing site
Scan a component library for missing ARIA roles and keyboard traps
Validate color contrast for a new theme before a major redesign
Produce remediation steps for a login flow that fails screen reader tests
Integrate into CI to block merges that introduce high-severity accessibility regressions

FAQ

What standards does the agent check against?

The agent focuses on WCAG success criteria and common screen reader and keyboard interaction patterns.

Are all accessibility issues fixable automatically?

Some issues can be fixed automatically or with suggested code changes, but many require developer judgment and manual testing to ensure correct UX.