mg-accessibility-review

Identify and document WCAG 2.1 AA/AAA accessibility violations in web interfaces.

1|1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/wonton-web-works/miniature-guacamole --skill mg-accessibility-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mg-accessibility-review
Source: https://github.com/wonton-web-works/miniature-guacamole/tree/main/src/framework/skills/mg-accessibility-review
Command: npx skills add https://github.com/wonton-web-works/miniature-guacamole --skill mg-accessibility-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

WCAG compliance gaps undermine usable interfaces. This skill identifies and documents WCAG 2.1 AA/AAA issues in web interfaces, enabling teams to meet accessibility standards and reduce risk.

Core Features & Use Cases

  • Semantic HTML analysis and ARIA labeling/relation checks to ensure correct structure and assistive technology interpretation.
  • Keyboard navigation and focus management verification across components, including focus indicators and skip links.
  • Color contrast and screen reader validation assessments to ensure perceivable content for users with disabilities.
  • Use Case: auditors and developers can generate remediation plans, track violations, and coordinate QA/design for fixes across workstreams.

Quick Start

Conduct an accessibility review for the current user interface and spawn QA/design as needed.

Frequently Asked Questions about mg-accessibility-review

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

FAQPage Schema
How do I run a WCAG 2.1 AA accessibility audit on a web interface?

Run a WCAG 2.1 AA accessibility audit by analyzing semantic HTML, ARIA labeling, keyboard navigation, color contrast, and screen reader compatibility. The review identifies compliance violations across components and generates structured findings with specific remediation guidance.

What does an ARIA labeling and keyboard navigation check cover for screen reader compatibility?

An ARIA labeling and keyboard navigation check verifies focus management, focus indicators, and skip links to ensure screen reader compatibility. It validates semantic HTML structure and ARIA relations so assistive technologies correctly interpret interface components.

Can I test color contrast and focus management for WCAG AAA compliance?

Yes, you can test color contrast and focus management for WCAG AAA compliance. The review assesses perceivable content by validating contrast ratios and focus indicators across components, documenting any violations against the specified AA or AAA thresholds.

Does the accessibility review generate remediation plans for QA and design teams?

Yes, the accessibility review generates remediation plans for QA and design teams. It documents violations in a structured output format and coordinates with QA and design by following defined memory protocols and escalation patterns to track fixes across workstreams.

What are the limitations of automated WCAG audits for web interfaces?

Automated WCAG audits do not make production changes; they only identify and document compliance issues. Limitations include relying on defined escalation patterns to coordinate fixes, meaning teams must manually implement the structured remediation guidance provided.

When do I need to check semantic HTML structure for assistive technology interpretation?

You need to check semantic HTML structure for assistive technology interpretation whenever web interfaces must meet WCAG 2.1 standards. This ensures correct document structure and ARIA relations, allowing screen readers to properly navigate and perceive content.