Accessibility Review
Design skill, available on Zeplik
Accessibility Review is a ready-to-run design skill on Zeplik. ", "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. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
The Accessibility Review skill loads automatically when your request matches it, or you can invoke it directly by typing /accessibility-review 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 Accessibility Review skill can do
- Audit designs or pages against WCAG 2.1 AA criteria
- Check color contrast ratios for text and UI components
- Evaluate keyboard navigation, focus order, and focus indicators
- Generate a structured findings report with severity and fixes
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 Accessibility Review skill works
/accessibility-review
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Audit a design or page for WCAG 2.1 AA accessibility compliance.
Usage
/accessibility-review $ARGUMENTS
Audit for accessibility: @$1
WCAG 2.1 AA Quick Reference
Perceivable
- 1.1.1 Non-text content has alt text
- 1.3.1 Info and structure conveyed semantically
- 1.4.3 Contrast ratio >= 4.5:1 (normal text), >= 3:1 (large text)
- 1.4.11 Non-text contrast >= 3:1 (UI components, graphics)
Operable
- 2.1.1 All functionality available via keyboard
- 2.4.3 Logical focus order
- 2.4.7 Visible focus indicator
- 2.5.5 Touch target >= 44x44 CSS pixels
Understandable
- 3.2.1 Predictable on focus (no unexpected changes)
- 3.3.1 Error identification (describe the error)
- 3.3.2 Labels or instructions for inputs
Robust
- 4.1.2 Name, role, value for all UI components
Common Issues
- Insufficient color contrast
- Missing form labels
- No keyboard access to interactive elements
- Missing alt text on meaningful images
- Focus traps in modals
- Missing ARIA landmarks
- Auto-playing media without controls
- Time limits without extension options
Testing Approach
- Automated scan (catches ~30% of issues)
- Keyboard-only navigation
- Screen reader testing (VoiceOver, NVDA)
- Color contrast verification
- Zoom to 200% — does layout break?
Output
## Accessibility Audit: [Design/Page Name]
**Standard:** WCAG 2.1 AA | **Date:** [Date]
### Summary
**Issues found:** [X] | **Critical:** [X] | **Major:** [X] | **Minor:** [X]
### Findings
#### Perceivable
| # | Issue | WCAG Criterion | Severity | Recommendation |
|---|-------|---------------|----------|----------------|
| 1 | [Issue] | [1.4.3 Contrast] | 🔴 Critical | [Fix] |
#### Operable
| # | Issue | WCAG Criterion | Severity | Recommendation |
|---|-------|---------------|----------|----------------|
| 1 | [Issue] | [2.1.1 Keyboard] | 🟡 Major | [Fix] |
#### Understandable
| # | Issue | WCAG Criterion | Severity | Recommendation |
|---|-------|---------------|----------|----------------|
| 1 | [Issue] | [3.3.2 Labels] | 🟢 Minor | [Fix] |
#### Robust
| # | Issue | WCAG Criterion | Severity | Recommendation |
|---|-------|---------------|----------|----------------|
| 1 | [Issue] | [4.1.2 Name, Role, Value] | 🟡 Major | [Fix] |
### Color Contrast Check
| Element | Foreground | Background | Ratio | Required | Pass? |
|---------|-----------|------------|-------|----------|-------|
| [Body text] | [color] | [color] | [X]:1 | 4.5:1 | ✅/❌ |
### Keyboard Navigation
| Element | Tab Order | Enter/Space | Escape | Arrow Keys |
|---------|-----------|-------------|--------|------------|
| [Element] | [Order] | [Behavior] | [Behavior] | [Behavior] |
### Screen Reader
| Element | Announced As | Issue |
|---------|-------------|-------|
| [Element] | [What SR says] | [Problem if any] |
### Priority Fixes
1. **[Critical fix]** — Affects [who] and blocks [what]
2. **[Major fix]** — Improves [what] for [who]
3. **[Minor fix]** — Nice to have
If Connectors Available
If ~~design tool is connected:
- Inspect color values, font sizes, and touch targets directly from Figma
- Check component ARIA roles and keyboard behavior in the design spec
If ~~project tracker is connected:
- Create tickets for each accessibility finding with severity and WCAG criterion
- Link findings to existing accessibility remediation epics
Tips
- Start with contrast and keyboard — These catch the most common and impactful issues.
- Test with real assistive technology — My audit is a great start, but manual testing with VoiceOver/NVDA catches things I can't.
- Prioritize by impact — Fix issues that block users first, polish later.
Zeplik output presentation
Present the final deliverable as a single polished artifact: clear headings, tables where the content is tabular, fenced code where it is code. Lead with the deliverable itself; keep process commentary to a single short line. If the skill produced multiple files or sections, end with a compact list of them with one-line purposes.
How to use the Accessibility Review skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Accessibility Review skill right away.
Describe your design task
Ask in plain language, or type /accessibility-review to invoke the skill directly. Zeplik recognizes the Accessibility Review skill and applies its method.
Review and refine the result
Zeplik returns a clear, structured answer. Ask follow-ups in the same chat to refine it or take the next step.
Source and credit
- Author
- Anthropic
- License
- Apache-2.0
Adapted from the open-source anthropics/knowledge-work-plugins project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the Accessibility Review skill?
- Accessibility Review is a ready-to-run design skill on Zeplik. ", "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. Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
- How do I use Accessibility Review on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /accessibility-review 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 Accessibility Review skill use?
- Any model you choose. Zeplik works across every model in one chat, so the Accessibility Review skill runs on your preferred model for the task.
- Where does the Accessibility Review skill come from?
- The Accessibility Review skill is adapted from the open-source anthropics/knowledge-work-plugins project (Apache-2.0) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the Accessibility Review 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
- 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".
- Design Style MirrorUse when replicating the visual style of an existing website onto the user's project -- colors, type, spacing, aesthetic. Not for designing a new interface from scratch (use frontend-design).
More on Zeplik
Try Accessibility Review on Zeplik
Every model, one chat. Bring the Accessibility Review skill into your next conversation and let the assistant do the work.