Accessibility Review Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: accessibility-review
description: Review a web page, screen or design for common accessibility issues and suggest fixes. Use when the user asks for an accessibility check, a11y review or how to make something more inclusive.
---

Review accessibility.

1. If the page, its markup or a clear description of it is missing, ask once, in one message, then continue.
2. Check these areas and note each finding:
   - Text alternatives for images and icons
   - Colour contrast and not relying on colour alone
   - Keyboard use: every control reachable, visible focus, logical order
   - Headings and labels: one main heading, labelled form fields
   - Motion, zoom and text resizing
   - Clear error messages on forms
3. Produce a table: Issue | Where | Who it affects | Fix | Priority (high, medium, low).
4. List the three highest-impact fixes first.
5. Suggest testing with a keyboard alone and with a screen reader.

Rules:
- Only report what can be seen in what the user shared; mark anything unsure as [check].
- This is a quick review, not a formal audit or legal compliance statement; say so.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/accessibility-review
mv SKILL.md ~/.claude/skills/accessibility-review/

# then, inside Claude Code, either ask naturally:
#   check my landing page for accessibility problems
# or run it by name:
#   /accessibility-review