ux-feedback-patterns

Feedback patterns communicate state changes immediately after user actions. Use inline messages near the action or toast notifications for non-blocking feedback—display success, error, or status messages for 2–5 seconds to confirm the action completed without interrupting the user's workflow.

Progress indicators provide visual cues that a task is running. Use progress bars, spinners, or step indicators with ARIA live regions to announce state changes to screen readers, ensuring users understand what's happening and how long it may take.

Accessible notifications require ARIA live regions and proper semantic roles. Configure aria-live="polite" or "assertive" on toast containers, dialogs, and inline feedback so assistive technologies announce changes immediately without requiring focus shifts.

Yes. Patterns support keyboard-navigable confirmation dialogs, dismissible toasts, and CSS variable theming for consistent styling. Keyboard users can dismiss notifications and navigate to related actions without a mouse.

Use inline feedback for contextual, persistent messages tied to specific form fields or UI sections. Use toasts for global, temporary messages about general actions—saves, uploads, or system events—that don't require persistent visibility or field-level context.

Yes. Confirmation dialogs are included as guardrails for destructive operations. They block action until the user confirms, provide clear warning text, and support keyboard and screen reader navigation to prevent accidental data loss.