Prioritising Accessibility Fixes

Given a set of accessibility issues, produce a prioritised remediation order based on severity, user impact, and effort. The output is a ranked list that helps decide what to fix first, what to batch together, and what can wait.

This skill works on a set of known issues. It does not find new issues (use reviewing-accessibility for that), estimate effort from scratch (use estimating-accessibility-effort for that, or provide estimates as input), or implement fixes (use fixing-accessibility-issues for that). If issues arrive without effort estimates, assess effort by reading the affected code before prioritising.

Inputs

A set of accessibility issues, ideally with:

• Description of the problem
• WCAG success criterion
• Severity (Blocker / Critical / Serious / Moderate / Minor)
• Affected pages or components
• Effort estimate (XS / S / M / L / XL)
• Reach (Systemic / Multi-page / Single page) — optional, most useful for projects with shared components

If effort estimates are missing, read the affected code and estimate before prioritising. Do not prioritise without understanding effort — a "Critical" issue that takes 5 minutes should be fixed immediately, while a "Critical" issue requiring an architectural redesign needs different planning.