WCAG Audit Patterns
Design skill, available on Zeplik
WCAG Audit Patterns is a ready-to-run design skill on Zeplik. 2 conformance audits: success criteria, A/AA/AAA levels, violation reporting, remediation. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured checklist you can keep and reuse: Checklist artifact -- actionable checked items with state, grouped by phase (see artifact-templates/checklist.md).
The WCAG Audit Patterns skill loads automatically when your request matches it, or you can invoke it directly by typing /wcag-audit-patterns in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the WCAG Audit Patterns skill can do
- Map violations to specific WCAG 2.2 success criteria and conformance levels
- Classify issues by impact tier from critical blockers to moderate
- Apply POUR principles to structure a formal audit report
- Recommend remediation strategies favoring semantic HTML over ARIA
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the WCAG Audit Patterns skill works
/wcag-audit-patterns
Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies. This skill is for formal, criteria-mapped conformance work; for an informal accessibility pass on a design, use accessibility-review.
When to Use
- Conducting accessibility audits
- Fixing WCAG violations
- Implementing accessible components
- Preparing for accessibility litigation exposure
- Meeting ADA/Section 508 requirements
- Achieving VPAT compliance
Core Concepts
1. WCAG Conformance Levels
| Level | Description | Required For |
|---|---|---|
| A | Minimum accessibility | Legal baseline |
| AA | Standard conformance | Most regulations |
| AAA | Enhanced accessibility | Specialized needs |
2. POUR Principles
Perceivable: Can users perceive the content?
Operable: Can users operate the interface?
Understandable: Can users understand the content?
Robust: Does it work with assistive tech?
3. Common Violations by Impact
Critical (Blockers):
- Missing alt text for functional images
- No keyboard access to interactive elements
- Missing form labels
- Auto-playing media without controls
Serious:
- Insufficient color contrast
- Missing skip links
- Inaccessible custom widgets
- Missing page titles
Moderate:
- Missing language attribute
- Unclear link text
- Missing landmarks
- Improper heading hierarchy
Detailed Patterns and Worked Examples
Detailed pattern documentation (audit workflows, testing tooling, criterion-by-criterion checks, remediation code) lives in references/details.md. Read that file when the navigation tier above is insufficient.
Best Practices
Do's
- Start early -- accessibility from the design phase
- Test with real users -- disabled users provide the best feedback
- Automate what you can -- 30-50% of issues are detectable automatically
- Use semantic HTML -- reduces ARIA needs
- Document patterns -- build an accessible component library
Don'ts
- Don't rely only on automated testing -- manual testing is required
- Don't use ARIA as the first solution -- native HTML first
- Don't hide focus outlines -- keyboard users need them
- Don't disable zoom -- users need to resize
- Don't use color alone -- multiple indicators needed
Usage
/wcag-audit-patterns $ARGUMENTS
How to use the WCAG Audit Patterns skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the WCAG Audit Patterns skill right away.
Describe your design task
Ask in plain language, or type /wcag-audit-patterns to invoke the skill directly. Zeplik recognizes the WCAG Audit Patterns skill and applies its method.
Review and refine the result
Zeplik returns a structured checklist you can edit, download, and reuse. Ask follow-ups to refine it.
Source and credit
- Author
- wshobson
- License
- MIT
Adapted from the open-source wshobson/agents project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the WCAG Audit Patterns skill?
- WCAG Audit Patterns is a ready-to-run design skill on Zeplik. 2 conformance audits: success criteria, A/AA/AAA levels, violation reporting, remediation. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer. It returns a structured checklist you can keep and reuse: Checklist artifact -- actionable checked items with state, grouped by phase (see artifact-templates/checklist.md).
- How do I use WCAG Audit Patterns on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /wcag-audit-patterns in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the WCAG Audit Patterns skill use?
- Any model you choose. Zeplik works across every model in one chat, so the WCAG Audit Patterns skill runs on your preferred model for the task.
- Where does the WCAG Audit Patterns skill come from?
- The WCAG Audit Patterns skill is adapted from the open-source wshobson/agents project (MIT) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the WCAG Audit Patterns skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related design skills
- Accessibility ReviewUse when the user asks to audit a design or page for accessibility — "check a11y", "is this accessible?", "run a WCAG audit" — covering color contrast, keyboard navigation, focus order, touch target size, and screen reader behavior against WCAG 2.1 AA before handoff.
- Brand Guidelines BuilderUse when the user wants Anthropic's official brand look-and-feel applied to an artifact — brand colors, typography, visual formatting, company design standards. Trigger: "use Anthropic branding", "apply our brand style". Visual identity only; not for brand voice or tone in writing (use brand-voice-enforcement).
- Brand Landing PageRuns a brand interview with no established visual direction, then generates deployment-ready landing-page HTML. Not for dashboards or app UI (use frontend-design).
- Design CritiqueUse when the user shares a design, mockup, screenshot, or Figma link and asks for feedback — "review this design", "critique this mockup", "what do you think of this screen?". Gives structured feedback on usability, hierarchy, and consistency. Not for a WCAG audit (use accessibility-review).
- Design Delivery NavigatorUse to chain UI delivery across skills -- research, design, systemize, accessibility, handoff. Not for a single critique (use design-critique).
- Design Handoff PackageUse when a design is ready for engineering and the user wants a developer handoff spec — layout, design tokens, component props, interaction states, responsive breakpoints, edge cases, animation details. Trigger: "write the handoff spec", "prep this design for devs", "spec this screen out".
More on Zeplik
Try WCAG Audit Patterns on Zeplik
Every model, one chat. Bring the WCAG Audit Patterns skill into your next conversation and let the assistant do the work.