mcpField
A
accessibility-audit

accessibility-audit

github.com/nickcrewTesting & quality6268 installsUpdated 18w ago
Repository

About accessibility-audit

accessibility-audit is a lightweight skill for triaging accessibility issues in pages, components, and pull requests. It combines automated scans with checks for keyboard use, semantics, contrast, and motion, and flags cases needing a full audit.

Key features

  1. 01Automated accessibility scan guidance
  2. 02Keyboard navigation checks
  3. 03Semantic and label checks
  4. 04Visual contrast checks
  5. 05Motion and dynamic update checks
  6. 06Full-audit escalation criteria

Use cases

  1. 01Checking accessibility before a release
  2. 02Reviewing component-level accessibility
  3. 03Finding regressions in pull requests
  4. 04Smoke-checking WCAG 2.2 AA

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nickcrew/claude-cortex --skill accessibility-audit

After installing, type/accessibility-auditin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported