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:
- Read the affected code. Open the file(s) and understand the current markup, component structure, and how the element is used.
- Identify the framework and component library. The correct fix differs significantly between plain HTML, React, Vue, Svelte, Angular, and between apps using a design system vs. raw elements. Look at
package.json, imports, and surrounding code. - Check for existing accessible patterns. Search the codebase for similar components that already handle accessibility correctly. Reuse established patterns rather than inventing new ones.
More from mattobee/skills
designing-agent-teams
Use this skill to design or refine a multi-agent coding team with model-to-role assignments. Triggers when creating an agent team for a codebase, adding agents to an existing team, reviewing an agent team configuration, choosing which AI model to assign to each role, or optimising cost/quality/speed tradeoffs across agents.
10reviewing-accessibility
Use this skill to review implemented UI code for WCAG accessibility compliance. Triggers when reviewing components, pages, or templates for accessibility, auditing a feature after implementation, or answering questions about accessible patterns, ARIA, keyboard navigation, or screen reader support.
7suggesting-next-steps
Use this skill to suggest prioritised next steps for a project. Triggers when the user asks what to work on next, wants to resume after a break, or needs help prioritising a backlog.
7prioritising-accessibility-fixes
Use this skill to prioritise a set of accessibility issues for remediation based on severity, user impact, and effort. Triggers when triaging an accessibility backlog, deciding what to fix first after an audit, planning an accessibility sprint, or asking which accessibility issues matter most.
7estimating-accessibility-effort
Use this skill to estimate the effort required to remediate accessibility issues. Triggers when sizing accessibility work for a sprint, estimating how long a WCAG fix will take, scoping remediation work, or planning accessibility improvements.
7predicting-accessibility-risks
Use this skill to identify accessibility risks in a proposed feature, design, or technical plan before implementation begins. Triggers when planning a new feature, reviewing a design, assessing a technical approach for accessibility impact, or asking what could go wrong for disabled users.
7