canopy-primary-message

To display accessible page-level messages in Angular, use the Canopy LgPrimaryMessageComponent as the sole content within its container, utilizing optional title and description subcomponents in a linear layout for optimal screen reader support.

Use a primary message component for Angular UI states such as full-page confirmations, empty states, error pages, and success screens to ensure consistent messaging UI and accessibility across enterprise applications.

For Canopy primary message accessibility, do keep the component as the sole content in its container and use a linear layout with optional title and description subcomponents. Do not include other content within the same container.

Yes, you can add a call-to-action to an Angular success screen using Canopy by following the recommended structure to display a title, description, and optional action within the primary message component.

Yes, the Canopy primary message component works for empty states and error pages, providing clear guidance and maintaining a clean, brand-consistent UI through its linear, accessible layout structure.

The primary limitation is that the Canopy primary message must be the sole content in its container, meaning you cannot place other elements or components alongside it within the same wrapper element.