The site map of a content publisher or an online professional remains an underestimated navigation element. On Philippe Bredif’s site, this page serves a specific purpose: to provide an overview of the hierarchy, sections, and available resources. Far from being just a technical file intended for search engines, the site map here constitutes a structured entry point for visitors.
Site Map and Digital Accessibility: What the Regulatory Framework Requires
Since June 28, 2025, the European Accessibility Act applies to several categories of digital services in Europe. E-commerce sites, banking services, passenger transport platforms, and electronic communications are directly concerned. Microenterprises providing services benefit from an exemption under certain conditions.
The French RGAA (General Reference for Improving Accessibility) includes the “site map” page among the pages that must be included in an audit sample. An accessibility audit must take into account, when they exist, the homepage, contact page, legal notices, accessibility page, site map page, help page, and authentication page.
This framework goes beyond mere technical compliance. It aims to ensure that every user, including those navigating with a keyboard or using a screen reader, can access all content. A well-constructed site map fulfills this function by providing a comprehensive and readable list of all pages, without relying on dropdown menus or JavaScript animations.
For those who wish to explore the site map of Philippe Bredif, the page provides access to the complete hierarchy and allows for quick identification of a section or specific content.
Heading Structure and Keyboard Navigation: Criteria for a Usable Site Map
Displaying a list of links is not enough to make a site map functional. To be truly usable, this page must meet several technical requirements that go beyond visual appearance.
- A consistent heading hierarchy: each section of the map must use ordered heading levels (H2, H3) without jumps, so that assistive technologies can convey the logical structure of the content.
- Keyboard navigation must remain functional across the entire page. A user without a mouse should be able to navigate through each link in the map in a logical order, without getting stuck on an interactive element.
- Text alternatives for non-text content (images, icons) must be present. A site map that uses pictograms without a descriptive alt attribute creates a barrier for screen readers.
- The color contrast and size of clickable areas directly influence the ease of navigation, especially on mobile where the interaction space is limited.
These criteria do not represent an exceptional level of requirement. They correspond to best practices documented by the RGAA and included in European accessibility standards.
HTML Site Map and XML Sitemap: Two Distinct Functions
A common confusion is to equate the site map visible to visitors (HTML page) with the sitemap.xml file intended for indexing bots. Both serve navigation purposes but for different audiences.
The XML sitemap lists the URLs of a site with metadata (last modified date, update frequency, relative priority). It is aimed exclusively at search engines. Google, Bing, or other crawlers use it to discover pages that may not be sufficiently linked by internal links.
The HTML site map is for humans. It presents the hierarchy in a visual and clickable manner. On a site like Philippe Bredif’s, this page allows users to bypass a main menu that may not display all sections or to find old content without going through the internal search engine.
The two formats complement each other but do not replace each other. A site that offers only an XML sitemap without an HTML map deprives its visitors of a direct navigation tool. Conversely, an HTML map without an XML sitemap can slow down the indexing of new pages by search engines.
Limitations and Points of Caution Regarding Site Map Updates
A site map is only valuable if it reflects the actual state of the content. However, the synchronization between the map and the published pages is not always automatic. On the most common CMS platforms, the site map page can be generated manually or via an extension. In both cases, a deleted article or a modified URL may continue to appear in the map, generating dead links.
This issue is not trivial for accessibility. A user who clicks on a link in the map and encounters a 404 error loses confidence in the reliability of navigation. For assistive technologies, a broken link interrupts the journey and requires going back, which represents additional cognitive and motor effort.
Field feedback varies on the ideal frequency of checks. Some extensions update the site map with every publication. Others require manual action. Regularly checking the consistency between the map and the actual content of the site remains the only reliable guarantee, regardless of the technical solution used.
The site map page of Philippe Bredif illustrates a concrete use of this navigation tool. It makes the entire available hierarchy visible and facilitates access to different sections. Its relevance depends, as with any site, on the rigor with which it is kept up to date and its compliance with the accessibility criteria imposed by the European regulatory framework and the RGAA.
