Skip to main content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.


The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.



Use: Deployed USWDS v3
Breadcrumbs provide secondary navigation to help users understand where they are in a website. In addition, the breadcrumb tells search engines how the site is structured, and it can be displayed in search results. This can improve rankings, and provide users with additional context.



View va-breadcrumbs in Storybook

Default at mobile viewport width

View va-breadcrumbs in Storybook

Rerender state

View va-breadcrumbs v3 and adjust state in Storybook

Wrapping state

View va-breadcrumbs v3 wrapping state in Storybook


Refer to the U.S. Web Design System for usage guidance

Additional guidance for VA

When to use

  • Complex levels. Use a breadcrumb when content is more than 2 levels deep.

When to consider something else

  • Simple sites. Do not use a breadcrumb if the site or experience has a flat structure (i.e. only 2 levels of content or less)
  • Irrelevant hierarchy. Do not use a breadcrumb if the path or hierarchy of the page is irrelevant to the user or experience.
  • One way exit. Do not use a breadcrumb if it would create a way for a user to exit or navigate away from a user flow that they are unable to return to, or would result in a loss of data.

Usability guidance

  • Breadcrumbs should be based on content hierarchy, not on the user’s click path or browser history. For online applications and forms, the breadcrumb represents the forms’s placement within the site hierarchy, it does not track the steps or progress of the form flow. In other words, the breadcrumb will only show up to the form as the current page segment, and will maintain that display while the user goes through the flow. For navigation through the steps of the form flow, forward and backward CTAs can be provided as part of the main content as appropriate.
  • Include one, include all. If you use a breadcrumb for one page in a hierarchy, always use a breadcrumb for all pages within that hierarchy.
  • Each breadcrumb segment should match the text of the title (h1) of the corresponding page. Breadcrumb segment text must match the title (h1) text of a corresponding page and not be an abbreviation or variation of that title. When writing H1s for a page, follow the content styleguide for writing page titles.
  • Use the title (h1 & title tag) of the Introduction page as the text of the final breadcrumb for a multi-step form. On a multi-step form the final crumb is frozen as the title of the Introduction page and should link back to the Introduction page. The breadcrumb works in concert with the Progress bar - Segmented component to provide context for a user is in a process and on the site.


  • The breadcrumb should be placed below the header and above the main content.
  • The placement of the breadcrumb must be consistent from page to page.


  • All links in the breadcrumb should be interactive and link to their corresponding page, or in the case of the current page link, link to content on the current page.

SEO considerations

  • Search engines utilize breadcrumbs to understand your site structure and gain additional context about your page to help in ranking.
  • Breadcrumbs can also be displayed in search engine results pages (SERPs), which provides additional context to users about your page.
  • Breadcrumbs are not the only element used by search engines, go to writing for SEO in the content styleguide for more SEO assistance.

Code usage

Attributes and Properties

Property Attribute Type Default Description
breadcrumbList breadcrumb-list any Represents a list of breadcrumbs. Use a JSON array of objects with label and href properties, then wrap in a string if using non-React-binding version. See Storybook examples for React-binding version. For pure web components, here's an example link: ``[{"href": "/link1", "label": "Link 1"}]`. This prop is available when `uswds` is set to `true`.
disableAnalytics disable-analytics boolean false Analytics tracking function(s) will not be called
homeVeteransAffairs home-veterans-affairs boolean true When true, the first breadcrumb label will be " home".
label label string 'Breadcrumb' Adds an aria-label attribute to the
uswds uswds boolean true Whether or not the component will use USWDS v3 styling.
wrapping wrapping boolean false Whether or not the component will wrap the breadcrumbs. This prop is available when `uswds` is set to `true`.


Name Description
component-library-analytics The event used to track usage of the component. This is emitted when a breadcrumb anchor is clicked and disableAnalytics is not true.
routeChange Fires when user clicks on breadcrumb anchor tag. Has no effect unless uswds is true and the href of anchor tag is part of breadcrumb object that also has isRouterLink: true

To use React Router with this component follow these instructions.

Content considerations

  • Use “ home” as the default home crumb title. This component will default to “ home” for the first crumb. This is the preferred content for this crumb. Deviation from this should only be done with express permission from CAIA.

Accessibility considerations

Refer to the U.S. Web Design System for accessibility guidance

Additional accessibility guidance for VA

  • Make current page a link. Use a link for the current page for robustness. While it may sound counterintuitive to link to the current page in this component, it makes sense to include this as a link so screen readers voice the current page link whether the user navigates by element or by tabbing. Making the current page a link rather than text makes it a focusable and clickable element. It also follows WAI-ARIA Authoring Practices Guide (APG) guidances which states that an a element with aria-current="page" should represent the current page.
Edit this page in GitHub (Permissions required)
Last updated: May 14, 2024