estimating-accessibility-effortlisted

# 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-accessibility` or 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: 1. **Find the affected files** — locate the components, pages, or templates where the issue exists. 2. **Assess the current state** — is there partial accessibility support that needs fixing, or is it entirely absent? 3. **Identify dependencies** — does the fix require changes to shared components, layouts, state management, or backend data? Fixes that cross module boundaries take longer. 4. **Check for repetition** — does the same issue appear in multiple places? A