Feedback components communicate state changes and results to users. They are assertive enough to get attention but unobtrusive enough not to block interaction unnecessarily. A toast auto-dismisses after a timeout. An alert or banner remains until the user dismisses it. A modal or drawer blocks until addressed. The duration and mode of dismissal should be clear from the design and the microcopy.

Feedback atoms are the fundamental UI primitives: button, icon, close icon, progress bar, spinner. Each atom ships with every state and styles from design tokens. See <a href="/design-system/atomic-design#atoms">Atomic design → Atoms</a> for the canonical atom definition.

Feedback molecules combine atoms into purposeful patterns. A button and icon become a toast trigger. An icon and text become an alert. A progress bar and text become a status update. See <a href="/design-system/atomic-design#molecules">Atomic design → Molecules</a> for the canonical molecule definition.

Feedback organisms are distinct interface regions: a toast container, an alert banner, a modal drawer. They can hold state and accept data through props but their visual building blocks all come from lower levels. See <a href="/design-system/atomic-design#organisms">Atomic design → Organisms</a> for the canonical organism definition.

Feedback components must be operable via keyboard and screen reader friendly. Toasts should announce their message to screen readers. Alerts and banners should have dismiss buttons with clear labels. Modals and drawers should trap focus and provide escape key handling.

Start with the most common pattern toast for transient messages. Add alerts for important but non-blocking information. Use modals or drawers only for critical interactions that require user attention. Always test with keyboard and screen reader.