accessibility-audit

Audit web interfaces for WCAG compliance issues and remediation recommendations.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/MinhDuyDEV/mdpi --skill accessibility-audit-minhduydev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/MinhDuyDEV/mdpi/tree/main/.pi/skills/accessibility-audit
Command: npx skills add https://github.com/MinhDuyDEV/mdpi --skill accessibility-audit-minhduydev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams identify accessibility issues in web interfaces and components by providing a structured WCAG-focused review process instead of relying only on automated checks.

Core Features & Use Cases

  • WCAG Compliance Auditing: Review UI components and pages for keyboard access, screen reader support, contrast, semantics, and interaction issues.
  • Issue Identification: Map accessibility problems to relevant WCAG criteria and provide remediation guidance for common frontend patterns.
  • Use Case: Use this Skill during a pre-release review of a web application to find accessibility barriers and create an actionable audit report for developers.

Quick Start

Use the accessibility audit skill to review this web page or component for WCAG 2.1 AA compliance issues and provide a remediation report.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I check my web application for WCAG compliance issues?

To check web applications for WCAG compliance issues, review UI components for keyboard access, screen reader support, contrast, and semantics, then map identified defects to WCAG criteria for actionable remediation.

What is the best way to audit frontend components for screen reader compatibility?

Auditing frontend components for screen reader compatibility involves evaluating UI semantics and interaction patterns against WCAG criteria to identify accessibility barriers and generate structured remediation guidance.

How do I perform a pre-launch accessibility verification for a web interface?

Perform pre-launch accessibility verification by running a structured WCAG-focused audit on web interfaces to identify keyboard navigation gaps and screen reader barriers before releasing the application.

Can I map keyboard navigation defects to specific WCAG criteria?

Yes, you can map keyboard navigation defects to specific WCAG criteria by executing structured frontend reviews that identify interaction issues and provide actionable remediation recommendations.

Does this accessibility audit replace automated UI testing tools?

This accessibility audit complements automated tools by providing a structured WCAG-focused manual review process, mapping UI defects to specific criteria and generating remediation guidance automated checks often miss.