fixing-accessibility-issues

Fixes WCAG violations in UI code from axe-core scans and audits with validated workflows.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mattobee/skills --skill fixing-accessibility-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixing-accessibility-issues
Source: https://github.com/mattobee/skills/tree/main/skills/fixing-accessibility-issues
Command: npx skills add https://github.com/mattobee/skills --skill fixing-accessibility-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fix accessibility issues in implemented UI code. This skill takes findings from reviewing-accessibility, axe-core scans, or manual audits and produces code changes. It does not find new issues, estimate effort, prioritise, or write tests — use reviewing-accessibility, estimating-accessibility-effort, prioritising-accessibility-fixes, and writing-accessibility-tests for those.

Core Features & Use Cases

  • Provides structured guidance for remediating WCAG violations in UI code.
  • Analyzes findings from reviews, axe-core scans, and audits to generate concrete fixes.
  • Supports read-before-fix workflows and validated outcomes.

Quick Start

Run the fix-accessibility-issues skill against your UI codebase to remediate WCAG violations.

Frequently Asked Questions about fixing-accessibility-issues

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

FAQPage Schema
How do I fix WCAG violations found in my UI code?

Remediate WCAG violations in UI code by applying structured fix patterns to findings from axe-core scans or manual accessibility audits. The workflow enforces read-before-fix guidance and validation checks to ensure code changes directly address identified accessibility issues.

Can I use this to automatically find new accessibility issues in my codebase?

No, this skill does not find new accessibility issues. It specifically remediates existing WCAG violations already identified by reviewing-accessibility checks, axe-core scans, or manual audits. You must provide known findings for it to generate concrete UI code fixes.

What's the best way to remediate axe-core scan results in UI components?

The best way to remediate axe-core scan results is using a structured workflow with defined fix patterns and validation checks. This skill analyzes scan findings to produce concrete code changes in UI components, ensuring validated outcomes without writing new tests or estimating effort.

Does this skill write accessibility tests or estimate remediation effort?

No, this skill does not write accessibility tests or estimate remediation effort. It strictly focuses on generating UI code fixes for existing WCAG violations. Dedicated skills like writing-accessibility-tests and estimating-accessibility-effort handle those specific tasks.

How do I remediate UI code accessibility issues without breaking existing components?

Remediate UI code accessibility issues safely by following the enforced read-before-fix workflow. This approach analyzes audit findings and applies defined fix patterns to ensure code changes remediate WCAG violations accurately while maintaining component structure through validation checks.