A website can contain hundreds of pages without the visitor suspecting the extent. The sitemap, often relegated to the footer, remains the only place where the complete architecture of a domain is displayed in a single view. Yet, the way this map is designed determines whether it actually aids navigation or adds an additional layer of confusion.
Sitemap and WCAG 2.2 Compliance: What Changes for Navigation
Competitors largely address navigation menus, types of bars, and ergonomic best practices. They overlook a recent normative angle: the WCAG 2.2 criteria fundamentally change how a detailed sitemap should be constructed.
Criterion 2.4.5 (Multiple Ways) requires that the user has more than one way to reach each page. A main menu is no longer sufficient if the site exceeds a few dozen pages. The detailed map then becomes a compliance mechanism, not just a footer gadget.
Criterion 2.4.11 (Focus Not Obscured) adds a technical constraint: when a visitor navigates via keyboard through a long list of links, the keyboard focus must never disappear behind a sticky header or a cookie consent banner. For a sitemap that sometimes displays several hundred links, this necessitates rethinking the positioning of fixed elements on the page.
Criterion 2.5.8 (Target Size) requires that each clickable target be large enough to be activated without error. A cramped sitemap in 11-pixel font with links stuck together does not meet this requirement, even if all links technically work.
Reading a Sitemap: Spotting the Hierarchy Before Clicking
A detailed sitemap is only useful if its structure reflects the actual hierarchy of the content. Before clicking, the visitor should be able to identify the main categories, subcategories, and the depth level of each page within seconds. For example, you can view the sitemap of By Caroline and CO to see how a clear branching organizes content thematically without overwhelming the reader.
Most sitemaps consist of a flat list of links. Field feedback varies on this point: some users prefer an alphabetical listing, while others prefer a thematic organization. The available data does not allow for a definitive conclusion, but grouping by categories with visual indentation reduces cognitive load for the majority of visitors.
Elements That Distinguish a Readable Sitemap from a Useless One
- Descriptive link titles that reflect the actual title of the target page, not generic labels like “learn more” or “click here”.
- Indentation or a bullet system that materializes depth levels (category, subcategory, final page).
- A stable logical order, identical to that of the main menu, to comply with criterion WCAG 3.2.3 (Consistent Navigation).
- A visual separation between thematic blocks, even if it’s just an additional white space.
HTML Sitemap and XML Sitemap: Two Tools, Two Functions
Confusion is common. The HTML sitemap is a page intended for human visitors. The XML sitemap is a technical file intended for indexing robots from Google and other search engines. Both share the same name, but they do not serve the same audience.
The XML sitemap lists all URLs with their metadata (last modified date, update frequency, relative priority). It is not meant to be read by a human. In contrast, the HTML sitemap does not necessarily contain all URLs: it presents the pages useful to the visitor, grouped in an understandable way.
When the HTML Sitemap Complements Internal Search
An internal search engine helps when the visitor knows what they are looking for. The sitemap helps when they do not know yet. It is an exploration tool, not a query tool. On sites with highly segmented content (product catalog, blog with hundreds of articles, institutional site with multiple branches), the HTML sitemap remains the only way to visualize the entire scope without typing keywords.
Sites that offer both (internal search and detailed sitemap) cover both modes of navigation: active search and passive exploration. Removing one in favor of the other amounts to closing off an access path.
Designing a Sitemap That Works on Mobile
On a desktop screen, a three-column sitemap with a hundred links remains readable. On mobile, the same sitemap becomes a wall of text impossible to scan. With the majority of web traffic coming from mobile devices, a sitemap designed solely for desktop loses most of its audience.
Two approaches work on small screens. The first is to use collapsible sections (accordions) by category: the visitor only expands the block that interests them. The second relies on internal anchor navigation at the top of the page, with each anchor linking to the corresponding section further down.
In both cases, adherence to criterion WCAG 2.5.8 on target size remains relevant: links that are too small or too close together on a touchscreen generate tap errors. A minimum spacing between each clickable link avoids this problem without cluttering the layout.
Known Limitations of Sitemaps on Very Large Sites
Beyond several thousand pages, a comprehensive HTML sitemap itself becomes a navigation problem. Some e-commerce or media sites then choose a partial sitemap, limited to main categories and the most visited pages. This pragmatic approach accepts that a sitemap does not replace a complete navigation architecture, but rather complements it.
The detailed sitemap remains an underestimated navigation tool. Its value lies not in the exhaustiveness of the links it contains, but in the clarity of their organization. A poorly structured map adds noise. A well-designed map offers the visitor a readable map of the territory, regardless of the device used.