skills.rest
gitkraken
gitkrakenOFFICIAL
Explore all skills by this author →
Website𝕏@gitkrakenGitHub

a11y-remediate

Generates leader-facing accessibility remediation proposals from WCAG audit outputs and team context.

9.9k|1.8k|Updated Aug 8, 2016
Search Tags:#wcag#stakeholder communication#A11y# accessibility#remediation planning#Sprint Planning#Compliance
One-click install
npx skills add https://github.com/gitkraken/vscode-gitlens --skill a11y-remediate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a11y-remediate
Source: https://github.com/gitkraken/vscode-gitlens/tree/main/.claude/skills/a11y-remediate
Command: npx skills add https://github.com/gitkraken/vscode-gitlens --skill a11y-remediate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turning raw accessibility audit findings into a defensible plan for sprint staffing, customer commitments, and compliance deadlines is slow and error-prone, and leaders often get proposals with fabricated numbers or over-scoped compliance claims.

Core Features & Use Cases

  • Audit-to-Proposal Translation: Consumes one or more /a11y-audit outputs and produces a 10-section remediation proposal covering compliance rollup, staffing ask, sprint plan, critical path, customer communication, and deferral risk.
  • Anti-Fabrication Guardrails: Refuses to invent numbers, owner names, or compliance claims beyond audited scope, and ends every proposal with an explicit gaps section listing what cannot be answered.
  • Stakeholder-Ready Language: Generates bounded customer-facing status templates plus internal PM/VP framing, including VPAT awareness, interim workarounds, and good-faith remediation positioning.
  • Use Case: After auditing a shared component library with /a11y-audit, feed the audit files plus team size, sprint cadence, and a Q3 WCAG 2.1 AA contract target to get a proposal an EM can take directly into a VP staffing meeting.

Quick Start

Use the a11y-remediate skill to build a remediation proposal from my audit files, with a 3-engineer team on 2-week sprints targeting WCAG 2.1 AA by Q3.

Frequently Asked Questions about a11y-remediate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a WCAG accessibility audit into a remediation plan?▼

Run /a11y-audit first to produce structured audit outputs, then invoke this skill with those files plus team context. It generates a 10-section proposal covering staffing, sprint planning, critical path, and customer communication.

What inputs does an accessibility remediation proposal need?▼

It needs one or more audit outputs plus user-supplied team size, focus-time fraction, sprint cadence, PR review cycle, and compliance target. Missing inputs produce explicit 'cannot calculate' gaps rather than fabricated estimates.

Can it estimate sprints without team velocity data?▼

No. Without team size, focus-time, and cadence inputs, it emits engineer-day ranges only and refuses calendar or sprint conversions. This prevents indefensible commitments derived from guessed velocity.

Does it claim product-wide WCAG compliance from partial audits?▼

No. Compliance statements are strictly bounded to audited files, and unaudited surface is always flagged. A one-file audit cannot support a product-wide compliance claim.

How does it handle design-blocked accessibility fixes?▼

Design-blocked issues are surfaced as critical-path decisions with typical owner roles, required inputs, and blocked issue lists. It never invents owner names or decision ETAs, and flags commitments as indefensible until decisions have both.

What are the limitations of audit-based remediation planning?▼

It consumes audit output rather than producing it, so runtime-only WCAG criteria like contrast and focus visibility require separate tooling verification. It also cannot assess unaudited surface or legal consequences without user-supplied contract context.

Related Skills

Explore More Product & Management Skills→
langflow-ailangflow-ai
154.0k

ibm-a11y-level1-audit

Audit Langflow frontend surfaces against IBM Equal Access Level 1 criteria and produce a findings report.

Official
Advanced
jdonohoojdonohoo
15

enterprise

Formalize enterprise governance, risk, and compliance decision workflows with stakeholder sign-offs.

Community
Advanced
webdevcodywebdevcody
22

audit-a11y

Audit React/JSX routes for accessibility defects and WCAG AA contrast.

Community
Intermediate
hulusi-tunchulusi-tunc
3

compliance-mapping

Map design decisions to WCAG criteria and generate conformance documentation.

Community
Intermediate