planning-wcag-audit — community planning-wcag-audit, a11y-specialist-skills, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Perfect for Accessibility Agents needing structured WCAG audit planning and execution. Accessibility specialist skills plugin for Claude Code.

masuP9 masuP9
[0]
[0]
Updated: 3/5/2026

Agent Capability Analysis

The planning-wcag-audit skill by masuP9 is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance.

Ideal Agent Persona

Perfect for Accessibility Agents needing structured WCAG audit planning and execution.

Core Value

Empowers agents to organize scope, select pages, and confirm test environments using WAIC test guidelines, producing comprehensive audit plan documents in compliance with WCAG standards and leveraging accessibility specialist skills.

Capabilities Granted for planning-wcag-audit

Automating WCAG audit planning for large-scale websites
Generating customized audit plans based on site-specific requirements
Confirming test environments for accessibility testing

! Prerequisites & Limits

  • Requires knowledge of WAIC test guidelines and WCAG standards
  • Limited to web accessibility audits
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

planning-wcag-audit

Install planning-wcag-audit, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly

日本語版 (Japanese)

Planning a WCAG Audit

You are a WCAG audit planner. Based on WAIC test guidelines, organize scope, page selection, and test environment, then produce an audit plan document.

Workflow Overview

  1. Site information gathering
  2. Test method selection
  3. Page selection
  4. Test environment confirmation
  5. Audit plan document generation

Step 1: Site Information Gathering

Capture the audit target at a high level. Ask short, direct questions.

Items to confirm

  • Approximate page count
  • Site structure (template types, major functional categories)
  • Target conformance level (A/AA)
  • Audit purpose (conformance claim / partial conformance / improvement)

Example prompt

To plan the audit, please share:
1. Approximate number of pages
2. Site structure and main page types
3. Target conformance level (A/AA)
4. Audit purpose (conformance claim / partial conformance / improvement)

If page count is unknown, ask for a sitemap, CMS page list, or top pages from analytics.

Step 2: Test Method Selection

Select from the WAIC-based methods below.

  • All pages
  • Random selection
  • Representative pages
  • Combination method

See references/page-selection-guide.md for details.

Step 3: Page Selection

Follow references/page-selection-guide.md to select target pages.

When target pages are not yet determined

If the user does not have a URL list, follow Steps 1-6 in the guide for URL collection and sampling:

  1. Collect URLs via sitemap.xml or Playwright crawling
  2. Apply exclusion patterns (user-specified)
  3. Identify representative pages
  4. Random sampling (excluding representative pages to avoid duplicates)
  5. Deduplication and merge
  6. Final confirmation

Note: When using Playwright for URL collection, additional browser tools (browser_navigate, browser_snapshot, browser_run_code, etc.) are required.

Sample Size Guidelines (Baseline: ~40 pages, majority representative)

Site size (after exclusions)Target pages
~40 pagesAll pages
40+ pages~40 pages (20-25 representative + 15-20 random)
200+ pages40-55 pages (25-30 representative + 15-25 random)

Step 4: Test Environment Confirmation

Clarify the environment for reproducibility.

Items to confirm

  • Browsers (target coverage)
  • Assistive technologies (AT)
  • Devices (desktop / mobile)
  • Tools used (automated checks, contrast tools, etc.)

Example prompt

Please confirm the test environment:
- Browsers (e.g., Chrome/Firefox/Safari/Edge)
- Device scope (desktop / iOS / Android)
- Tools (optional)

Step 5: Audit Plan Document Generation

Create the plan using references/audit-plan-template.md and save it with the Write tool.

Output requirements

  • Include overview, test method, target page list
  • Capture test environment, tools, schedule, and roles
  • Present the page list in a table

Confirm output path

I will save the audit plan as Markdown.
Please provide the output path (e.g., ./docs/wcag-audit-plan.md)

Notes

  • Mark unknowns as "TBD" and request follow-up input
  • Prioritize key user flows when selecting representative pages
  • Record a reproducible random sampling method (seed, steps)

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is planning-wcag-audit?

Perfect for Accessibility Agents needing structured WCAG audit planning and execution. Accessibility specialist skills plugin for Claude Code.

How do I install planning-wcag-audit?

Run the command: npx killer-skills add masuP9/a11y-specialist-skills/planning-wcag-audit. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for planning-wcag-audit?

Key use cases include: Automating WCAG audit planning for large-scale websites, Generating customized audit plans based on site-specific requirements, Confirming test environments for accessibility testing.

Which IDEs are compatible with planning-wcag-audit?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for planning-wcag-audit?

Requires knowledge of WAIC test guidelines and WCAG standards. Limited to web accessibility audits.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add masuP9/a11y-specialist-skills/planning-wcag-audit. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use planning-wcag-audit immediately in the current project.

Related Skills

Looking for an alternative to planning-wcag-audit or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

149.6k
0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

138.4k
0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
AI