skills.rest
malinskibeniamin
malinskibeniaminCOMMUNITY
Explore all skills by this author →
GitHub

setup-accessibility

Configure PostToolUse hooks with Playwright AXE for WCAG 2.1 AA checks.

3|1|Updated Mar 23, 2026
Search Tags:#testing#accessibility#a11y#playwright#hook#axe-core#aria
One-click install
npx skills add https://github.com/malinskibeniamin/skills --skill setup-accessibility
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-accessibility
Source: https://github.com/malinskibeniamin/skills/tree/main/setup-accessibility
Command: npx skills add https://github.com/malinskibeniamin/skills --skill setup-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This setup provides automated ARIA accessibility enforcement by installing and configuring PostToolUse hooks and Playwright AXE-based checks to ensure WCAG 2.1 AA compliance during development.

Core Features & Use Cases

  • Install and configure accessibility hooks for your codebase
  • Integrate Playwright AXE checks to catch ARIA and naming issues
  • Enforce WCAG 2.1 AA guidelines during commits, PRs, and merges
  • Use with custom test helpers to validate accessibility across pages and components

Quick Start

Install the accessibility hook and AXE setup, then run a pre-commit or post-tool hook to enforce accessibility checks.

Frequently Asked Questions about setup-accessibility

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

FAQPage Schema
How do I automate accessibility checks in Playwright using AXE?▼

Automate Playwright AXE accessibility checks by configuring PostToolUse hooks in .claude/hooks and settings.json, running WCAG 2.1 AA validations during commits and PRs to catch ARIA issues automatically.

What are PostToolUse hooks for WCAG 2.1 AA compliance?▼

PostToolUse hooks are scripts triggered after tool operations that run Playwright AXE to enforce WCAG 2.1 AA compliance by validating ARIA attributes and accessibility naming conventions in frontend codebases.

Do I need Playwright AXE installed to enforce ARIA accessibility hooks?▼

Yes, Playwright AXE is required. You also need hook scripts placed in .claude/hooks and configuration defined in .claude/settings.json to execute accessibility tests and generate compliance results.

Can I run AXE accessibility tests automatically during pull requests?▼

Yes, the setup integrates accessibility enforcement into your commit and PR workflow, triggering Playwright AXE checks via hooks to ensure frontend code meets WCAG 2.1 AA standards before merging.

What limitations exist when enforcing ARIA accessibility with automated hooks?▼

Automated AXE hooks catch ARIA and naming issues but cannot detect all manual accessibility barriers. They require Playwright AXE and proper hook configuration in .claude/settings.json to function within frontend codebases.

Related Skills

Explore More Software Engineering Skills→
ingpocingpoc
9

global-hook-setup

Install and configure global Claude Code hooks across machines.

Community
Intermediate
fugazifugazi
215

a11y-playwright-testing

Automate WCAG 2.1 AA accessibility scans in Playwright tests with axe-core.

Community
Intermediate
michaelsvanbeekmichaelsvanbeek
1

accessibility-testing

Automate accessibility testing and WCAG compliance validation for web projects.

Community
Advanced
guichefferguicheffer
3

web-accessibility

Enforce WCAG 2.1 AA compliance using semantic HTML, ARIA attributes, axe-core, and jest-axe automated tests.

Community
Intermediate