Accessibility Per Component

by murphytrueman

Accessibility Per Component is a Quality skill for Claude Code, published by murphytrueman in design-system-ops.

176 stars7 forkson murphytrueman/design-system-opsAdded 2026/09/07+1% in starsRepository updated 2026/08/22

View source on GitHub Download repo ZIP

claude-codeclaude-code-plugindesign-systemdesign-systemsdesign-tokensfigmaskills

Install in seconds

Install Accessibility Per Component

Copy Accessibility Per Component into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/murphytrueman/design-system-ops/tree/main/skills/accessibility-per-component ~/.claude/skills/accessibility-per-component

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/murphytrueman/design-system-ops.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/accessibility-per-component/SKILL.md in murphytrueman/design-system-ops
Installs to: ~/.claude/skills/accessibility-per-component
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1817 skills

What Accessibility Per Component does

Accessibility Per Component runs a structured accessibility audit on a single design system component. It checks keyboard use, screen reader behavior, colour contrast, focus, and ARIA against WCAG 2.1 AA.

Accessibility Per Component is cataloged under Quality on DirSkills. Accessibility Per Component comes from a repository tagged claude-code, claude-code-plugin, design-system, design-systems and design-tokens.

Documentation

README

Excerpt

Accessibility per component

A skill for running a structured accessibility audit on a design system component, covering five dimensions: keyboard navigation, screen reader experience, colour and contrast, focus management, and ARIA implementation. Produces a PASS/FAIL/WARN per criterion with specific remediation guidance.

Context

Accessibility audits at the component level are more valuable than page-level or system-level assessments because they fix the problem at its source. A component with a correct accessibility implementation propagates that correctness to every product that uses it. A component with an accessibility bug propagates that bug at the same scale.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Accessibility Per Component

What else does murphytrueman publish alongside Accessibility Per Component?
Accessibility Per Component is one of 25 skills that DirSkills catalogs from murphytrueman/design-system-ops, the repository it ships in. Its siblings there include AI Component Description, Adoption Report and Backlog Generator. Each one is a separate skill with its own page in this directory, installs the same way Accessibility Per Component does, and is maintained by murphytrueman in that same repository. The rest of the collection is listed on the murphytrueman/design-system-ops page.
How does Accessibility Per Component compare to other Quality skills?
Accessibility Per Component ranks #1689 by stars among the 1817 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Accessibility Per Component against them. Open each page to compare what they document and how they install.