1---2name: 080103-ux-standards3description: UX standards: WCAG accessibility, touch interaction, form UX, navigation, UX writing, cognitive load. Heuristic evaluation and critique methodology.4license: MIT5---67# UX Standards89Production-grade UX standards for web and mobile: accessibility, interaction, form design, navigation architecture, copy, and cognitive load.1011## References1213| Topic | File |14|---|---|15| WCAG accessibility: contrast 4.5:1, focus, keyboard, screen reader, ARIA, reduced motion | [references/accessibility.md](references/accessibility.md) |16| Touch interaction: targets 44×44pt, gestures, haptics, safe areas, platform standards | [references/touch-interaction.md](references/touch-interaction.md) |17| Form UX: labels, validation, error recovery, progressive disclosure, keyboard, autofill | [references/form-ux.md](references/form-ux.md) |18| Navigation: bottom nav, sidebar, breadcrumbs, back stack, deep linking, adaptive patterns | [references/navigation-patterns.md](references/navigation-patterns.md) |19| UX writing: error messages, empty states, CTAs, confirmation, tone | [references/ux-writing.md](references/ux-writing.md) |20| Cognitive load: information density, chunking, progressive disclosure, decision fatigue | [references/cognitive-load.md](references/cognitive-load.md) |2122## Core Rules2324- **Accessibility is critical**: Color contrast ≥4.5:1, visible focus rings, keyboard nav, aria-labels, skip links, heading hierarchy never skips levels. Color is never the only indicator.25- **Touch targets**: Minimum 44×44pt (Apple) / 48×48dp (Material). 8px minimum gap between targets. Don't rely on hover alone.26- **Forms**: Visible labels (not placeholder-only), errors below the field, progressive disclosure, validate on blur, input types trigger correct keyboard.27- **Navigation**: Bottom nav ≤5 items, labels + icons. Back must preserve scroll/state. All screens reachable via deep link.28- **UX writing**: Every word earns its place. Errors state cause + how to fix. Empty states teach the interface.2930## When to Use3132| Trigger | Use |33|---|---|34| Designing forms or inputs | [references/form-ux.md](references/form-ux.md) |35| Building navigation structure | [references/navigation-patterns.md](references/navigation-patterns.md) |36| Reviewing accessibility | [references/accessibility.md](references/accessibility.md) |37| Writing UI copy | [references/ux-writing.md](references/ux-writing.md) |38| Evaluating information density | [references/cognitive-load.md](references/cognitive-load.md) |39| Mobile/touch design review | [references/touch-interaction.md](references/touch-interaction.md) |