Accessibility Debt Tracking — Component Remediation Backlogs

When to use it

Supply existing audit findings or user reports and component ownership. Useful for maintaining design systems and prioritizing regressions after redesigns; does not discover or confirm violations by itself. Distinct from a general design-debt audit: focuses on accessibility barriers and remediation accountability. Upstream 30/90-day timelines, sprint allocations and blanket regression severity are suggested team policies, not legal deadlines or universal priorities. Verify criterion mappings and agree local triage rules. Upstream documentation reviewed only; not installed or runtime-tested. GitHub stars are repository-wide, not skill-specific.

Compatible agents

Claude CodeCodexGemini CLICursor

Installation

Claude Code: `/plugin marketplace add Owl-Listener/inclusive-design-skills`, then `/plugin` → Discover → install accessibility-decisions. Other documented hosts: copy accessibility-decisions/skills/accessibility-debt-tracking into the host-recognized skills directory, preserving SKILL.md. Start a new session and ask for accessibility-debt-tracking on the target interface. See the upstream README.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Nov 2, 2026.

Pair this skill with a visual reference

A skill guides how your agent works; a design reference shows the direction you want. Choose an example for a specific job, such as the headline hierarchy or form layout, and keep your project's existing design rules explicit.

Start with design references you can inspect, then use our guide to briefing an AI coding agent to turn observations into requirements. If you need implementation components, compare UI libraries for your stack.

These pages are public. Browsing a skill does not install it, and TastefulKit's design-reference MCP tools do not search the AI-skill directory.