If there is only one parent, the component renders as a link with the text "Back" and a left-facing arrow. The showTwoBreadcrumbs property takes precedence over this property.
If there is only one parent and the backLinkWithoutText property is true, the component renders as just a left-facing arrow. The showTwoBreadcrumbs property takes precedence over this property.
If there are exactly two breadcrumb items and the showTwoBreadcrumbs is set to true, the component renders both the parent and current page as clickable breadcrumbs. If showTwoBreadcrumbs is false, a back link renders as an arrow, with or without text depending on backLinkWithoutText.
The breadcrumb is a secondary navigational component that helps users identify their current location and enables them to move to a parent level or a previous step. Comprised of text links, each link in a breadcrumb represents a page, one level up, that users can quickly access.
Breadcrumbs are an important navigational element that support wayfinding — making users aware of their current location within the hierarchical structure of an application.
The breadcrumb component consists of the following elements:
Text link: Breadcrumbs appear as a live text link with a blue fill, like hyperlinks. They direct users to the parent-level page.
Text link separator: The separator provides a visual indication of separation between pages. It uses the same font as the text link. Separators aren't interactive.
Current item: The breadcrumb item for the page the user is currently viewing. Appears as plain text.
All items in the breadcrumb trail (except the current page) must represent a place the user can go to. If there's a logical category that doesn't have an associated page, don't include it in the breadcrumb trail.
Breadcrumb trails typically start with the homepage. However, if the global navigation includes a link to the homepage, don't include the Home link in the breadcrumb trail.
Breadcrumbs are intended to show the hierarchical structure of the site, not the history of pages traversed.
Ensure that all items in the breadcrumb trail, except the current page, are active links.
On mobile devices, don't wrap breadcrumbs to multiple lines. Consider shortening the breadcrumb trail to include only the last levels.
The aria role of 'navigation' and the aria-label='breadcrumb' are included to provide more context to screen reader users. Similarly, when the 'lastItemClickable' checkbox is enabled, the final link in the breadcrumb trail adopts the value aria-current="page" to identify the current page.
The contrast ratio of textual elements against their background is above 4.5:1 as per WCAG 2.1 AA requirements. Non-textual content that needs to convey meaning (such as icons and keyboard focus visibility) has a contrast ratio of at least 3:1 with its adjacent colors. All content is visible and functional up to and including 400% without requiring scrolling in two dimensions.
This component has been validated to meet the WCAG 2.1 AA accessibility guidelines. However, changes made by the content author can affect accessibility conformance.
Make sure to understand the Design System components API surface, and the implications and trade-offs. Learn more in our introduction to the component API.
If set to true, the back link renders as just an "arrow" icon. If set to false, it also includes the word "Back". The showTwoBreadcrumbs property takes precedence over this property.
If set to true, breadcrumbs for both the parent and the current page are displayed if there are only two breadcrumbs. If set to false, the back link renders as an arrow with or without text depending on backLinkWithoutText.
The showTwoBreadcrumbs prop was added to allow the display of both breadcrumb links if there are only two breadcrumb links: the current page and the "home" page. Previously, a back arrow (with or without text) was always displayed.
A new opt-in feature was introduced that disables automatic event publishing for the Breadcrumb component. You can enable this feature by adding JUTRO_DISABLE_AUTO_EVENTS_PUBLISHING=true to the .env file in the root of your Jutro application. When this is enabled, legacy components no longer publish events by default. For more information on events and how to set up new events, see the Events documentation.