skills.rest
cedricfressin
cedricfressinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

a11y-audit

Automate accessibility audits for Next.js and Expo projects with Lighthouse and Flashlight.

Updated Aug 27, 2026
Search Tags:#accessibility#a11y#audit#mobile#Lighthouse#web#Flashlight
One-click install
npx skills add https://github.com/cedricfressin/claude-config --skill a11y-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a11y-audit
Source: https://github.com/cedricfressin/claude-config/tree/main/skills/workflow-a11y-audit
Command: npx skills add https://github.com/cedricfressin/claude-config --skill a11y-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, lighthouse, @bamtech/flashlight, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides an end-to-end workflow to automate accessibility auditing for web (Next.js) and mobile (Expo) projects, reducing manual checks and accelerating fixes.

Core Features & Use Cases

  • Platform-detection driven audits: auto-detects platform (web or mobile) and runs appropriate tooling.
  • End-to-end workflow: from platform detection to reporting and interactive fix proposals.
  • Reporting and collaboration: generates structured reports and supports saving outputs for traceability.

Quick Start

Use the a11y-audit skill to start a full project audit:

  • Run: /a11y-audit
  • Audit a specific path: /a11y-audit src/components/LoginForm.tsx
  • Force web audit: /a11y-audit -w
  • Economy mode: /a11y-audit -e

Frequently Asked Questions about a11y-audit

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

FAQPage Schema
How do I automate accessibility audits for Next.js and Expo projects?▼

You can automate accessibility audits for Next.js and Expo projects by running automated checks with Lighthouse and Flashlight, which detects the platform, analyzes results, and generates structured WCAG/RAAM reports.

What is the best way to run web and mobile accessibility checks?▼

The best way to run web and mobile accessibility checks is using an end-to-end auditing workflow that auto-detects the platform, runs Lighthouse for web or Flashlight for mobile, and proposes interactive fixes.

Does automated accessibility auditing support specific frameworks?▼

Automated accessibility auditing specifically supports Next.js for web projects and Expo for mobile projects, applying parallel analysis and mapping results to WCAG and RAAM requirements.

How do I audit a single component file instead of the full project?▼

To audit a single component file, you can target a specific path like 'src/components/LoginForm.tsx' directly in the audit command, restricting the automated checks and generated reports to that file.

Do I need to install Lighthouse and Flashlight before running an audit?▼

Yes, you need the required dependencies installed, including Bun, Lighthouse for web audits, and @bamtech/flashlight for mobile audits, to execute the end-to-end accessibility checks and report generation.

Can I force a web accessibility audit when platform detection fails?▼

Yes, you can force a web accessibility audit by passing the '-w' flag, overriding automatic platform detection to explicitly run Lighthouse checks and generate web-specific reports.

Related Skills

Explore More Software Engineering Skills→
BoltDoggyBoltDoggy

bun-pnpm

Manage Bun project dependencies using pnpm commands.

Community
Advanced
geoffreycroftegeoffreycrofte
31

raam-audit

Audit iOS and Android apps against RAAM 1.1 criteria.

Community
Advanced
nicoarbelaeznicoarbelaez

accessibility

Audit web pages for WCAG 2.2 gaps and generate remediation guidance.

Community
Intermediate
89jobrien89jobrien
4

web-accessibility

Audit web content for WCAG 2.1/2.2 conformance and accessibility issues.

Community
Advanced