Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
nickcrew avatar

Accessibility Audit

  • 39 installs
  • 28 repo stars
  • Updated June 29, 2026
  • nickcrew/claude-ctx-plugin

Helps with security tasks.

About

accessibility-audit is a Claude Code skill for security. It helps solo builders move faster with AI-assisted development.

  • accessibility-audit
  • Security
  • AI-coding skill

Accessibility Audit by the numbers

  • 39 all-time installs (skills.sh)
  • Ranked #1,418 of 2,202 Security skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/nickcrew/claude-ctx-plugin --skill accessibility-audit

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs39
repo stars28
Last updatedJune 29, 2026
Repositorynickcrew/claude-ctx-plugin

What it does

Helps with security tasks.

Files

SKILL.mdMarkdownGitHub ↗

Accessibility Audit Skill

Fast, high-signal accessibility triage for pages, components, or PRs. This is a lightweight check, not a full compliance audit.

When to Use This Skill

  • Quick accessibility triage before releases
  • Component-level a11y verification
  • PR review for accessibility regressions
  • Smoke checks for WCAG compliance
  • Validating keyboard navigation on new features

Quick Audit Checklist

1. Automated Snapshot (Recommended)

Run one of these automated tools first:

  • npx @axe-core/cli <url> - Quick axe-core scan
  • npx pa11y <url> --standard WCAG2AA - Pa11y audit
  • Lighthouse Accessibility score (Chrome DevTools > Lighthouse > Accessibility)

2. Keyboard Basics

CheckExpected
All interactive elements reachable via TabYes
Focus indicator always visibleYes
No keyboard trapsYes
Logical tab orderYes
Skip link works for long pagesYes

3. Semantics and Labels

CheckExpected
Single, descriptive H1Yes
Logical heading order (no large jumps)Yes
Form inputs have visible labels or aria-labelYes
Buttons and links have clear namesYes
Images have meaningful alt text (or empty for decorative)Yes

4. Visual Contrast

ElementMinimum Ratio
Normal text4.5:1
Large text (18pt+ or 14pt bold+)3:1
UI components (inputs, buttons, focus rings)3:1

5. Motion and Updates

CheckExpected
Respects prefers-reduced-motionYes
Dynamic updates announced (aria-live)Yes

Output Format

After running the audit, report findings as:

## Accessibility Audit: [Component/Page Name]

### Result: [Pass | Needs Fixes | Escalate to Full Audit]

### Findings

| Severity | Issue | Location | Fix Guidance |
|----------|-------|----------|--------------|
| Critical | [Description] | [Selector/Line] | [How to fix] |
| Major | [Description] | [Selector/Line] | [How to fix] |
| Minor | [Description] | [Selector/Line] | [How to fix] |

### Escalation Recommendation
[If applicable, explain why a full audit is needed]

Escalate to Full Audit When

  • New or changed navigation structure
  • Complex forms or authentication flows
  • Custom widgets or advanced interactions (modals, accordions, tabs)
  • Public releases or compliance requirements
  • Significant page structure changes
  • Failed automated scans with multiple critical issues

Notes

  • This smoke check targets WCAG 2.2 AA by default
  • If a different compliance level is required, state it explicitly
  • Automated tools catch ~30-40% of issues; manual testing is essential
  • Test with actual screen readers (VoiceOver, NVDA) for comprehensive coverage

Related skills

Securityappsec

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.