accessibility-debt-tracking
Track and manage accessibility debt — known accessibility issues that have been deferred. Use when managing a backlog of accessibility issues, planning remediation, or when accessibility problems are accumulating faster than they're being fixed. Triggers on: accessibility debt, tech debt, known issues, backlog, deferred, we'll fix it later, remediation, accessibility backlog, accumulating issues, regression.
- Installs
- 72
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill accessibility-debt-tracking- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads accessibility-debt-tracking automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Accessibility Debt Tracking
Track accessibility debt the way you'd track technical debt — as a known liability with a cost that compounds over time.
What Is Accessibility Debt
Accessibility debt is every known accessibility issue that exists in your product but hasn't been fixed. It includes:
- Issues found in audits that were deprioritised
- Tradeoffs where accessibility was deferred
- New features shipped without full accessibility
- Regressions introduced by updates or redesigns
- Known gaps in assistive technology support
Why It Compounds
Unlike a feature request that just waits, accessibility debt grows:
- Each new feature built on top of an inaccessible foundation inherits the inaccessibility
- Users with disabilities develop workarounds that break when you eventually fix things differently than they expect
- Legal exposure increases with time and awareness
- The longer an issue persists, the more expensive it becomes to fix (code has grown around it)
- Team knowledge of why the issue exists fades
Debt Record Format
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
Managing the Debt
Triage Rules
- Critical (blocks task): fix in current sprint, no exceptions
- Major (significant difficulty): fix within 30 days
- Minor (friction): fix within 90 days
- Any issue older than its deadline gets escalated
Preventing New Debt
- Accessibility acceptance criteria on every story
- Accessibility check before merge (automated + manual)
- Regression testing for previously fixed issues
- New features cannot ship with critical accessibility debt
Paying Down Debt
- Allocate a percentage of each sprint to debt reduction (10–20% is common)
- Fix debt when you're already touching the component
- Prioritise by: severity × number of users affected
- Celebrate debt reduction — make it visible
Tracking Regressions
- When a previously fixed issue reappears, it's a regression
- Regressions should be treated as critical by default
- Add automated tests for every fix to prevent recurrence
- Track regression rate as a quality metric
Assessment Questions
- Is there a documented list of known accessibility issues?
- Does each issue have a severity, owner, and deadline?
- Is accessibility debt being paid down each sprint?
- Are regressions caught and treated as critical?
- Is the debt trend improving or worsening over time?
FAQ
What does the accessibility-debt-tracking skill do?
Track and manage accessibility debt — known accessibility issues that have been deferred. Use when managing a backlog of accessibility issues, planning remediation, or when accessibility problems are accumulating faster than they're being fixed. Triggers on: accessibility debt, tech debt, known issues, backlog, deferred, we'll fix it later, remediation, accessibility backlog, accumulating issues, regression.
How do I install accessibility-debt-tracking?
Run npx skills add https://github.com/owl-listener/inclusive-design-skills --skill accessibility-debt-tracking in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/accessibility-debt-tracking/ (personal) or .claude/skills/accessibility-debt-tracking/ (project).
Which AI agents can use accessibility-debt-tracking?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is accessibility-debt-tracking safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains accessibility-debt-tracking?
It is published by owl-listener in owl-listener/inclusive-design-skills. It has 72 recorded installs.
More from owl-listener/inclusive-design-skills
keyboard-navigation
owl-listener/inclusive-design-skills
Design keyboard navigation and focus management for users who cannot or prefer not to use a mouse or touch screen. Use when designing any interactive interface — forms, menus, modals, tabs, carousels, drag-and-drop, data tables, or custom components. Triggers on: keyboard, focus, tab order, focus trap, skip link, arrow keys, keyboard shortcut, can't use mouse, motor disability, switch access, focus indicator, focus ring.
plain-language-design
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
cognitive-load-assessment
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
responsive-review
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
user-preference-respect
owl-listener/inclusive-design-skills
Design interfaces that detect and respond to system-level user preferences. Use when implementing dark mode, reduced motion, high contrast, text scaling, or any user preference that affects how the interface renders. Triggers on: user preference, system preference, prefers-reduced-motion, prefers-contrast, prefers-color-scheme, forced-colors, media query, user settings, system settings, accessibility settings, OS settings.
error-prevention-recovery
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.