a11y
Systematically improve accessibility so the interface works for users with disabilities, temporary impairments, and assistive technology.
This skill focuses on remediation and implementation, not just scoring. It complements audit (which measures across dimensions) and harden (which handles edge cases broadly). Use this when accessibility is the primary goal.
MANDATORY PREPARATION
Users start this workflow with /a11y. Once this skill is active, load $frontend-design — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow that protocol before proceeding — if no design context exists yet, you MUST load $setup first.
Consult the accessibility testing reference for automated tool integration (axe, WAVE, Pa11y) and CI workflow guidance. Consult the colorblindness UX reference when color is carrying meaning in states, charts, or validation. Consult the component accessibility reference for keyboard support, focus handling, skip links, and hidden content patterns. Consult the interaction design reference for focus, loading, transitions, and feedback states. Consult the semantic color reference when checking whether color communicates state or just decoration. Consult the responsive design reference when accessibility needs to adapt across small screens, touch contexts, or zoom levels.
Assess Accessibility
Identify what is broken and who it affects:
More from aladicf/better-web-ui
critique
Evaluate an interface from a UX perspective, assessing hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring and actionable feedback. Use when the user wants an overall design or UX review—not when the main need is measurable accessibility/performance diagnosis, or final micro-detail polish.
32polish
Perform a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the work is functionally complete and needs finishing touches—not when the hierarchy, structure, tone, or technical foundation still need major changes.
32frontend-design
Create distinctive, production-grade frontend interfaces with strong hierarchy, thoughtful systems, and polished implementation that avoid generic AI aesthetics. Use when the user wants to build or redesign web pages, flows, components, or full app surfaces, or when another better-web-ui skill needs shared project design context before other better-web-ui skills.
31empty-state
Design focused empty states for zero-data, no-results, permission, and error situations with clear value framing, strong CTAs, and less dead chrome. Use when the user mentions blank pages, zero-data screens, no results, permission states, or dead controls—not broader onboarding strategy.
30normalize
Audit and realign UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.
30colorize
Build or refine UI color systems, warmth, semantic color, and color-based hierarchy in designs that are too gray, monochromatic, or missing color meaning. Use when the user mentions dull colors, gray UI, missing warmth, weak semantic color, or a need for stronger color hierarchy.
30