How accessible is your website?Start free check
WCAG 2.4.8Level AAAOperable

Breadcrumbs: Accessible Breadcrumb Navigation

Also called: Breadcrumb navigation, Breadcrumb trail

Definition

Breadcrumbs are a trail of links, usually above the page heading, that shows where the current page sits in a website's hierarchy, such as Home › Shop › Shoes. A breadcrumb trail is one of the W3C's sufficient techniques for WCAG 2.4.8 Location at Level AAA.

Breadcrumbs are the short trail of links at the top of a page – Home › Shop › Shoes – that tells visitors where they are and lets them step back up one level. A visitor who lands on a deep product page straight from a search engine sees at a glance which section it belongs to. Built with the right markup, a breadcrumb navigation is just as clear for people using a screen reader.

What it means

Breadcrumbs belong to WCAG 2.4.8 Location, a Level AAA criterion: "Information about the user's location within a set of web pages is available." W3C explains that this helps people orient themselves, in particular people with short attention spans who get confused after a long series of navigation steps, and visitors who arrive directly on a deep page.

A breadcrumb trail is one of several ways to meet it. The sufficient techniques W3C lists:

Technique What it does
G65 Providing a breadcrumb trail
G63 Providing a site map
G128 Indicating current location within navigation bars
ARIA26 Using aria-current to identify the current item in a set
G127 Identifying a page's relationship to a larger collection of pages

Because 2.4.8 is Level AAA, most laws that point to WCAG 2.2 Level AA do not require breadcrumbs. They are still worth it on any site with more than two levels: they add a second way to move around next to the menu and search, which supports multiple ways (2.4.5, Level AA).

Examples

Example
<nav aria-label="Breadcrumb">
  <ol>
    <li><a href="/">Home</a></li>
    <li><a href="/shop">Shop</a></li>
    <li><a href="/shop/shoes" aria-current="page">Shoes</a></li>
  </ol>
</nav>

The <nav> element makes the trail a navigation landmark, and aria-label="Breadcrumb" tells it apart from the main menu – screen reader users can jump straight to it via the list of ARIA landmarks. The ordered list tells them how many levels there are. aria-current="page" marks the last item as the page they are on (technique ARIA26). The separators › or / are best added with CSS, so screen readers don't read "greater than" between every link.

Do

Wrap the trail in a labeled nav, use a list in hierarchy order, mark the current page with aria-current="page", use the real page names as link text, and add separators with CSS.

Don't

Build the trail from plain text with no links, put separator characters in the HTML, use a second unlabeled nav next to the main menu, or show a history of visited pages instead of the site hierarchy.

How to check breadcrumbs

    Questions

    Are breadcrumbs required by WCAG?

    No. Breadcrumbs are one sufficient technique for WCAG 2.4.8 Location, which is Level AAA. A site map or highlighting the current item in the menu are other ways to meet it. Laws such as the European Accessibility Act usually refer to Level AA.

    Should the current page be a link in the breadcrumb?

    Both are common. If you keep it as a link, mark it with aria-current="page" – that is W3C technique ARIA26. If you show it as plain text, keep it inside the list so screen readers still count it as the last level.

    What aria-label should a breadcrumb nav have?

    A short, distinct name such as "Breadcrumb" or "You are here". Don't add the word "navigation" – screen readers already announce the landmark type.

    How do I hide breadcrumb separators from screen readers?

    Add them with CSS (for example li + li::before { content: "›"; }) or put them in an element with aria-hidden="true". Typed characters inside the links are read aloud.

    Do breadcrumbs help SEO as well?

    Yes, they give search engines a clear site hierarchy and extra internal links. For accessibility, what counts is that they reflect the real structure of the site, not keyword-stuffed labels.

    • Multiple Ways: More Than One Path to a Page

      Multiple ways is WCAG success criterion 2.4.5. More than one way must be available to locate a web page within a set of web pages – for example navigation plus search or a site map – except where the page is the result of, or a step in, a process.

      Read definition: Multiple Ways: More Than One Path to a Page
    • ARIA Landmarks: Page Regions for Screen Readers

      ARIA landmarks are roles such as banner, navigation, main and contentinfo that identify the large regions of a page. Screen readers list them and let users jump directly to each region.

      Read definition: ARIA Landmarks: Page Regions for Screen Readers
    • Consistent Navigation: Same Menus, Same Order

      Consistent Navigation is WCAG success criterion 3.2.3. Navigational mechanisms that are repeated on multiple web pages within a set of web pages must occur in the same relative order each time they are repeated, unless a change is initiated by the user.

      Read definition: Consistent Navigation: Same Menus, Same Order
    • Link Purpose: Write Link Text That Makes Sense

      Link purpose is what a link does or where it leads. Under WCAG 2.4.4, users must be able to tell it from the link text alone or together with its programmatically determined context, such as the surrounding sentence.

      Read definition: Link Purpose: Write Link Text That Makes Sense

    Let AI Handle Website Accessibility

    Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

    1. 1Choose your plan
    2. 2Install in 2 min
    3. 3AI fixes your website
    4. Done