An HTML sitemap does more than list URLs. Its real, often underused, purpose is to compensate for the limitations of a main navigation menu that hides deep content. When a menu has more than three levels or relies on complex interactions (dropdown menus, JavaScript filters), some pages become invisible to certain user groups. A sitemap restores direct access to this content, provided it is built carefully.
Testing a sitemap with assistive technologies: a practical protocol
A sitemap that meets WCAG criteria does not prove that its content is easy to find in real-world situations. The W3C reminds us that meeting technical accessibility criteria does not guarantee that content is easy to understand or locate for the people concerned.
To verify a sitemap’s real-world usefulness, we recommend a three-step test with users of different assistive technologies.
- Recruit at least three distinct user profiles: a screen reader user (NVDA or JAWS), someone who navigates exclusively by keyboard, and someone with cognitive or attention-related disabilities who uses a simplified display.
- Define a specific search scenario: ask each participant to find a deeply nested page (at least three levels down), first through the main navigation and then through the sitemap. Measure the time taken and number of interactions in each case.
- Compare the journeys: if the sitemap reduces the number of tab presses or clicks by at least half compared with the menu, it is doing its job. Otherwise, its structure needs to be reviewed.
This protocol highlights the gap between technical compliance and lived experience. A sitemap whose link list is not organized under headings that a screen reader can navigate often fails this test, even if it passes automated validators.
For an example of hierarchical organization on an online publication, the Journal Du Web sitemap organizes its sections using heading levels that make sequential keyboard navigation easier.

XML sitemap and HTML sitemap: two functions that navigation cannot replace
Confusion between XML sitemaps and HTML sitemaps persists. The XML file is intended for crawlers. It signals URLs to search engines without guaranteeing that they will be crawled or indexed. Google describes it as a supplement, not a substitute for internal links.
An HTML sitemap, by contrast, is intended for visitors. It provides a complete, human-readable map of the site structure. These two tools address different needs and are not interchangeable.
What XML sitemaps no longer do
The <priority> and <changefreq> tags are ignored by Google. Including them in the file does not cause an error, but it does not influence crawling behavior. Spending time on these settings means optimizing a signal that nobody reads.
The lastmod tag is only taken into account if it reflects an actual change to the content. Changing the copyright date in the footer or regenerating the file without changing the content will not fool crawlers. Google clarified this in a June 2023 announcement on Search Central.
When an HTML sitemap compensates for a flawed architecture
On a site with more than a few hundred pages, some URLs receive no contextual internal links. They exist in the CMS and may appear in the XML sitemap, but visitors cannot reach them through the site’s navigation. An HTML sitemap fixes this by providing a single entry point to all published pages.
This safety-net role becomes critical for dynamic sections (blogs, news, archives), whose content quickly disappears from the homepage and menus.
HTML sitemap structure: technical choices that change the experience
A sitemap that lists hundreds of links without visual hierarchy does not make anything easier. The difference between a useful sitemap and a decorative one comes down to three design decisions.
The first concerns the heading levels (Hn) used to divide sections. Screen reader users can navigate from heading to heading. If the sitemap uses H2 headings for main sections and H3 headings for subsections, users can jump straight to the section they are interested in. Without this hierarchy, they have to work through the entire list.
The second decision concerns scope. A sitemap is not a duplicate of the menu. It includes key pages, subsections, and deep content, but excludes technical pages (legal notices, cookie policy, internal search results pages). Adding these pages makes the sitemap harder to read without improving navigation.
The third concerns display order. Sorting sections by how often they are visited rather than alphabetically reduces search time for most visitors. Internal analytics data can provide this information.

European Accessibility Act: what a sitemap alone cannot cover
Since June 28, 2025, the European Accessibility Act has applied to certain digital services, including e-commerce services. Its scope does not extend indiscriminately to every business website: exemptions apply depending on the type of service and the size of the organization.
An accessible sitemap contributes to ease of use, but it is not enough to establish a site’s compliance with this regulatory framework. Compliance requires a comprehensive audit covering the perceivability, operability, understandability, and robustness of all interactive components.
A sitemap remains one link in a larger chain. Its absence may constitute a compliance issue if no alternative mechanism provides access to all content. Its presence, however, does not exempt a site from any other obligations.
An HTML sitemap should be treated as a navigation component in its own right, tested with real users and maintained in step with the rest of the site structure. An outdated sitemap that lists deleted pages or omits recent sections undermines trust and the user experience instead of improving them.



