wcag-audit-patterns
Audit WCAG Accessibility Patterns
Accessibility reviews often miss keyboard, contrast, and semantic issues. This skill gives Claude, Codex, and Claude Code a structured WCAG 2.2 audit checklist with remediation patterns.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "wcag-audit-patterns" from https://skillstore.io/skills/wshobson-wcag-audit-patterns.md and its manifest at https://skillstore.io/api/skills/wshobson-wcag-audit-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "wcag-audit-patterns". Review a checkout form for accessibility issues.
Expected outcome:
- Missing visible labels affect email and card fields.
- Error messages need programmatic association with each field.
- Recommended validation includes keyboard testing and screen reader confirmation.
Using "wcag-audit-patterns". Assess a custom dropdown before release.
Expected outcome:
- Keyboard support must include Enter, Space, Escape, and arrow navigation.
- The control needs a clear role, accessible name, and expanded state.
- Focus must remain visible and return predictably after selection.
Using "wcag-audit-patterns". Create a WCAG audit plan for a marketing site.
Expected outcome:
- Start with automated scans for every template.
- Add manual checks for headings, landmarks, contrast, zoom, and focus order.
- Prioritize blockers before visual polish or AAA enhancements.
Security Audit
SafeAll static findings are false positives caused by Markdown fences, accessibility examples, placeholder URLs, and resource links in SKILL.md. I found no executable code path, credential material, reconnaissance behavior, data exfiltration intent, or prompt injection text. The CLI examples should still be run only against approved targets.
Risk Factors
⚙️ External commands (45)
🌐 Network access (6)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/wshobson-wcag-audit-patterns/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/wshobson-wcag-audit-patterns?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/wshobson-wcag-audit-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wshobson-wcag-audit-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/wshobson-wcag-audit-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
wshobson. (2026). wcag-audit-patterns security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wshobson-wcag-audit-patterns/audits/7BibTeX citation
@techreport{wshobson-wshobson-wcag-audit-patterns-2026,
author = {wshobson},
title = {wcag-audit-patterns security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/wshobson-wcag-audit-patterns/audits/7},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "wcag-audit-patterns security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "wshobson"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/wshobson-wcag-audit-patterns/audits/7"
identifiers:
- type: other
value: "skillstore:wshobson-wcag-audit-patterns:audit:7"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
wshobson-wcag-audit-patterns
2026-08-21
sickn33-wcag-audit-patterns
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Audit a Product Flow
Review checkout, signup, or dashboard flows for WCAG 2.2 issues and remediation priorities.
Fix Frontend Components
Check custom controls, forms, focus states, and live regions before release.
Prepare Compliance Evidence
Structure findings, references, and validation steps for Section 508, ADA, or VPAT work.
Try These Prompts
Use wcag-audit-patterns to review this page for WCAG 2.2 A and AA issues. Group findings by impact and include fixes.
Review this component for keyboard, focus, label, role, and contrast issues. Explain each failed WCAG criterion and propose accessible markup.
Create a WCAG audit plan for this application. Include axe-core, pa11y, Lighthouse, keyboard testing, screen reader checks, and manual review steps.
Analyze these audit findings and create a prioritized remediation roadmap. Include owners, severity, WCAG references, validation steps, and regression test ideas.
Best Practices
- Combine automated checks with keyboard, screen reader, zoom, and color review.
- Tie every issue to a WCAG criterion, user impact, and validation method.
- Review real user flows, not only isolated components.
Avoid
- Treating a clean automated scan as full compliance.
- Adding ARIA before checking native HTML options.
- Fixing contrast or labels without retesting focus and keyboard behavior.