How do I install the Spirit:accessibility skill?

Run npx skillmds@latest add alma-oss/spirit-accessibility in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spirit:accessibility safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spirit:accessibility?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spirit:accessibility free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spirit:accessibility?

alma-oss (@alma-oss) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spirit:accessibility by alma-oss — Agent Skill

Name: Spirit:accessibility
Author: alma-oss

Spirit:accessibility

Audit and improve web accessibility, semantics, ARIA, keyboard operability, focus management, contrast, following WCAG 2.2 guidelines. Always apply when adding or reviewing Spirit components and features. Also triggered by "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

alma-oss Updated Sep 17, 2026

File contents

Accessibility

Accessibility is a primary review lens for Spirit — design-system components are consumed everywhere, so an a11y regression multiplies. Target WCAG 2.2 AA. Spans React (.tsx), vanilla HTML, and SCSS.

A blocking finding is appropriate when a change removes or breaks accessibility that previously worked (keyboard trap, lost focus, missing accessible name on an interactive control).

Beyond the Component

A few WCAG 2.2-only success criteria are application-level and rarely actionable on an isolated component — note them for consumers but don't force them onto a primitive: consistent help (3.2.6), redundant entry (3.3.7), and accessible authentication (3.3.8).

References

references/accessibility-checklist.md — the detailed, actionable checklist (keyboard, screen readers, visual, forms, content, ARIA live regions, common anti-patterns, impact prioritization, and automated-testing commands).
references/accessibility-patterns.md — worked, Spirit-adapted code patterns (icon-button names, :focus-visible with the focus-ring token, error fields, live regions, modal focus management, form labels, reduced motion, and the new 2.2 patterns).

Frequently asked questions