Agent skill

Accessibility Compliance

by vmDeshpande in vmDeshpande/ai-agent-automation

Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support.

Apache-2.0Auto-check passedFrontend & Design

Install Accessibility Compliance

skills CLI
$ npx skills add vmDeshpande/ai-agent-automation --skill accessibility-compliance -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vmDeshpande/ai-agent-automation accessibility-compliance --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vmDeshpande/ai-agent-automation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/accessibility-compliance .claude/skills/accessibility-compliance && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
accessibility-compliance
GitHub stars
178
Used in
3 other repos
Token cost
~601 tokens
SKILL.md length
257 words
Files
5 (incl. references)
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support.

  • Works in 8 steps: Use Semantic HTML: Prefer native… → Test with Real Users: Include people… → Keyboard First: Design interactions to… → …
  • Auditing accessibility
  • SKILL.md covers When to Use This Skill, Detailed patterns and worked…, Best Practices and Common Issues, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Accessibility Compliance is an agent skill from vmDeshpande/ai-agent-automation. Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.

Its SKILL.md is about 600 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/aria-patterns.md`, `references/details.md` and `references/mobile-accessibility.md`).

It sits in Frontend & Design, covering Accessibility. It works with Next.js, React and Node.js. The repository describes itself as: Modular AI agent workflow automation platform with schedulers, tools, and observability. https://vmdeshpande.github.io/ai-automation-platform-website/. The licence is Apache-2.0.

When your agent uses it

  • Auditing accessibility
  • Implementing ARIA patterns
  • Building for screen readers
  • Ensuring inclusive user experiences

Example prompts

  • “/accessibility-compliance”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Use Semantic HTML: Prefer native elements over ARIA when possible
  2. Test with Real Users: Include people with disabilities in user testing
  3. Keyboard First: Design interactions to work without a mouse
  4. Don't Disable Focus Styles: Style them, don't remove them
  5. Provide Text Alternatives: All non-text content needs descriptions
  6. Support Zoom: Content should work at 200% zoom
  7. Announce Changes: Use live regions for dynamic content
  8. Respect Preferences: Honor prefers-reduced-motion and prefers-contrast

What it can do on your machine

Read from SKILL.md and the folder at commit 86b6072. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Accessibility Compliance loads about 601 tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 71 tokens; SKILL.md has 257 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~601
With references · SKILL.md plus every file in references/, read only if the agent opens them
~13k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vmDeshpande/ai-agent-automation at commit 86b6072, republished under its Apache-2.0 licence (© vmDeshpande). 257 words, ~601 tokens.

Download SKILL.mdSave it as .claude/skills/accessibility-compliance/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
accessibility-compliance
description
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.

Accessibility Compliance

Master accessibility implementation to create inclusive experiences that work for everyone, including users with disabilities.

When to Use This Skill

  • Implementing WCAG 2.2 Level AA or AAA compliance
  • Building screen reader accessible interfaces
  • Adding keyboard navigation to interactive components
  • Implementing focus management and focus trapping
  • Creating accessible forms with proper labeling
  • Supporting reduced motion and high contrast preferences
  • Building mobile accessibility features (iOS VoiceOver, Android TalkBack)
  • Conducting accessibility audits and fixing violations

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

  1. Use Semantic HTML: Prefer native elements over ARIA when possible
  2. Test with Real Users: Include people with disabilities in user testing
  3. Keyboard First: Design interactions to work without a mouse
  4. Don't Disable Focus Styles: Style them, don't remove them
  5. Provide Text Alternatives: All non-text content needs descriptions
  6. Support Zoom: Content should work at 200% zoom
  7. Announce Changes: Use live regions for dynamic content
  8. Respect Preferences: Honor prefers-reduced-motion and prefers-contrast

Common Issues

  • Missing alt text: Images without descriptions
  • Poor color contrast: Text hard to read against background
  • Keyboard traps: Focus stuck in component
  • Missing labels: Form inputs without associated labels
  • Auto-playing media: Content that plays without user initiation
  • Inaccessible custom controls: Recreating native functionality poorly
  • Missing skip links: No way to bypass repetitive content
  • Focus order issues: Tab order doesn't match visual order

Testing Tools

  • Automated: axe DevTools, WAVE, Lighthouse
  • Manual: VoiceOver (macOS/iOS), NVDA/JAWS (Windows), TalkBack (Android)
  • Simulators: NoCoffee (vision), Silktide (various disabilities)

© vmDeshpande, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in .agents/skills/accessibility-compliance of vmDeshpande/ai-agent-automation.

  • SKILL.md
  • references/aria-patterns.md
  • references/details.md
  • references/mobile-accessibility.md
  • references/wcag-guidelines.md

Open the folder on GitHubat commit 86b6072

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in vmDeshpande/ai-agent-automation, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Accessibility Compliance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Accessibility Compliance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Accessibility Compliance this skillvmDeshpande/ai-agent-automation1783 repos~601Automated safety check: PassApache-2.0
UI/UX Design System AdvisorGalaxy-Dawn/claude-scholar5.7k1 repos~1.1kAutomated safety check: PassMIT
UI Design Systemtry-works/role-model118—~5kAutomated safety check: PassMIT
Design Code for Any Frameworkplugin87/ux-ui-agent-skills1.6k—~1.7kAutomated safety check: PassMIT
Frontend A11yaffaan-m/ECC276k1 repos~3.2kAutomated safety check: PassMIT
Motion Foundationsaffaan-m/ECC276k1 repos~2.4kAutomated safety check: PassMIT

Similar skills

  • UI/UX Design System Advisor

    Galaxy-Dawn/claude-scholar

    Turns a vague UI request into a concrete design system with style, palette, typography and layout guidance from a search script, plus stack-specific implementation advice.

    5.7k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • UI Design System

    try-works/role-model

    React UI component systems with TailwindCSS + Radix + shadcn/ui.

    118 GitHub stars~5k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Design Code for Any Framework

    plugin87/ux-ui-agent-skills

    Generates complete, accessible, token-driven UI component code for a chosen framework such as React with Tailwind, SwiftUI, Vue, Flutter or Jetpack Compose.

    1.6k GitHub stars~1.7k tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed
  • Frontend A11y

    affaan-m/ECC

    Accessibility patterns for React and Next.js — semantic HTML, ARIA attributes, form labeling, keyboard navigation, focus management, and screen reader support.

    276k GitHub starsUsed in 1 repo~3.2k tokens
    Frontend & DesignAuto-check passed
  • Motion Foundations

    affaan-m/ECC

    Motion tokens, spring presets, performance rules, device adaptation, accessibility enforcement, and SSR safety for React / Next.js using motion/react.

    276k GitHub starsUsed in 1 repo~2.4k tokens
    Frontend & DesignAuto-check passed
  • Discover Frontend

    rand/cc-polymath

    Automatically discover frontend development skills when working with React, Next.js, UI components, state management, data fetching, forms, accessibility, performance optimization, or SEO.

    181 GitHub stars~2.4k tokensUpdated 7 mo ago
    Frontend & DesignAuto-check passed

More from vmDeshpande/ai-agent-automation

  • Wcag Audit Patterns

    vmDeshpande/ai-agent-automation

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.

    178 GitHub starsUsed in 11 repos~610 tokens
    Auto-check passed
  • Core Web Vitals

    vmDeshpande/ai-agent-automation

    Optimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking.

    178 GitHub starsUsed in 4 repos~3.6k tokens
    Auto-check passed

Questions about Accessibility Compliance

What does Accessibility Compliance do?

Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Accessibility Compliance is an agent skill from vmDeshpande/ai-agent-automation.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support.

When should I use Accessibility Compliance?

Accessibility Compliance fits situations like: auditing accessibility; implementing ARIA patterns; building for screen readers; ensuring inclusive user experiences.

How do I install Accessibility Compliance in Claude Code?

Run `npx skills add vmDeshpande/ai-agent-automation --skill accessibility-compliance -a claude-code`. Or copy the skill folder (.agents/skills/accessibility-compliance in vmDeshpande/ai-agent-automation) into .claude/skills/accessibility-compliance in your project. Claude Code loads it when a task matches its description.

How do I install Accessibility Compliance in Codex?

Run `npx skills add vmDeshpande/ai-agent-automation --skill accessibility-compliance -a codex`. Or copy the skill folder (.agents/skills/accessibility-compliance in vmDeshpande/ai-agent-automation) into .agents/skills/accessibility-compliance in your project. Codex loads it when a task matches its description.

Can I use Accessibility Compliance in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vmDeshpande/ai-agent-automation --skill accessibility-compliance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/accessibility-compliance, .gemini/skills/accessibility-compliance, .github/skills/accessibility-compliance and .opencode/skills/accessibility-compliance in your project.

What does Accessibility Compliance need to run?

SKILL.md names no scripts, command-line tools or credentials: Accessibility Compliance is instructions for the agent only.

Does Accessibility Compliance access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Accessibility Compliance safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Accessibility Compliance use?

Accessibility Compliance is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Accessibility Compliance use?

About 601 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 13k tokens, read only when the agent opens those files.

What are the alternatives to Accessibility Compliance?

Skills that share tags, products or a category with Accessibility Compliance: UI/UX Design System Advisor (Galaxy-Dawn/claude-scholar, 5.7k stars), UI Design System (try-works/role-model, 118 stars), Design Code for Any Framework (plugin87/ux-ui-agent-skills, 1.6k stars) and Frontend A11y (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Accessibility Compliance?

vmDeshpande (a GitHub user) maintains it in vmDeshpande/ai-agent-automation, which has 178 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 12, 2026.

Source: vmDeshpande/ai-agent-automation on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.