accessibility-audit

Audits HTML designs for WCAG accessibility issues across contrast, semantics, keyboard, and motion.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Mjlike123/ui-prototype-workbench --skill accessibility-audit-mjlike123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/Mjlike123/ui-prototype-workbench/tree/main/.agents/skills/monkren-design/skills/04-review/accessibility-audit
Command: npx skills add https://github.com/Mjlike123/ui-prototype-workbench --skill accessibility-audit-mjlike123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs often ship with accessibility defects—low contrast text, missing labels, keyboard traps, and motion hazards—that exclude users and fail WCAG compliance. This Skill systematically reviews HTML design files and produces a structured, evidence-backed issue list instead of relying on ad-hoc manual checks. ## Core Features & Use Cases - Four Parallel Review Agents: Covers contrast and color (WCAG AA ratios), semantic HTML structure, keyboard navigation and focus, plus motion, forms, and touch targets in one coordinated pass. - Evidence-Based Issue Reports: Each finding includes location, actual value, required value, impact, and a recommendation, with confidence and severity estimates. - Optional Remediation: Reports issues by default and only modifies files when the user explicitly requests fixes, then re-verifies the changes. - Use Case: After building a landing page prototype, ask for an accessibility audit to receive a deduplicated list of violations—such as a 3.2:1 button contrast ratio or a div used as a button—before design review. ## Quick Start Ask the assistant to run an accessibility audit on the HTML file you just edited and report all WCAG AA issues.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I check my HTML page for WCAG accessibility issues?

Run an accessibility audit on the HTML file you just edited. The review covers contrast ratios, semantic structure, keyboard navigation, and motion, then returns a structured issue list with actual versus required values and fix recommendations.

What contrast ratio does WCAG AA require for text?

WCAG AA requires 4.5:1 for normal text under 18px, 3:1 for large text (18px bold or 24px and above), and 3:1 for UI components like buttons, icons, and focus rings. The audit computes actual ratios for each color pair it can resolve.

Does the accessibility audit fix issues automatically?

No, it only reports issues by default with evidence and recommendations. Files are modified only when you explicitly request fixes, after which deterministic changes are applied by severity and re-verified.

What accessibility areas does the audit cover?

Four areas: contrast and color use, semantic HTML and ARIA usage, keyboard navigation and focus visibility, and motion, forms, and touch targets. This includes prefers-reduced-motion support, form error messaging, and 44x44px minimum touch areas.

Can the audit run without parallel sub-agent support?

Yes. If the environment supports sub-agents, four reviewers run in parallel; otherwise the current agent completes the four review areas sequentially. The audit never aborts due to missing parallel capability.