document

Document feature accessibility decisions, tradeoffs, and WCAG compliance mappings.

3|Updated Mar 28, 2026

Search Tags:#accessibility #wcag #document #decision-record #compliance-mapping #design-process #feature-design

Ready to run

npx skills add https://github.com/hulusi-tunc/unicorn-skills --skill document-hulusi-tunc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document
Source: https://github.com/hulusi-tunc/unicorn-skills/tree/main/.claude/skills-archive/accessibility-decisions--document
Command: npx skills add https://github.com/hulusi-tunc/unicorn-skills --skill document-hulusi-tunc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document accessibility decisions and tradeoffs for a feature, ensuring decisions are traceable and reusable across teams and lifecycle stages.

Core Features & Use Cases

Generates a feature accessibility decision record including feature summary, decision log, tradeoff register, compliance mapping, and open items.
Maps decisions to WCAG criteria with rationale and evidence, enabling audits and handoffs.
Use Case: when designing or shipping a feature, capture decisions to inform implementation and future iterations.

Quick Start

Generate an accessibility decision record for a new feature.

Frequently Asked Questions about document

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

FAQPage Schema

How do I document accessibility decisions for a feature design?▼

You document accessibility decisions by generating a feature accessibility decision record that captures the summary, decision log, and tradeoffs during the design and development process. This ensures your choices are traceable for future iterations.

What is an accessibility decision record and when do I need one?▼

An accessibility decision record is a structured document logging design tradeoffs and compliance mappings for a feature. You need it when designing or shipping a feature to inform implementation and enable future audits.

How do I map feature design decisions to WCAG compliance criteria?▼

You map feature design decisions to WCAG criteria by generating a compliance map within the accessibility decision record, providing rationale and evidence for each choice to enable audits and team handoffs.

Can I use this to track accessibility tradeoffs and open items during development?▼

Yes, you can track accessibility tradeoffs and open items during development. The generated record includes a tradeoff register and an open items list to track unresolved issues across the lifecycle stages.

What is the best way to capture design rationale for accessibility audits?▼

The best way to capture design rationale for accessibility audits is to generate a decision record that maps choices to WCAG criteria with evidence. This produces a compliance map that ensures decisions are traceable and reusable across teams.

Does this approach work for recording accessibility decisions across multiple teams?▼

Yes, recording accessibility decisions this way works across multiple teams. It produces a structured decision record with summaries and compliance mappings that ensure decisions remain traceable and reusable during handoffs.