fixing-accessibility-issues

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.

Accept findings

Each finding should include at minimum:

• What the issue is
• The WCAG success criterion (if known)
• The affected file and location (if known)

Findings may come from reviewing-accessibility output, axe-core violation reports, browser DevTools accessibility audits, or manual testing notes. If a finding lacks a file location, search the codebase to locate the affected code before proceeding.

Read before fixing

Before changing anything, gather context: