reviewing-a11y

Review web pages, code, and designs for WCAG 2.2 accessibility issues.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/malinovskiy-makar/qls --skill reviewing-a11y-malinovskiy-makar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-a11y
Source: https://github.com/malinovskiy-makar/qls/tree/main/.claude/skills/reviewing-a11y
Command: npx skills add https://github.com/malinovskiy-makar/qls --skill reviewing-a11y-malinovskiy-makar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Accessibility issues in web pages, component code, and design mockups are often discovered too late or missed entirely. This Skill performs structured accessibility reviews against WCAG 2.2 and WAI-ARIA APG standards, reporting severity-ranked issues with concrete fixes before they reach users. ## Core Features & Use Cases - Automatic target routing: Detects whether the input is a live URL, source file, or design artifact and loads the matching review guide. - Three review modes: Page review via browser snapshots or HTML retrieval, static code analysis for React/Vue/Angular/HTML, and visual design review for Figma files, images, and PDFs. - Severity-ranked output: Reports good practices plus Critical, Major, and Minor issues, each linked to WCAG success criteria with impact and fix suggestions, plus manual verification recommendations. - Use Case: A developer pastes a Figma URL before implementation; the Skill flags icon-only buttons, color-only error states, and missing focus indicator specs, then lists questions for the design team. ## Quick Start Ask the assistant to review the accessibility of a URL, component file path, or Figma link and report issues by severity.

Frequently Asked Questions about reviewing-a11y

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

FAQPage Schema
How do I review a web page for WCAG accessibility issues?

Provide the page URL and the Skill loads the page review guide. It uses browser interaction to inspect the accessibility tree when available, or falls back to HTML retrieval, then reports issues by severity with WCAG criteria and fixes.

How to check React or Vue components for accessibility problems?

Provide the component file path and the Skill performs static code analysis. It checks semantic HTML, alt text, form labels, ARIA usage, keyboard handlers, and framework-specific patterns like React aria-* props or Vue :aria-* bindings.

Can I review a Figma design for accessibility before implementation?

Yes, provide a Figma URL or design image and the design review guide checks color contrast risks, touch target sizes, visible labels, focus indicators, and error patterns. It also generates questions for the design team about dynamic behavior.

What accessibility issues can automated review not detect?

Color contrast ratios, full keyboard navigation flows, focus management in modals, ARIA live region announcements, and multi-page consistency require manual testing. The Skill flags these as manual verification items rather than guessing.

What is the difference between an accessibility review and a WCAG audit?

A review identifies severity-ranked issues and fixes for a specific page, file, or design. A formal audit determines conformance across all WCAG success criteria, which this Skill delegates to the separate auditing-wcag skill.