auditing-wcag

Audit WCAG 2.2 A/AA conformance and report Pass/Fail/NT/NA per success criterion with evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @a11y-skills/audit, playwright, and includes references (resource) components.

What problem does it solve? Formal accessibility compliance requires checking every WCAG 2.2 A/AA success criterion and documenting the result with evidence, which is slow and error-prone when done manually. This Skill systematizes the audit into a six-step workflow that produces a criterion-by-criterion conformance report. ## Core Features & Use Cases - Full WCAG 2.2 A/AA coverage: Assigns Pass, Fail, NT (Not Tested), or NA to every success criterion using a coverage matrix spanning automated, interactive, manual, and content checks. - Automated and interactive testing: Uses Playwright accessibility tree analysis plus the a11y-audit CLI (axe-core, reflow, zoom, focus indicator, target size, keyboard trap, and more) to detect violations with JSON and screenshot evidence. - Formal report generation: Produces a structured audit report with scope, summary tables, per-criterion verdicts, issue lists, and limitations, saved to a dated output directory. - Use Case: A compliance team needs to certify that https://example.com meets WCAG 2.2 AA before launch. The skill establishes a scope contract, runs automated and keyboard-interaction checks, flags items needing human judgment as NT, and delivers an evidence-backed conformance report. ## Quick Start Audit WCAG 2.2 AA conformance for https://example.com and generate a Pass/Fail/NT/NA report for every success criterion.

Frequently Asked Questions about auditing-wcag

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

FAQPage Schema
How do I audit a website for WCAG 2.2 AA compliance?

Provide a URL or file path, agree on scope (level, pages, limitations), then the skill runs automated Playwright and axe-core checks, interactive keyboard tests, and manual review items. It outputs a report with Pass/Fail/NT/NA for every A/AA success criterion.

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

An audit systematically verifies conformance against all WCAG 2.2 A/AA criteria and produces formal Pass/Fail/NT/NA verdicts with evidence. A review focuses on finding practical issues and suggesting fixes during development, which the reviewing-a11y skill handles instead.

Can automated tools fully test WCAG conformance?

No. Playwright and axe-core only expose the computed accessibility tree, so screen reader verification, AT and browser compatibility, and cognitive accessibility judgment cannot be automated. Untestable items are marked NT rather than guessed.

What automated checks does the a11y-audit CLI support?

The CLI includes axe-audit, reflow-check, text-spacing-check, zoom-200-check, orientation-check, autocomplete-audit, time-limit-detector, auto-play-detection, focus-indicator-check, target-size-check, and keyboard-trap-check. It requires Node 18+ and outputs JSON results with exit codes.

What do Pass, Fail, NT, and NA mean in a WCAG audit report?

Pass means the criterion is satisfied, Fail means a violation was detected, NT means the item was not tested and needs assistive technology or human verification, and NA means the criterion does not apply because the target content does not exist.