Accessibility standards documented

Severity: Recommended

Developers need guidance on building accessibly. Without documentation, accessibility depends on individual knowledge.

Check automatically:

# Look for accessibility docs
find . -maxdepth 4 -type f \( -name "*accessibility*" -o -name "*a11y*" \) -name "*.md" 2>/dev/null | grep -v node_modules

# Check for contributing guidelines mentioning a11y
grep -riE "accessibility|a11y|wcag" CONTRIBUTING.md docs/contributing* 2>/dev/null

# Look for component documentation with a11y guidance
grep -riE "accessibility|keyboard|screen reader" docs/ --include="*.md" 2>/dev/null | head -10

# Check for Storybook with a11y docs
find . -maxdepth 5 -type f -name "*.stories.*" 2>/dev/null | head -3 | xargs grep -l "a11y\|accessibility" 2>/dev/null

Ask user:

• "Is there a documented accessibility standard for the project?"
• "Where do developers learn how to build accessibly?" (docs, training, code review)
• "Are there component-level a11y guidelines?" (how to use buttons, modals, forms)

Pass criteria:

• Accessibility guidelines exist (even lightweight)
• Developers know where to find guidance
• Standards align with stated target (A11Y-001)
• Updated as patterns evolve

Fail criteria:

• No documentation ("just make it accessible")
• Exists but outdated or ignored
• Only lives in one person's head

Cross-reference with:

• A11Y-001 (docs should reference the target standard)
• Section 14 (Documentation) — general docs practices

Evidence to capture:

• Documentation location
• Coverage (component-level, pattern library, etc.)
• Last updated date
• Discoverability

---