Accessibility

Library-wide semantics, keyboard behavior, motion, and contrast responsibilities.

Liquidify components are built around native HTML semantics and documented ARIA patterns. The application still owns accessible labeling, meaningful copy, page structure, and validation messages.

Application checklist

Give icon-only controls an accessible name.
Preserve visible focus treatment and a logical tab order.
Use a native label association for fields whenever the component API permits it.
Keep disabled and loading states distinguishable without relying on color alone.
Put validation text next to its field and connect it through the component's documented API.
Test dialogs, menus, sheets, and popovers with keyboard-only navigation.
Respect prefers-reduced-motion; do not add surrounding animation that defeats the library fallback.

Keyboard contracts

Native buttons activate with Enter and Space. Composite controls may add arrow-key navigation, Home, End, or Escape according to their pattern. Refer to the component page for the exact table; do not assume one composite pattern applies to another.