Your destination for everything in the adult industry.
ATN — All Things NSFW. Explore. Create. Build.

Check website breadcrumbs against the real page hierarchy.

Breadcrumbs help readers understand where a page belongs within a site and move to its parent pages. Their usefulness depends on a real, understandable hierarchy and reliable destinations. Review the page relationships before checking the component’s labels, links, and presentation; a decorative chain of labels cannot resolve an unclear content structure.

1. Identify the page’s actual hierarchy

Start with the page being reviewed and write its intended route through the site structure. Decide which category or collection is its parent and which higher-level pages help a reader orient themselves. If the same content appears in several collections, document how the site chooses the breadcrumb rather than inventing a different hierarchy on every visit.

W3C’s breadcrumb pattern describes links to parent pages in hierarchical order. That is a different purpose from reproducing a person’s browser history. Keep the breadcrumb consistent with the information architecture and check that the parent pages provide useful context for the current item.

Sources: [1]

2. Verify labels and parent destinations

Open every parent link from the actual rendered page. Check that its destination exists, uses the intended canonical route, and contains the category or context implied by its label. Look for an outdated category name that survived a page move or a link that returns to a general homepage when a useful parent page already exists.

Use understandable labels and compare them with the destination headings. Exact wording may differ for space, but the relationship should remain obvious. Check a deep page and a page near the top of the hierarchy so the component does not assume every article has the same number of ancestors.

3. Identify the navigation and current page

W3C recommends a labelled navigation landmark for the breadcrumb. When the current-page item is a link, its pattern uses aria-current="page"; that attribute is optional when the current item is not a link. Check the implemented markup and the exposed name, not just a screenshot of the component.

W3C’s example uses an ordered list and keeps decorative separators out of the accessibility tree. Treat the example as guidance that still needs testing in production. Review whether a separator is being announced as extra content and whether the current item can be distinguished without relying only on its color.

Sources: [1] [2]

4. Check keyboard access and long labels

Move through the links with a keyboard and confirm that focus remains visible. Follow a parent link and verify the resulting page. Repeat with a narrow viewport and a deliberately long real page title; inspect wrapping, spacing, and whether the final item is obscured or forces avoidable horizontal scrolling.

If the design shortens a path, confirm that the chosen behavior preserves useful orientation and access to the relevant ancestors. Record what was actually tested, including the viewport and input method. A successful markup check alone does not establish that the component works for every reader or assistive technology.

5. Recheck breadcrumbs when content moves

Include breadcrumbs in the checklist for renamed categories, moved pages, and navigation changes. Review the current page and representative siblings, because a shared template can distribute one stale parent relationship across many pages. Keep redirects and the displayed hierarchy aligned with the new structure.

Save the page path, expected ancestors, observed destinations, and any unresolved structural decision. Distinguish a broken link from an editorial question about where the content belongs; they may need different fixes. This review does not guarantee a particular search-result appearance or replace broader navigation and accessibility testing.

PUT IT INTO PRACTICE

Your quick checklist

  • The hierarchy reflects real parent pages.
  • Every parent destination and label is checked.
  • The navigation and current page are identified appropriately.
  • Keyboard access and long labels are reviewed.
  • Page moves trigger a new hierarchy check.

Sources & scope

W3C supports the breadcrumb pattern and semantic examples. The hierarchy, destination, and maintenance checklist is ATN editorial guidance. No live component or assistive-technology test is implied, and breadcrumbs do not guarantee search enhancements.

  1. W3C ARIA Authoring Practices: Breadcrumb pattern (opens in a new tab)Source checked October 10, 2026
  2. W3C ARIA Authoring Practices: Breadcrumb example (opens in a new tab)Source checked October 10, 2026

Published October 10, 2026. No affiliate links or paid placements in this guide.

ALL THINGS NSFW