carl0s

Accessibility Playbook — Development skill for Claude Code

Development community

Multi-book accessibility knowledge base as a Claude Code / Amp skill.

How to install Accessibility Playbook

This entry records only its repository, not the path inside it, so there is no exact command to give. Open carl0s/accessibility-playbook and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Accessibility Playbook does

Multi-book accessibility knowledge base as a Claude Code / Amp skill —

Alternatives in Development

Rb Refresh — Rebuild the repobrain project knowledge base after significant changes 1.3k ★
Ag Refresh — Rebuild the antigravity project knowledge base after significant changes 1.2k ★
Agent Teams Configuration — This file defines coordinated multi-agent workflows for enterprise accessibility scanning in the Claude Code e 219 ★

README

accessiblity-playbook

Multi-book accessibility knowledge base as a Claude Code / Amp skill — distills the Accessibility Playbook, Giving a Damn About Accessibility, and the Appt Handbook into on-demand frameworks for service, design, and WCAG/mobile.

What this skill does

It gives Claude Code (or Amp) a **curated, source-tagged accessibility reference** that loads only when you need it. Instead of relying on the model's generic, sometimes-outdated accessibility knowledge, it pulls answers from three vetted books — each covering a different layer of the problem:

Service & organization [P] — AccessAbility Playbook (Gov. of Canada): how to deliver accessible client service in person, by phone, and online; barrier audits, personas, culture change.
Mindset & advocacy [GD] — Giving a Damn About Accessibility (Sheri Byrne-Haber): how to win the argument internally, counter resistance, avoid overlay snake-oil, and go from compliant to genuinely great.
Build & WCAG [Appt] — Appt Accessibility Handbook: WCAG 2.2 (POUR) criteria at A/AA, mobile-app specifics, contrast/target-size/keyboard rules, and a shift-left testing approach.

The skill ships a `SKILL.md` index plus per-chapter files, a glossary, reusable patterns, and a cheatsheet — so Claude reads the *relevant* chapter on demand rather than guessing.

What you can use it for

During code review or design — "is this contrast ratio compliant?", "what's the minimum touch-target size?", "does this custom component have proper Name/Role/Value?"
Writing UI copy & forms — plain-language checks, accessible error messages, time-limit and save-and-resume patterns.
Making the case for accessibility — turn "only a few users need this" or "where's the ROI?" into a grounded counter-argument (the 6 resistance archetypes, the substitution test).
Auditing a service or product — the 5 Barrier Areas, the Channel × Disability matrix, the maturity/shift-left model.
**Looking up a s