accessibility-review

Audit HTML/CSS/JS projects for WCAG conformance across Blade, Kirby, and PHP templates.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/benjaminhaeberli/claude-plugins --skill accessibility-review-benjaminhaeberli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-review
Source: https://github.com/benjaminhaeberli/claude-plugins/tree/main/skills/general/accessibility-review
Command: npx skills add https://github.com/benjaminhaeberli/claude-plugins --skill accessibility-review-benjaminhaeberli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams identify and fix accessibility gaps in codebases to meet WCAG standards and relevant regional requirements, guiding improvements before release.

Core Features & Use Cases

  • Inspect HTML structure, ARIA usage, color contrast, keyboard navigation, and focus management for WCAG conformance.
  • Scan Blade, Kirby, PHP templates, and components to surface accessibility issues and actionable fixes.
  • Use Case: when auditing a web app or site for accessibility, quality assurance, or pre-release compliance to ensure inclusive design.

Quick Start

Run the accessibility-review on a project repository to generate an initial WCAG-focused audit highlighting issues and recommended fixes.

Frequently Asked Questions about accessibility-review

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

FAQPage Schema
How do I audit my codebase for WCAG conformance?

To audit codebases for WCAG conformance, you can scan HTML templates, ARIA usage, color contrast, and keyboard navigation to produce an actionable accessibility report. It statically checks alt text, landmarks, language attributes, and heading structure.

Can I check accessibility issues in Blade and Kirby PHP templates?

Yes, you can check accessibility issues in Blade, Kirby, and PHP templates. The audit scans these components to surface issues and recommended fixes for inclusive design and pre-release compliance.

What is included in an HTML accessibility audit?

An HTML accessibility audit includes static checks and pattern-based analyses of ARIA usage, color contrast, keyboard navigation, focus management, alt text, landmarks, language attributes, and heading structure to verify WCAG alignment.

When do I need to perform an accessibility review before release?

You need to perform an accessibility review before release when ensuring pre-release compliance and inclusive design. It helps teams identify and fix WCAG gaps in web apps or sites during quality assurance.

Does this accessibility audit verify ARIA usage and keyboard navigation?

Yes, the accessibility audit verifies ARIA usage and keyboard navigation. It examines focus management and applies pattern-based analyses to HTML, CSS, and JS projects to generate a WCAG-focused report.

What's the best way to find inclusive design gaps in frontend code?

The best way to find inclusive design gaps in frontend code is running a static audit that inspects HTML structure, ARIA usage, color contrast, and keyboard navigation to highlight WCAG issues and actionable fixes.