Remediation plan for gaps

Severity: Recommended (Critical if compliance deadline exists)

A backlog without prioritization is a graveyard. Known gaps need a plan with ownership and timelines.

Check automatically:

# Look for remediation/roadmap docs
find . -maxdepth 4 -type f \( -name "*remediation*" -o -name "*roadmap*" -o -name "*a11y*plan*" \) -name "*.md" 2>/dev/null

grep -riE "accessibility.*roadmap|a11y.*plan|remediation|compliance.*timeline" docs/ --include="*.md" 2>/dev/null

# Check if accessibility issues have milestones/priorities
gh issue list --label "accessibility" --state open --json title,milestone,labels --limit 10 2>/dev/null

# Look for prioritization in issue labels
gh issue list --label "accessibility" --state open --json title,labels --limit 20 2>/dev/null | jq '.[].labels[].name' 2>/dev/null | sort | uniq -c

Ask user:

• "Is there a plan for addressing known a11y gaps?"
• "How are issues prioritized?" (severity, user impact, legal risk)
• "Is there a timeline?" (quarterly goals, release targets)
• "Who owns accessibility remediation?"

Pass criteria:

• Known gaps have a prioritized plan (not just a pile of issues)
• Critical issues have timelines
• Someone owns driving remediation
• Progress is tracked over time

Fail criteria:

• Backlog exists but no prioritization
• "We'll get to it" with no timeline
• No ownership (everyone's problem = no one's problem)
• Same issues open for years

Cross-reference with:

• A11Y-010 (plan is built from tracked issues)
• A11Y-001 (plan works toward stated target)
• Section 40 (Technical Debt Tracking) — DEBT-003/004 patterns apply here

Evidence to capture:

• Plan exists (doc, roadmap, milestones)
• Prioritization method
• Owner/DRI
• Timeline or target dates

---