name: Alert description: A banner component used to communicate a state that affects the entire application or page, not a specific feature or task. category: Feedback slds_classes: root: '' elements: [] modifiers: - class: slds-alert_warning description: Warning alert variant usage: Use for warnings that need user attention - class: slds-alert_error description: Error alert variant usage: Use for error messages that require immediate attention - class: slds-alert_offline description: Offline state alert variant usage: Use specifically for offline connectivity messages states: [] variants: - name: Base description: Standard alert with different severity levels classes: - slds-alert_warning - slds-alert_error usage_context: Page-level or application-level notifications differences: Different colors and icons based on message type lightning_component: name: lightning-alert url: https://developer.salesforce.com/docs/component-library/bundle/lightning-alert mapping_notes: Direct mapping - Lightning component implements SLDS alert blueprint accessibility: keyboard_support: - No specific keyboard interactions required - Focus management handled by parent context screen_reader: - Alert role automatically announced by screen readers - Icon meaning conveyed through appropriate aria-label - Alert text read immediately when displayed aria_attributes: - role='alert' for immediate announcements - aria-label on icons to convey meaning - aria-live='polite' or 'assertive' based on severity usage_guidelines: when_to_use: - For system-wide messages that affect the entire application - To communicate global state changes - For critical information that users must be aware of - When the message applies to the entire page or workflow when_not_to_use: - For feature-specific messages (use toast instead) - For field-level validation (use field-level help) - For temporary notifications (use toast instead) - For success confirmations of user actions (use toast) best_practices: - Use appropriate severity levels (info, warning, error) - Keep alert messages concise and actionable - Place alerts at the top of the content area - Provide clear next steps when appropriate - Don't stack multiple alerts unless absolutely necessary common_mistakes: - Overusing alerts for non-critical information - Using wrong alert type for the message content - Making alert messages too long or complex - Not providing actionable information in critical alerts code_examples: - title: Info Alert code: "