How do I install the Accessibility skill?

Run npx skillmds add shipshitdev/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 Accessibility safe to use?

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

Which AI agents work with 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 Accessibility free to use?

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

Who published Accessibility?

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

Accessibility by shipshitdev — Agent Skill

Name: Accessibility
Rating: 4.2 (5 reviews)
Author: shipshitdev

Accessibility

Applies WCAG 2.1 AA to web UI work and fixes what fails — semantic HTML, ARIA roles and states, keyboard access, focus management, contrast ratios, and screen-reader verification — while a component is being built or reviewed. Use when the user names accessibility, a11y, WCAG, ARIA, keyboard navigation, focus traps, screen readers, or contrast. For a scored multi-dimension quality report, use `audit`; for design-token consistency, use `design-consistency-auditor`.

shipshitdev 529cd9b 3 files · 19.9 KB Updated Sep 9, 2026

File contents

Accessibility (a11y) Skill

When to Use

Use when you're:

Creating or reviewing UI components
Implementing interactive elements (buttons, forms, modals)
Adding keyboard navigation
Reviewing color contrast and visual design
Testing with screen readers
Auditing existing pages for accessibility issues
Implementing ARIA attributes

Quick Workflow

Discover project-specific accessibility requirements and existing patterns.
Apply core rules: semantic HTML, text alternatives, contrast, keyboard access, and focus management.
Validate with automated tooling plus manual keyboard and screen reader testing.
Document issues and fixes with examples.

WCAG Principles

Perceivable: text alternatives, contrast, responsive support.
Operable: keyboard access, focus management, timing.
Understandable: clear language, predictable behavior.
Robust: valid HTML and ARIA usage.

References

Full guide: WCAG patterns, component examples, and testing checklists

audit — a scored 0-4 sweep across accessibility, performance, theming, responsive design, and anti-patterns when no single dimension is named.
design-consistency-auditor — token drift, hardcoded colors, and design-system divergence.

Frequently asked questions