prioritising-accessibility-fixes

Prioritizes accessibility issues by severity, user impact, and effort into a ranked remediation plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prioritises the remediation of accessibility issues to help teams focus on the highest-impact fixes first, reducing risk and effort.

Core Features & Use Cases

  • Prioritisation scoring based on severity, user impact, and effort to generate a clear remediation order.
  • Supports audits, sprint planning, and backlogs by providing a ranked list of issues and batching guidance.
  • Handles input sets where some issues include explicit effort estimates and can infer effort where missing.

Quick Start

Provide a ranked remediation plan for the given accessibility issues.

Frequently Asked Questions about prioritising-accessibility-fixes

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

FAQPage Schema
How do I prioritise accessibility issues in a backlog for remediation?

Prioritise accessibility issues by scoring each item based on severity, user impact, and effort to generate a ranked remediation order. This approach helps teams focus on the highest-impact fixes first, reducing risk and effort during backlog grooming or sprint planning.

What is the best way to triage WCAG criteria violations from an audit?

Triage WCAG criteria violations by evaluating the severity and user impact of each issue alongside remediation effort. This scoring method produces a clear, ranked remediation plan that batches issues efficiently for sprint planning and audit follow-ups.

Can I score accessibility issues for a sprint plan if effort estimates are missing?

Yes, you can score accessibility issues even when effort estimates are missing. The process accepts issues with known effort estimates and can infer effort where missing by assessing the affected code and components to produce a complete ranked remediation plan.

What inputs do I need to provide to rank accessibility fixes by impact and effort?

To rank accessibility fixes, provide a set of issues with descriptions, WCAG criteria, severity, affected pages or components, and optional effort estimates. The system uses these inputs to return a ranked remediation plan tailored to your triage scenario.

Does this approach work for batching accessibility fixes across multiple affected pages?

Yes, this approach supports batching accessibility fixes across multiple affected pages or components. By ranking issues based on severity, user impact, and effort, it provides batching guidance to streamline remediation during audits and backlog grooming.