/Catalogue/Prompt/plugin87/plugin87-ux-ui-agent-skills-a11y-audit

Origin: github

a11y-audit

Audit a UI or design against WCAG 2.2 AA/AAA and ARIA patterns, returning criterion-referenced findings with severity and specific fixes. Use when the user wants an accessibility check, contrast verification, keyboard/screen-reader review, or wants to confirm a component meets POUR.

by plugin87 · updated 9d ago · imported from GitHub

Installs0+0/7d
Security score100/100
Retention 14d0%
GitHub stars1.5K

Skill logic

Execution graph
User message
Prompt rewrites behaviour
Response

SKILL.md

View on GitHub ↗

Skill: Accessibility Audit

Evaluate against WCAG 2.2 and the project's ARIA patterns.

Steps

  1. Read accessibility/wcag-checklist.md (POUR-organized, P0/P1/P2) and accessibility/aria-patterns.md.
  2. Check the mandatory P0 set per component: keyboard navigable, focus visible (≥3:1), screen-reader name/role/state, contrast (4.5:1 text / 3:1 UI), target size ≥24×24, no color-only signaling.
  3. Verify WCAG 2.2 additions: Focus Not Obscured (2.4.11), Target Size (2.5.8), Accessible Authentication (3.3.8).
  4. Contrast — measure, don't eyeball. For rendered HTML, RUN the real-render gates and report their actual output (CLAUDE.md → Verification Protocol): node scripts/measure_render.mjs <file> [--dark] (every text element) AND node scripts/verify_states.mjs <file> [--dark] (every interactive element in default/hover/focus — catches hover-state failures). For loose color pairs, python3 scripts/contrast.py "<fg>" "<bg>". Never state a ratio you did not measure.
  5. Check reduced-motion handling (taste/motion-choreography.md).

Output

A findings table: WCAG criterion (e.g. 1.4.3) · severity (P0/P1/P2) · what fails · specific fix. Confirm passes explicitly. Accessibility may never be traded for aesthetics.

Discussion

No comments yet — start the thread.

Sign in to join the discussion.

/More from plugin87/ux-ui-agent-skills

plugin87· 9d agoCommunity
design-review

Prompts · JavaScript · v0.1.0

Review or audit a design/UI across 6 weighted dimensions with Nielsen's 10 heuristics and a prioritized findings table. Use when the user wants a design critique, quality score, heuristic evaluation, or audit of an existing screen, page, or product before/after build.

#accessibility#ai-agents#claude

0 1.5K
plugin87· 9d agoCommunity
apply-aesthetic

Prompts · JavaScript · v0.1.0

Apply a visual direction — an archetype (high-end agency, editorial minimal, brutalist, soft-SaaS, dark-tech) or one of 138 named design systems (apple, linear-app, stripe, vercel, notion, material, shadcn, spotify, tesla…) — by resolving it into the token system. Use when the user wants a specific look/vibe/brand feel, or asks to make a design feel premium/expensive/non-generic.

#accessibility#ai-agents#claude

0 1.5K
plugin87· 9d agoCommunity
brandkit

Prompts · JavaScript · v0.1.0

Generate a complete, accessible brand design system from a brief — primitive → semantic → component DTCG tokens (color, type, spacing, radius, shadow, motion), light + dark, plus a single theme.css — verified for WCAG. Use when the user wants a from-scratch brand/design foundation, a new palette + type system, or a themeable token kit for a product.

#accessibility#ai-agents#claude

0 1.5K
plugin87· 9d agoCommunity
data-dashboard

Prompts · JavaScript · v0.1.0

Build a dense, data-heavy screen - an analytics console or a trading terminal - with real charts drawn from tokens: candlestick, volume, depth, stacked area, waterfall, scatter, correlation matrix, donut, gauge, sparklines, heatmaps and order books. Use when the request is a dashboard, terminal, monitoring view, data console, or any screen whose job is to show many numbers at once. Covers the layout sequence, the SVG geometry, the accessibility contract per chart type, and the contrast traps that only appear in dark mode.

#accessibility#ai-agents#claude

0 1.5K