a11y-remediator

Generate accessibility fixes for existing code using MCP server guidance.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/joe-watkins/a11y-devkit --skill a11y-remediator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-remediator
Source: https://github.com/joe-watkins/a11y-devkit/tree/main/packages/a11y-remediator
Command: npx skills add https://github.com/joe-watkins/a11y-devkit --skill a11y-remediator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The a11y-remediator skill generates fixes for accessibility issues found in existing code by querying MCP servers for authoritative guidance on component patterns, ARIA usage, and WCAG criteria. It focuses on upgrading accessibility without adding new structure or content.

Core Features & Use Cases

  • Automated remediation of existing elements by adding or adjusting attributes (aria-*, alt, roles) while preserving behavior and styling.
  • MCP-guided implementation notes and patterns (magentaa11y-mcp, aria-mcp, wcag-mcp) to ensure standards-compliant fixes.
  • Handling of complex scenarios: when changes would require structural updates, the fix is escalated to manual review with actionable guidance.

Quick Start

Provide the list of identified accessibility issues as input to the skill; the tool will emit patch diffs that modify only existing elements.

Frequently Asked Questions about a11y-remediator

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

FAQPage Schema
How do I automatically fix WCAG and ARIA accessibility issues in existing code?

To fix WCAG and ARIA issues in existing code, the skill generates patch diffs that add or adjust attributes like aria-* and alt text while preserving original behavior and styling.

What is the best way to remediate accessibility issues without changing page structure?

Remediating accessibility without structural changes involves modifying only existing elements by adjusting attributes and roles, escalating any fixes requiring structural updates to manual review.

How does automated accessibility remediation handle complex code changes?

Automated accessibility remediation escalates complex code changes to manual review when modifications would alter DOM structure or user behavior, providing actionable guidance instead of risky patches.

Can I use MCP servers to guide ARIA and WCAG code fixes?

Yes, you can use MCP servers like wcag-mcp and aria-mcp to query authoritative component patterns and WCAG criteria, ensuring generated accessibility fixes remain standards-compliant.

What input do I need to provide for automated accessibility remediation?

You need to provide a list of identified accessibility issues as input, and the tool will emit targeted patch diffs that modify only existing HTML elements to resolve them.

When should I not use automated accessibility code fixes?

You should avoid automated accessibility code fixes when resolving an issue requires adding new HTML structure or content, as the tool will escalate these scenarios to manual review.