audit-accessibility

Analyze labeled user complaint clusters to generate WCAG-aligned accessibility findings.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/speplinski/hackathon-opus-47 --skill audit-accessibility-speplinski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-accessibility
Source: https://github.com/speplinski/hackathon-opus-47/tree/main/skills/audit-accessibility
Command: npx skills add https://github.com/speplinski/hackathon-opus-47 --skill audit-accessibility-speplinski

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Accessibility reviews are often inconsistent and time-consuming; teams lack a structured, auditable way to translate user feedback into compliant design decisions.

## Core Features & Use Cases

  • WCAG-aligned audits across five dimensions (Perceivable, Operable, Understandable, Robust, Inclusive & Cognitive) with evidence mapping to quotes and UI markup.
  • Generates actionable findings with severity and WCAG references to support design and development repairs.
  • Useful for product teams, designers, and accessibility leads who need traceable justification for design decisions on web apps and mobile interfaces.

### Quick Start Provide a labelled cluster (label, quotes, and optional ui_context/html/screenshot) to generate WCAG-aligned accessibility findings.

Frequently Asked Questions about audit-accessibility

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

FAQPage Schema
How do I audit user feedback for WCAG compliance issues?▼

WCAG accessibility audits map user complaint quotes to specific WCAG A/AA criteria, producing structured findings with dimension scores and evidence mapping to support compliant design repairs.

Can I use HTML markup as evidence in an accessibility audit?▼

HTML markup can be included as optional UI context within the cluster payload, allowing the audit to map evidence and surface WCAG A/AA insights directly to the provided code.

What is the best way to translate screen-reader complaints into actionable design decisions?▼

The best way to translate screen-reader complaints into design decisions is to cluster feedback with labels and quotes, generating a structured JSON payload that maps evidence to WCAG references.

Does this accessibility audit cover inclusive design and cognitive dimensions?▼

Yes, the accessibility audit covers inclusive design and cognitive dimensions alongside Perceivable, Operable, Understandable, and Robust dimensions, scoring each area with mapped evidence.

What format do I need to structure user feedback in for an accessibility audit?▼

User feedback must be structured as a labelled cluster payload containing a label, user quotes, and optional UI context, HTML, or screenshots to generate WCAG-aligned accessibility findings.