skills.rest
jdforsythe
jdforsytheCOMMUNITY
Explore all skills by this author →
GitHub

wolfe-a11y

Detect and verify accessibility defects in frontend code against WCAG standards.

Updated Jun 15, 2026
Search Tags:#accessibility#a11y#WCAG#frontend#audit
One-click install
npx skills add https://github.com/jdforsythe/wolfe-pack --skill wolfe-a11y
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wolfe-a11y
Source: https://github.com/jdforsythe/wolfe-pack/tree/main/templates/bots/wolfe-a11y
Command: npx skills add https://github.com/jdforsythe/wolfe-pack --skill wolfe-a11y

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the detection and verification of accessibility defects in frontend code, ensuring compliance with WCAG standards and improving the user experience for people with disabilities.

Core Features & Use Cases

  • Automated Accessibility Auditing: Identifies missing alt text, broken semantics, keyboard inaccessibility, and other WCAG-compliant issues.
  • Verification: Ensures that fixes are effective by re-running automated checks.
  • Use Case: Integrate this Skill into your CI/CD pipeline to automatically check for accessibility issues before deploying code changes.

Quick Start

Run /wolfe-a11y [area] to audit the specified area for accessibility issues.

Frequently Asked Questions about wolfe-a11y

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate accessibility audits for frontend code?▼

You can automate accessibility audits by running the `/wolfe-a11y [area]` command to detect missing alt text, broken semantics, and keyboard inaccessibility issues in your frontend code.

What WCAG compliance issues can automated frontend audits detect?▼

Automated frontend audits detect WCAG compliance issues including missing alt text, broken HTML semantics, and keyboard inaccessibility. They utilize accessibility engines and lint rules to identify these defects in frontend code.

Can I integrate accessibility checks into a CI/CD pipeline?▼

Yes, you can integrate accessibility checks into a CI/CD pipeline to automatically verify frontend code for WCAG compliance before deploying changes, ensuring fixes are effective by re-running automated checks.

What do I need to configure before running an accessibility audit?▼

To configure and run an accessibility audit, you need a WOLFE.md file present at the root of your repository. This file provides the necessary configuration and bindings for the audit process.

How does automated verification work after fixing accessibility defects?▼

Automated verification ensures accessibility defect fixes are effective by re-running automated checks and lint rules against the updated frontend code, confirming compliance with WCAG standards.

Does this accessibility audit work with component tests?▼

Yes, the accessibility audit utilizes component tests alongside accessibility engines and lint rules to verify frontend code compliance with WCAG standards and detect structural defects.

Related Skills

Explore More Software Engineering Skills→
ki2pixelki2pixel

check-config

Diagnose and validate Config Store state across Redis and file storage.

Community
Intermediate
Patasse97Patasse97

a11y-audit

Identify WCAG 2.2 violations in frontend projects and generate remediation guidance.

Community
Advanced
flitzrrrflitzrrr
4

accessibility

Audit web interfaces for HTML semantics, ARIA, keyboard navigation, and color contrast.

Community
Advanced
nvimcraftnvimcraft

wcag-audit

Audit web interfaces for WCAG compliance and remediation requirements.

Community
Advanced