accessibility

1# Accessibility (a11y)
2 
3Comprehensive accessibility guidelines based on WCAG 2.2 and Lighthouse accessibility audits. Goal: make content usable by everyone, including people with disabilities.
4 
5## Evidence-led audit workflow
6 
7When a rendered page is available:
8 
91. Run a live Lighthouse Accessibility audit when that capability is available; with Chrome DevTools MCP, use `lighthouse_audit`. Use mobile navigation mode for a general public page or snapshot mode when reloading would lose authenticated or user-created state.
102. Use failed audit nodes to localize the relevant component or template instead of searching the whole repository for generic patterns.
113. Inspect a rendered accessibility-tree snapshot for names, roles, states, landmarks, and heading structure; with Chrome DevTools MCP, use `take_snapshot`. Exercise the affected flow with the keyboard.
124. Fix the source, then re-run the same audit and manual interaction.
13 
14If the live tools are unavailable, use Lighthouse CLI or axe for automated coverage and complete the same manual checks. Automated tools detect only a subset of accessibility barriers: a score of 100 is not WCAG conformance, and a low score does not replace issue-level evidence.
15 
16## WCAG Principles: POUR
17 
18| Principle | Description |
19|-----------|-------------|
20| **P**erceivable | Content can be perceived through different senses |
21| **O**perable | Interface can be operated by all users |
22| **U**nderstandable | Content and interface are understandable |
23…