better-accessibility

Reviews and fixes UI code for keyboard, screen-reader, and WCAG accessibility compliance.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/xzedm/clipplic-landing --skill better-accessibility-xzedm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: better-accessibility
Source: https://github.com/xzedm/clipplic-landing/tree/main/.agents/skills/better-accessibility
Command: npx skills add https://github.com/xzedm/clipplic-landing --skill better-accessibility-xzedm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Interfaces often ship with invisible accessibility failures: missing focus rings, unlabeled icon buttons, keyboard traps, and errors that screen readers never announce. This Skill gives you a systematic set of principles and review procedures to find and fix these issues in UI code before users hit them. ## Core Features & Use Cases - Fourteen Core Principles: Covers native elements first, visible focus rings, full keyboard support per ARIA APG, focus trapping in modals, minimum hit areas, form labels and error announcements, accessible names, reduced motion, live regions, alt text, semantic structure, and zoom/reflow survival. - Structured Review Output: Produces findings grouped by principle in a Severity/Location/Before/After/Why table, followed by a verification report and a Block/Needs changes/Approve verdict. - Common Mistakes Reference: Maps frequent anti-patterns (outline: none, div onClick, placeholder-as-label, positive tabindex) directly to their fixes. - Use Case: A developer asks for an accessibility review of a React settings page; the Skill walks the code as a keyboard-only and screen-reader user, flags an unlabeled icon button and a missing focus-visible style, and returns actionable before/after fixes with file and line citations. ## Quick Start Review the accessibility of my React components and report any keyboard, focus, or screen-reader issues with fixes.

Frequently Asked Questions about better-accessibility

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

FAQPage Schema
Should I disable the submit button until a form is valid?▼

No. Keep submit enabled and validate on submit, since a disabled button hides what must be fixed. On failure, mark invalid fields with aria-invalid, attach inline error text via aria-describedby, and move focus to the first invalid field.