planning-wcag-audit — community planning-wcag-audit, a11y-specialist-skills, community, ide skills

v1.0.0

About this Skill

Ideal for Accessibility Agents requiring structured WCAG audit planning and test environment setup. WCAG audit planning support based on WAIC test guidelines. Helps determine audit scope, page selection method, and generates audit plan documents.

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

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
42
Canonical Locale
en
Detected Body Locale
en

Ideal for Accessibility Agents requiring structured WCAG audit planning and test environment setup. WCAG audit planning support based on WAIC test guidelines. Helps determine audit scope, page selection method, and generates audit plan documents.

Core Value

Empowers agents to streamline WCAG audits by organizing scope, selecting representative pages, and confirming test environments, leveraging WAIC test guidelines and producing comprehensive audit plan documents in various formats, including HTML and markdown.

Ideal Agent Persona

Ideal for Accessibility Agents requiring structured WCAG audit planning and test environment setup.

Capabilities Granted for planning-wcag-audit

Automating site information gathering for WCAG audits
Generating audit plans based on WAIC test guidelines
Selecting representative pages for testing
Confirming test environments for accessibility audits

! Prerequisites & Limits

  • Requires knowledge of WAIC test guidelines
  • Limited to WCAG audit planning and does not perform actual testing

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

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

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?

Ideal for Accessibility Agents requiring structured WCAG audit planning and test environment setup. WCAG audit planning support based on WAIC test guidelines. Helps determine audit scope, page selection method, and generates audit plan documents.

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 site information gathering for WCAG audits, Generating audit plans based on WAIC test guidelines, Selecting representative pages for testing, Confirming test environments for accessibility audits.

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. Limited to WCAG audit planning and does not perform actual testing.

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.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

planning-wcag-audit

Install planning-wcag-audit, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

日本語版 (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)

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

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer