accessibility-review

Audit designs and web pages for WCAG 2.1 AA violations and produce structured reports.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ilove323/comlan-skills --skill accessibility-review-ilove323
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-review
Source: https://github.com/ilove323/comlan-skills/tree/main/design/skills/accessibility-review
Command: npx skills add https://github.com/ilove323/comlan-skills --skill accessibility-review-ilove323

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, repeatable WCAG 2.1 AA accessibility audit workflow to identify, categorize, and prioritize accessibility issues in designs and web pages, reducing missed regressions and improving developer handoffs.

Core Features & Use Cases

  • Guided WCAG checklist: Maps findings to WCAG 2.1 AA criteria with examples for contrast, alternative text, semantics, ARIA, and focus order.
  • Practical testing methods: Recommends automated scans plus manual checks including keyboard navigation, screen reader validation, contrast measurements, and zoom behavior.
  • Handoff and remediation: Produces a structured audit report with severity, remediation suggestions, and instructions for creating prioritized tickets in project trackers.
  • Use case: Run an audit during design review to generate a prioritized accessibility backlog and concrete fixes for engineers and designers.

Quick Start

Ask the assistant to run an accessibility review of the "Homepage design" and produce a WCAG 2.1 AA audit report with prioritized fixes and a contrast table.

Frequently Asked Questions about accessibility-review

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

FAQPage Schema
How do I run a WCAG 2.1 AA accessibility audit on a web page?

Run a WCAG 2.1 AA accessibility audit by applying this workflow to designs or live pages to identify violations. It produces a structured report mapping issues to WCAG criteria, including severity levels, contrast checks, and suggested fixes.

What is the best way to check keyboard navigation and screen reader compatibility?

Checking keyboard navigation and screen reader compatibility involves manual validation guided by a WCAG checklist. This process identifies focus order and semantic issues, generating concrete remediation suggestions and testing instructions for developers.

Can I use this WCAG checklist for both UI design reviews and QA testing?

Yes, you can use this WCAG checklist for UI design reviews and QA testing. It applies to prototypes and live pages, generating a prioritized accessibility backlog with contrast tables and specific fixes for developer handoffs.

How do I generate an accessibility report with prioritized fixes for developer handoff?

Generate an accessibility report by running an audit on your target UI. The output maps findings to WCAG 2.1 AA criteria, assigns severity levels, provides remediation suggestions, and formats prioritized tickets for project trackers.

Does the accessibility audit include automated scans and manual contrast checks?

Yes, the accessibility audit includes both automated scans and manual checks. It recommends measuring contrast, validating zoom behavior, and testing keyboard navigation to ensure comprehensive WCAG 2.1 AA compliance.

Why are my UI designs failing WCAG 2.1 AA contrast requirements?

UI designs fail WCAG 2.1 AA contrast requirements when color ratios fall below acceptable thresholds. This audit measures contrast directly, maps failures to specific criteria, and provides actionable fixes for designers.