aravinds-wick/aravindhan-skills/a11y

Claude Code and agent skill by aravinds-wick/aravindhan-skills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Review and fix accessibility issues (WCAG 2.2 Level AA). Use when the user asks for an accessibility review, runs /a11y, or wants to fix a11y issues in UI components, forms, or pages.

Install

npx vskill@latest install aravinds-wick/aravindhan-skills/a11y

SKILL.md

The same SKILL.md was published earlier as aravinds-wick/aravindhan-skills/a11y.

Accessibility Review & Fix

Review and optionally fix accessibility issues. See .agent/rules/accessibility.mdc for standards.

Steps

  1. Determine scope automatically
  • Check git status --short for uncommitted changes
  • If path provided in command (e.g., /a11y path/to/file.js):
  • Use that specific file/directory
  • Else if working tree is clean AND file is open:
  • Auto-review currently open file (no prompt needed)
  • Else if uncommitted changes exist:
  • Ask: "Review uncommitted changes or current open file?"
  • Else (no file open, no changes):
  • Ask: "What file/directory would you like to review?"
  1. Immediately perform review
  • Don't prompt for action upfront
  • Always start with review-only mode
  • Show full accessibility report first
  1. Announce scope and start review
  • Start with clear scope announcement:

`` ## Accessibility Review: {filename} **Scope:** {scope description} **Files:** {list of files} **Component Type:** {detected type} ``

  • Examples:
  • "Scope: Currently open file (working tree clean)"
  • "Scope: 3 files with uncommitted changes"
  • "Scope: Specific file: path/to/Component.tsx"
  1. Load accessibility context
  • Reference .agent/rules/accessibility.mdc for WCAG 2.2 Level AA standards
  • Reference Intuit's 10 accessibility requirements
  • Check against common patterns (modals, forms, navigation, tables)
  1. Analyze the code
  • Detect component type (form, modal, navigation, table, page-level route, child component, etc.)
  • Check all 10 Intuit requirements:
  1. Alt text for images
  2. H tags and skip links
  3. Clear and meaningful link text
  4. Accessible forms (labels, errors, ARIA)
  5. Keyboard accessibility
  6. Accessible data tables
  7. Unique page titles (ONLY check for page-level/route components - NOT child or reusable components)
  8. Page zoom (relative font sizes)
  9. Multimedia (captions/transcripts)
  10. Color, contrast & flashing
  • Common mistakes check: Missing alt text, divs as buttons, missing labels, insufficient contrast, removed focus outline, no focus management, skipped heading levels, silent dynamic updates, unlabeled icons, ARIA overuse, page title set in child components (should only be in page-level components)
  1. Generate accessibility review report
  • CRITICAL: Output must have blank lines between EVERY section for proper markdown rendering
  • Format structure with explicit line breaks:

``` ## Accessibility Review: {filename}

Scope: {scope description}

File: {path}

Component Type: {detected type}


## ๐Ÿšจ Critical Issues (WCAG Violations)

### 1. {Issue Title} (Lines X-Y)

Problem: {description}

WCAG: {criterion violated}

Current:

``{startLine}:{endLine}:{filepath} {code} ``

Fix:

``{language} {corrected code} ``


## โš ๏ธ High Priority Issues

### 1. {Issue Title} (Lines X-Y)

Problem: {description}

WCAG: {criterion violated}

Current:

``{startLine}:{endLine}:{filepath} {code} ``

Fix:

``{language} {corrected code} ``


## ๐Ÿ“‹ Medium/Low Priority Recommendations

  • Brief list item 1
  • Brief list item 2

## ๐ŸŽฏ Priority Summary

PriorityCountMust Fix Before PR
CriticalXโœ… Yes
HighXโœ… Yes
MediumXโš ๏ธ Recommended

## ๐Ÿ“‹ Next Steps

  • [ ] Type "yes" to apply auto-fixes
  • [ ] Add jest-axe test if not present
  • [ ] Manual keyboard testing
  • [ ] Screen reader verification

## Would you like me to auto-fix these issues?

I can automatically fix:

  • โœ… {Issue 1}
  • โœ… {Issue 2}

Requires manual review:

  • ๐Ÿ’ก {Issue 1} - {reason}
  • ๐Ÿ’ก {Issue 2} - {reason}

Type "yes" to apply auto-fixes, or "no" to skip. ```

  • MANDATORY formatting rules (DO NOT SKIP):
  • ALWAYS add a blank line after every heading (## or ###)
  • ALWAYS add a blank line before and after every --- separator
  • ALWAYS add a blank line before and after every code block
  • ALWAYS add a blank line before and after every list
  • ALWAYS add a blank line before and after every table
  • Use ## for major sections, ### for subsections
  • Use checkboxes - [ ] for actionable items
  • Omit "What's Working Well" section - focus on issues only
  • Prioritize output - Critical and High issues first with full details
  1. Prompt user for auto-fix after showing review
  • Ask: "Would you like me to auto-fix these issues?"
  • Explain what will be fixed automatically vs. what requires manual review
  • Wait for user confirmation before proceeding
  1. If user confirms auto-fix: Categorize and apply fixes
  • Categorize findings by safety level:
  • Safe auto-fixes: Missing alt text, missing labels, missing button types, redundant ternaries, self-closing tags
  • Suggest only: Focus management, keyboard handlers, ARIA patterns requiring context, color contrast (needs design review), heading hierarchy changes (structural)
  • Apply safe auto-fixes:
  • Missing alt text: Add alt="" for decorative images
  • Missing form labels: Add <label htmlFor="id"> with sensible text
  • Missing button type: Add type="button" to buttons
  • Missing ARIA on icon buttons: Add aria-label with descriptive text
  • Redundant boolean ternary: Simplify {condition ? true : false} to {condition}
  • Self-closing tags: Fix <Component></Component> to <Component />
  • Missing required/aria-required: Add to form fields
  • Missing aria-invalid on errors: Add when error state exists
  • Generate fix report:

``` ## Accessibility Auto-Fix: {filename} Scope: {scope description}


### โœ… Auto-Fixed Issues ({count})

#### 1. {Issue Title} (Line X) - {Priority} Before: {old code}

After: {new code}

WCAG: {criterion if applicable}


### ๐Ÿ’ก Manual Fixes Required ({count})

#### 1. {Issue Title} (Lines X-Y) - {Priority: Critical/High} Problem: {description} WCAG: {criterion violated}

Suggested Fix: {code example}

Why manual: {explanation}


### ๐Ÿ“Š Summary

TypeCountStatus
Auto-fixedXโœ… Applied
Manual required (Critical)Xโš ๏ธ Action needed
Manual required (High)Xโš ๏ธ Action needed
SuggestionsXโ„น๏ธ Optional

### ๐Ÿ“‹ Next Steps

  • [ ] Review auto-fixed changes
  • [ ] Address {X} critical manual fixes
  • [ ] Run tests: npm test {test-file}
  • [ ] Add jest-axe test if missing

```

  1. Apply changes to file
  • Use search_replace tool for each fix
  • Make one fix at a time
  • Verify each change before moving to next
  • Batch related fixes (e.g., all missing alt text in one pass)
  1. Validate changes
  • Ensure syntax is valid
  • Check imports still work
  • Verify no duplicate attributes added
  • Confirm proper indentation preserved
  • Run linter if applicable
  1. Ask user if they want to commit and create PR
  • Prompt: "Would you like me to commit these changes and create a PR?"
  • If YES, proceed to git workflow
  • If NO, stop here (changes remain uncommitted)
  1. Git workflow (if user confirms) - Request ["git_write", "network"] permissions upfront
  • Extract Jira ticket from branch name
  • Check if on feature branch:
  • If on main: Create new branch {ticket-prefix}-{ticket-num}-a11y-{filename}
  • Example: XP-1234-a11y-login-page
  • Stage ONLY modified file(s): git add {modified_files}
  • Commit: "[{TICKET}] Fix accessibility issues in {filename}"
  • Push to origin
  1. Create PR (if git workflow completed)
  • Environment detection:
  • Try to detect if running in Cloud Workspace (check for CLOUD_WORKSPACE env var or test gh availability)
  • If gh pr create is not available or fails, proceed with manual PR creation flow
  • LOCAL (gh available):
  • Read .github/pull_request_template.md for template structure
  • Create PR: gh pr create --title "[{TICKET}] Fix accessibility issues in {filename}" --body "{populated_template}" --label a11y-cursor-command
  • Populate ALL template sections (see below for details)
  • Apply labels: a11y-cursor-command, accessibility
  • Submit as regular PR (not draft)
  • CLOUD WORKSPACE or gh unavailable:
  • Read .github/pull_request_template.md for template structure
  • Prepare populated PR template body (see below for details)
  • Display to user:

``` ## โœ… Changes Committed and Pushed

Branch: {branch-name} Commit: [{TICKET}] Fix accessibility issues in {filename}

## ๐Ÿ“ Create PR Manually

Cloud Workspace Limitation: PR creation via CLI is not supported.

Click here to create PR: https://github.your-company.com/mailchimp-monolith/mailchimp/compare/main...{branch-name}?expand=1

PR Title (copy this): [{TICKET}] Fix accessibility issues in {filename}

PR Body (copy this): {populated_template}

Labels to add: a11y-cursor-command, accessibility ```

  • Template sections to populate (for both local and cloud):
  • Background context: Accessibility audit findings, WCAG compliance requirements
  • Change summary: List of fixed issues (Critical, High, Medium) with before/after
  • Steps to test:
  • Test with keyboard navigation (Tab, Enter, Escape)
  • Test with screen reader (VoiceOver on macOS, NVDA on Windows)
  • Test at 200% browser zoom
  • Verify color contrast with browser tools
  • Risk mitigation table:
  • ๐Ÿšฉ Flag/Experiment name: N/A (accessibility fix)
  • ๐ŸŒŠ Splatter zone: "{component/page name} - visual/markup changes only"
  • ๐Ÿ‘€ Monitoring: Manual accessibility testing, jest-axe tests
  • ๐Ÿ’ฌ Slack Channel: #mc-accessibility or {team_channel}
  • ๐ŸŽŸ๏ธ Jira ticket: https://jira.your-company.com/browse/{TICKET}
  1. Generate final checklist
  • Show user remaining manual tasks:

```markdown ## โœ… Auto-Fixed Issues ({count})

  • [x] {Issue 1}
  • [x] {Issue 2}

## โš ๏ธ Manual Fixes Required ({count})

  • [ ] {Issue 1} - See PR description for details
  • [ ] {Issue 2} - See PR description for details

## ๐Ÿงช Testing Checklist

  • [ ] Keyboard navigation test
  • [ ] Screen reader test (VoiceOver/NVDA)
  • [ ] 200% zoom test
  • [ ] Color contrast verification
  • [ ] Add jest-axe test if missing

## ๐Ÿ“Ž PR Created

PR #{pr_number}: {pr_url} ```

Safety Rules (Auto-fix mode)

Always auto-fix:

  • Empty alt text for decorative images
  • Missing form field labels (with sensible defaults)
  • Missing button types
  • Missing aria-label on icon-only buttons
  • Boolean ternary simplification
  • Self-closing tag syntax

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/aravinds-wick/aravindhan-skills/a11y/badge)](https://verified-skill.com/skills/aravinds-wick/aravindhan-skills/a11y)

Something wrong with this skill or its page? Tell us.