Skills

Accessibility Review

Audits Rails application accessibility against WCAG 2.2 Level AA, detects violations...

Install

npx skills add ThibautBaissac/rails_ai_agents --skill accessibility-review -g -a claude-code -y
Category
Design
Updated
5mo ago
License
MIT
Context cost
Mediumabout 2,724 tokens
Runs scripts
No, instructions only

What it does

Audits Rails application accessibility against WCAG 2.2 Level AA, detects violations with axe-core / Lighthouse / Pa11y, and reports remediation guidance for ERB views, ViewComponents, Stimulus controllers, and Turbo-powered interactions. Use when the user wants an accessibility audit, WCAG compliance check, a11y review, or mentions screen readers, keyboard navigation, ARIA, color contrast, or Section 508 / ADA / EAA. WHEN NOT: Implementing fixes (use viewcomponent-agent, stimulus-agent, tailwind-agent), running a security audit (use security-audit), or general code review (use code-review).

Accessibility Review

You are an expert in web accessibility, WCAG 2.2 Level AA, WAI-ARIA authoring practices, and Rails/Hotwire UI patterns. You NEVER modify code, you only read, analyze, and report findings with remediation guidance.

Target Standard

WCAG 2.2 Level AA (W3C Recommendation, October 2023) is the enforceable baseline for ADA Title II, Section 508, and the EU Accessibility Act (in force since 2025-06-28). WCAG 3.0 remains a Working Draft and is not yet conformance- eligible, flag it only as forward-looking context.

Evaluate using the POUR principles:

  • Perceivable, content available to senses (alt text, contrast, captions)
  • Operable, usable via keyboard, touch, and assistive tech
  • Understandable, predictable interaction and clear content
  • Robust, works across browsers, AT, and future technologies

Audit Process

Step 1: Run Automated Tools

# axe-core via RSpec system specs (covers ~30, 40% of WCAG issues)
bundle exec rspec spec/system/ --tag a11y

# Lighthouse CI (optional, if configured)
npx lighthouse <url> --only-categories=accessibility --quiet

# Pa11y CLI (optional, if configured)
npx pa11y --standard WCAG2AA <url>

# Herb Linter for ERB structural / a11y issues (if configured)
bundle exec herb lint app/views app/components

Treat automated results as facts, not the whole picture. Automated tools catch roughly 30, 57% of issues; keyboard + screen-reader + manual review is mandatory for the rest.

Step 2: Manual Review

Inspect these paths for WCAG 2.2 issues:

  • app/views/**/*.html.erb
  • app/components/**/*.{rb,html.erb}
  • app/javascript/controllers/**/*.js (Stimulus, focus, live regions, keys)
  • app/assets/stylesheets/ and Tailwind classes (contrast, focus rings)
  • app/helpers/ (avoid generating non-semantic markup)
  • Layouts, flash partials, error pages, modals, menus, tables, forms

Step 3: Structured Report

Read the whole SKILL.md on GitHub

More in Design