playbooks

home / skills / jeremylongshore / claude-code-plugins-plus-skills / accessibility-audit-runner

accessibility-audit-runner skill

/skills/05-frontend-dev/accessibility-audit-runner

This skill guides you through accessibility audit runner setup and validation, delivering production-ready configurations and best-practice recommendations for

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill accessibility-audit-runner

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.2 KB
---
name: "accessibility-audit-runner"
description: |
  Run accessibility audit runner operations. Auto-activating skill for Frontend Development.
  Triggers on: accessibility audit runner, accessibility audit runner
  Part of the Frontend Development skill category. Use when analyzing or auditing accessibility audit runner. Trigger with phrases like "accessibility audit runner", "accessibility runner", "accessibility".
allowed-tools: "Read, Write, Edit, Bash(cmd:*), Grep"
version: 1.0.0
license: MIT
author: "Jeremy Longshore <[email protected]>"
---

# Accessibility Audit Runner

## Overview

This skill provides automated assistance for accessibility audit runner tasks within the Frontend Development domain.

## When to Use

This skill activates automatically when you:
- Mention "accessibility audit runner" in your request
- Ask about accessibility audit runner patterns or best practices
- Need help with frontend skills covering react, vue, css, accessibility, performance optimization, and modern web development patterns.

## Instructions

1. Provides step-by-step guidance for accessibility audit runner
2. Follows industry best practices and patterns
3. Generates production-ready code and configurations
4. Validates outputs against common standards

## Examples

**Example: Basic Usage**
Request: "Help me with accessibility audit runner"
Result: Provides step-by-step guidance and generates appropriate configurations


## Prerequisites

- Relevant development environment configured
- Access to necessary tools and services
- Basic understanding of frontend development concepts


## Output

- Generated configurations and code
- Best practice recommendations
- Validation results


## Error Handling

| Error | Cause | Solution |
|-------|-------|----------|
| Configuration invalid | Missing required fields | Check documentation for required parameters |
| Tool not found | Dependency not installed | Install required tools per prerequisites |
| Permission denied | Insufficient access | Verify credentials and permissions |


## Resources

- Official documentation for related tools
- Best practices guides
- Community examples and tutorials

## Related Skills

Part of the **Frontend Development** skill category.
Tags: react, vue, css, accessibility, web

Overview

This skill automates accessibility audit runner operations for frontend projects. It guides developers through setting up, running, and interpreting accessibility audits, and generates practical configs and remediation steps. Designed for React, Vue, and standard web stacks, it helps turn audit results into actionable code and testing workflows.

How this skill works

The skill inspects project files and common tooling configurations, recommends or generates audit runner setups (e.g., axe, Lighthouse, Pa11y, or CI-integrated runners), and outlines command sequences to execute audits locally or in pipelines. It parses audit output, highlights severity and affected elements, and suggests concrete fixes and test assertions. It also validates generated configs against common standards and flags missing prerequisites.

When to use it

  • You need to set up an automated accessibility audit for a frontend repo
  • You want to convert audit findings into prioritized remediation tasks
  • You are integrating accessibility checks into CI/CD pipelines
  • You need example configurations for axe, Lighthouse, Pa11y, or GitHub Actions
  • You want step-by-step guidance to validate fixes and prevent regressions

Best practices

  • Start audits in development and enforce them in CI to prevent regressions
  • Prioritize issues by impact (critical/major) and affected user flows
  • Generate test assertions for fixed issues to lock in remediation
  • Use component-level testing (axe-core in unit/e2e tests) in addition to page-level audits
  • Keep configs version-controlled and document required environment variables

Example use cases

  • Generate a GitHub Actions workflow that runs Lighthouse and fails on accessibility regressions
  • Create axe-core integration snippets for React or Vue unit tests
  • Convert a Lighthouse report into a prioritized remediation checklist with file/line hints
  • Recommend a CI-friendly Pa11y or Playwright audit runner configured with thresholds
  • Validate an existing audit setup and produce a checklist of missing prerequisites and fixes

FAQ

What tools does this skill support?

It focuses on common runners like axe-core, Lighthouse, Pa11y, and CI integrations (GitHub Actions, GitLab CI) and can suggest Playwright or Cypress-based accessibility checks.

Can it auto-fix issues?

It does not make automatic DOM changes but generates code-level suggestions, patterns, and test assertions you can apply; some fixes may be automated via codemods if requested.

What prerequisites are required?

A configured dev environment with node/npm or yarn, access to the repository, and any CI credentials for pipeline setup. Local browser or headless environment is needed for some runners.