claude

Build accessible UI components by enforcing WCAG 2.2 AA standards through token-first constraints, keyboard-first interactions, and explicit interaction states like visible focus and disabled. This approach guarantees components meet strict accessibility quality gates.

Token-first constraints are foundational rules defining palette, typography, and spacing to prevent visual drift across UI components. You need them when authoring component rules to ensure consistent design-system implementation across engineering workflows.

Standardize writing tone and interaction states by specifying explicit do/don't patterns for hover, focus, disabled, and error states alongside concise, confident content guidelines. This ensures the UI maintains an authoritative editorial aesthetic.

Yes, this design system guidance generates engineering-ready rules by applying foundational token constraints and testable acceptance criteria to component authoring. It fits engineering workflows needing explicit interaction behavior and quality gates.

Prevent design token drift by applying foundational constraints that govern your typography, spacing, and color palette before authoring components. Enforcing these token-first rules ensures consistent, accessible UI implementation across teams.

UI components fail accessibility quality gates when they lack explicit interaction behavior, visible focus states, or keyboard-first interactions. Enforcing testable acceptance criteria based on WCAG 2.2 AA prevents these implementation failures.