Help us improve
Share bugs, ideas, or general feedback.
Track and manage accessibility debt as a known liability. Useful for backlog triage, remediation planning, and preventing regressions across features.
npx claudepluginhub owl-listener/inclusive-design-skills --plugin accessibility-decisionsHow this skill is triggered — by the user, by Claude, or both
Slash command
/accessibility-decisions:accessibility-debt-trackingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Track accessibility debt the way you'd track technical debt — as a
Discovers and documents undocumented accessibility decisions in an existing feature or product, including tradeoffs, compliance gaps, and debt.
Maintains a living markdown register of design debt in design-state.md, capturing deferred minor issues, notes, and compromises from design critiques and accessibility reviews. Surfaces debt for iteration planning.
Expert approach to accessibility-regression in accessibility testing. Use when working with .
Share bugs, ideas, or general feedback.
Track accessibility debt the way you'd track technical debt — as a known liability with a cost that compounds over time.
Accessibility debt is every known accessibility issue that exists in your product but hasn't been fixed. It includes:
Unlike a feature request that just waits, accessibility debt grows:
For each known accessibility issue, track:
Issue: clear description of the accessibility barrier Severity: critical (blocks task) / major (significant difficulty) / minor (friction) Who's affected: specific user groups Where: page, component, or flow WCAG criteria: which success criteria it violates Discovered: date and how (audit, user report, testing) Deferred because: the reason it wasn't fixed immediately Workaround: any temporary alternative for affected users Estimated fix effort: small / medium / large Remediation deadline: when it must be fixed Owner: who is responsible for the fix