You’re looking for a specific page on a website, but the menu isn’t helping. You scroll, click through several sections, then go back. A sitemap can save you from this tedious process. Often tucked away at the very bottom of a site, this page lists all its content in one place. But it needs to be well designed and genuinely usable.
Keyboard accessibility: what sets a useful sitemap apart from a simple footer link
Most websites have a sitemap. The link is usually in the footer, next to the legal notices. Its presence is reassuring, but it doesn’t guarantee anything.
WCAG 2.4.5, a Level AA criterion, requires users to have at least two ways to find a page, such as the main menu, a search engine, or a sitemap. There is an exception for pages that are part of a process (checkout steps, sequential forms). The sitemap must cover the entire site hierarchy to serve this purpose. A partial sitemap that shows only the main sections, without their subpages, is not a reliable alternative navigation method.
WCAG 2.2 goes further. It includes criteria for keyboard focus order, focus visibility, and ensuring that a focused element is not entirely obscured by another component.
A sitemap can therefore provide an additional way to find your way around, even if the rest of the site isn’t usable with a keyboard. An accessible sitemap link is no use if the links it contains can’t receive focus or aren’t visible when tabbing through them.
To check this for yourself, open the sitemap page and try to reach any link using only the Tab key. Check whether each link has a visible focus indicator (an outline or a change in color). If focus disappears or skips links, the sitemap is there, but it isn’t functional for keyboard navigation.

HTML sitemap: how to read and use this page to find content
You may have confused the HTML sitemap, which is intended for visitors, with the sitemap.xml file, which is intended for search engines. They are two different things. The XML file is a technical list that Google and Bing use to index pages. An HTML sitemap is a regular web page, readable by people and organized into sections and subsections.
A well-designed HTML sitemap looks like a table of contents. The main sections appear first, followed by indented subsections, like chapters and subchapters. Each heading is a clickable link that takes you directly to the relevant page.
Here’s a simple way to use one effectively: use your browser’s built-in search (Ctrl+F or Cmd+F) directly on the sitemap page. Type a keyword related to what you’re looking for. Your browser’s search function will find the link in seconds, even on a site with hundreds of pages. It’s faster than scanning the entire list.
For a real-world example, the Valbreon sitemap displays the site’s different sections in a structured list, making it easy to find a section without using the main menu.
What a sitemap needs to include to be genuinely useful
Not all sitemaps are created equal. Some show only five or six links to the main sections, effectively duplicating the navigation menu without adding anything useful.
- Key pages (home page, sections, subsections) and deeper pages (articles, product pages, service pages) should all be listed to provide a complete overview.
- Temporary pages or pages with no original content (search results pages, empty tag pages, pagination pages) don’t belong in an HTML sitemap because they add clutter without helping users navigate.
- The organization should reflect the site’s actual hierarchy: subpages should appear under their parent section, with visual spacing or indentation that makes the structure easy to follow.
Regulations and web navigation: what the European Accessibility Act changes in practice
Since June 28, 2025, the European Accessibility Act (EAA) has required certain consumer-facing digital services, particularly in e-commerce, to meet accessibility requirements. Microenterprises providing services are exempt under the thresholds set out in the directive.
For other businesses, having an accessible sitemap contributes to compliance, but doesn’t guarantee it on its own. Website accessibility depends on a range of criteria covering navigation, content, forms, and interactive components. A sitemap is just one link in the chain.
This regulatory context is prompting web teams to treat the sitemap not as a secondary page, but as a compliance tool that needs regular testing.
Test whether a sitemap is genuinely useful with three quick checks
You’ve found a sitemap on a website. Before relying on it, run these three quick checks to see whether it does its job.
- Completeness: compare the number of links in the sitemap with the number of sections shown in the menu. If the sitemap doesn’t contain more links than the menu, it adds nothing and isn’t a genuine alternative navigation method.
- Keyboard navigation: move through the page using the Tab key. Each link should receive focus in a logical order (top to bottom, left to right). If focus skips sections or becomes invisible, the sitemap isn’t accessible.
- Up-to-date links: click several links, especially those in subsections. If any lead to 404 errors or redirected pages, the sitemap is no longer maintained and can’t be relied on.

An HTML sitemap remains one of the most direct ways to access any page on a website, provided it’s complete, up to date, and keyboard-navigable. Next time you can’t find information through the menu, check the footer: the sitemap link is almost always there.



