accessibility-audit

Run Lighthouse audits and custom heuristics to report WCAG accessibility issues.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/dominika-zajac/better-frontend-skills --skill accessibility-audit-dominika-zajac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/dominika-zajac/better-frontend-skills/tree/main/skills/accessibility-audit
Command: npx skills add https://github.com/dominika-zajac/better-frontend-skills --skill accessibility-audit-dominika-zajac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a repeatable, comprehensive accessibility audit workflow to catch WCAG violations that Lighthouse alone may miss, helping teams ship more inclusive web experiences.

Core Features & Use Cases

  • Lighthouse desktop and mobile audits for automated detection of accessibility issues (via MCP/axe under the hood).
  • Custom evaluate_script heuristics, keyboard focus verification, modal visibility checks, a11y snapshot vs DOM parity, 320px reflow testing, and touch target assessments.
  • Output includes a structured markdown report template and severity guidance to enable easy handoff and ticketing.

Quick Start

Open the current page in your editor or tool and run the accessibility-audit skill to generate a structured WCAG-focused report.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I run a WCAG audit for web app accessibility?

Run a WCAG audit by executing Lighthouse-based desktop and mobile checks alongside custom heuristics. The workflow evaluates DOM-to-a11y parity, keyboard focus, and touch targets, outputting a structured markdown findings report for team handoff.

What does a Lighthouse accessibility check miss for WCAG compliance?

Lighthouse checks often miss complex interactive states like modal visibility, keyboard focus traps, and 320px reflow issues. This audit applies custom evaluate_script heuristics to capture these DOM-to-a11y parity gaps that automated scanners alone overlook.

Do I need chrome-devtools-mcp to run automated accessibility audits?

Yes, chrome-devtools-mcp is required to perform the automated Lighthouse-based desktop and mobile audits. It enables the underlying MCP and axe evaluations necessary to capture accessibility issues and generate the structured markdown report.

Can I test mobile accessibility and 320px reflow using automated audits?

Yes, you can test mobile accessibility and 320px reflow by running the mobile-targeted Lighthouse audits and custom heuristics. The workflow includes specific touch target assessments and viewport reflow checks to ensure mobile WCAG compliance.

How do I generate structured accessibility reports for developer handoff?

Generate structured accessibility reports by running the audit workflow to produce a markdown findings template. This output includes severity guidance and specific WCAG violations, enabling direct ticketing and seamless developer handoff.