From wicked-garden
Accessibility audit, compliance evaluation, and implementation guidance — WCAG 2.1 AA, keyboard navigation, screen readers, ARIA patterns, and color contrast. Use when: "accessibility audit", "a11y compliance", "WCAG evaluation", "audit for accessibility", "remediation plan", "compliance report", "make this accessible", "keyboard navigation", "screen reader support", "color contrast", "ARIA patterns", "semantic HTML", "accessible component"
npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardenThis skill uses the workspace's default tool permissions.
WCAG 2.1 Level AA compliance auditing and inclusive design guidance.
refs/aria-patterns-basics.mdrefs/aria-patterns-dynamic.mdrefs/aria-patterns-interactive.mdrefs/audit-report-findings.mdrefs/audit-report-results.mdrefs/common-violations-html-css.mdrefs/common-violations-interactive.mdrefs/keyboard-testing-basics.mdrefs/keyboard-testing-patterns.mdrefs/screen-reader-testing-advanced.mdrefs/screen-reader-testing-commands.mdrefs/wcag-checklist.mdProvides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
WCAG 2.1 Level AA compliance auditing and inclusive design guidance.
Accessibility is not optional. It's legal compliance, user respect, and better code.
Information must be presentable to users in ways they can perceive.
Interface components must be operable.
Information and operation must be understandable.
Content must work with assistive technologies.
Full WCAG checklists: See refs/wcag-checklist.md
Use the Read tool on a screenshot file, or capture via browser automation if available (e.g., Playwright, Puppeteer, or an MCP browser tool). For automated WCAG scanning, use axe DevTools, Lighthouse, WAVE, or pa11y.
Full keyboard testing guide: See refs/keyboard-testing-basics.md and refs/keyboard-testing-patterns.md
Full screen reader guide: See refs/screen-reader-testing-commands.md and refs/screen-reader-testing-advanced.md
# Find potential issues
wicked-garden:search "<div.*onclick" --type html # Non-semantic buttons
wicked-garden:search "<img(?!.*alt)" --type html # Missing alt
wicked-garden:search "aria-" --type html # ARIA usage
<!-- ✗ Missing alt -->
<img src="profile.jpg">
<!-- ✓ Fixed -->
<img src="profile.jpg" alt="Profile of Jane Doe">
<!-- ✗ Non-semantic button -->
<div onclick="submit()">Submit</div>
<!-- ✓ Fixed -->
<button onclick="submit()">Submit</button>
<!-- ✗ Form without label -->
<input type="text" placeholder="Email">
<!-- ✓ Fixed -->
<label for="email">Email</label>
<input type="text" id="email">
<!-- ✗ Low contrast -->
<p style="color: #999; background: #fff;">Text</p> /* 2.5:1 */
<!-- ✓ Fixed -->
<p style="color: #666; background: #fff;">Text</p> /* 4.7:1 */
More examples: See refs/common-violations-html-css.md and refs/common-violations-interactive.md
## A11y Audit
**WCAG**: {✓ Pass | ⚠ Issues | ✗ Fail}
- Perceivable: {✓⚠✗}
- Operable: {✓⚠✗}
- Understandable: {✓⚠✗}
- Robust: {✓⚠✗}
### Critical (Level A)
- Issue: {description}
- WCAG: {criterion}
- Fix: {specific code}
### Major (Level AA)
- Issue: {description}
- WCAG: {criterion}
- Fix: {recommendation}
### Recommendations
1. {Priority fixes}
Full report template: See refs/audit-report-findings.md and refs/audit-report-results.md
Tools:
# Color contrast check
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/product/contrast-check.py" "#666" "#fff"
# Track issues via native TaskCreate
# TaskCreate(
# subject="A11y: {issue}",
# metadata={
# "event_type": "task",
# "chain_id": "a11y-review.root",
# "source_agent": "a11y-expert",
# "priority": "P0"
# }
# )
Collaboration:
Accessibility auditing can leverage available integrations by capability:
| Capability | Discovery Patterns | Provides |
|---|---|---|
| A11y testing | axe, a11y, accessibility | Automated WCAG scanning |
| Browser testing | playwright, puppeteer | Screenshots, DOM snapshots |
| Performance | lighthouse | Combined a11y + performance audit |
Discover available integrations via capability detection. Fall back to local contrast-check.py when none available.
Detailed guides in refs/:
Legal context: ADA (US), Section 508 (gov), EAA (EU). ~15-20% of users need accessibility; screen readers double as SEO bots.