estimating-accessibility-effort
Estimating Accessibility Effort
Estimate the effort required to remediate accessibility issues. Given a set of findings — from an audit, automated scan, user report, or backlog — produce effort estimates that help with planning. This is a planning skill; it does not fix the issues.
Inputs
This skill expects one or more accessibility issues to estimate. These may come from:
- An accessibility audit report (from
reviewing-accessibilityor a manual audit) - axe-core scan results
- GitHub issues labelled as accessibility
- A backlog of known accessibility problems
- A VPAT or compliance gap analysis
For each issue, the input should ideally include: what the problem is, where it occurs, and which WCAG criterion it violates. If the input is sparse (e.g., "fix keyboard navigation on the settings page"), gather context by reading the affected code before estimating.
Read the code first
Effort estimates based only on the issue description are unreliable. Before estimating, read the actual implementation:
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.
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.
7writing-accessibility-tests
Use this skill to write Playwright accessibility tests using the two-layer strategy (axe-core scans + targeted assertions). Triggers when adding accessibility test coverage, reviewing test gaps, writing axe scans, or creating Playwright assertions for accessible names, landmarks, ARIA states, focus management, or contrast.
7