This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung

Accessibility

Why does a website need multiple routes to every page?

A website needs several ways to reach every page, because people search differently: some click through the menu, others type a term into search, others get an overview from a site map. WCAG criterion 2.4.5 requires at least two such routes — menu plus search, say, or menu plus site map. Pages that are a step in a fixed process are exempt, such as the payment page in a checkout flow.

Menu, search, and site overview complement each other

Each route serves a different way of orienting yourself. The menu helps when visitors know your terms — anyone looking for "Services" finds the item. Internal search helps when they bring their own words: "patio roof" leads to the target even if your menu item is called "Canopies". A site overview — a plain page listing all pages in an organised way — helps people who want a complete overview; for screen reader users, it's often the fastest route. For people with memory or concentration difficulties, the second route isn't a convenience, it's a lifeline when the first one leads nowhere.

How the audit service reports this criterion

Whether there are at least two ways to reach every page on your website is a question of overall structure: a machine would have to check every page against the menu, search, and overviews, and recognise exceptions such as order flows — a judgment that can't be made responsibly in an automated way. The audit service therefore makes no such claim here: the report openly marks the criterion as a manual check point. That's our basic principle — every WCAG criterion appears individually as passed, violated, needs manual review, or not automatable. You see what was checked, not just what stood out.

Examples

Only accessible via the menu

Not met

<nav>…</nav>
<!-- keine Suche, keine Sitemap, keine Verweise im Text -->

Passes

<nav>…</nav>
<form role="search" action="/suche"><label>Suche <input name="q"></label></form>
<a href="/sitemap">Alle Seiten</a>

Two paths to each page extend: menu plus search, menu plus sitemap or references in the text.

Offer at least one second route alongside the menu: internal search or a site map of all pages.
Link the site map in the footer of every page — that's where visitors expect it.
Spot-check five subpages: is each one reachable via at least two routes?
Add a breadcrumb trail ("Home › Services › Roof renovation") — it shows the current location and offers another way back.

Deutsche Fassung dieser Seite

FAQ

Which routes to a page count under WCAG 2.4.5?

Recognised routes include: navigation in the menu, internal search, a site map listing all pages, links between related content, and an overview on the homepage. Two of these are enough. Pages that are a step in a fixed process are exempt — the payment page of a checkout doesn't need a second route.

Does every small website need internal search?

No. Two routes are required, and search is just one of the possible options. For a small website with few pages, a simple site map that lists all pages in an organised way and is linked in the footer is enough alongside the menu. Search becomes worthwhile once visitors start searching for content using their own terms — in a guide section, say.

Can an automated test check whether there are multiple routes to every page?

Not responsibly. That would require checking every single page against the menu, search, and overviews, and correctly recognising exceptions such as checkout flows. Our audit report therefore openly marks the criterion as a manual check point instead of claiming an unsupported judgment. Which criteria were decided automatically is listed individually in the report for every audit.