Why HTML sitemaps improve website accessibility (WCAG and ADA)

TL;DR

An HTML sitemap is a page of links for people, and it is one accepted way to meet WCAG 2.4.5 Multiple Ways alongside the menu or site search. It does not replace skip links (2.4.1) or fix a broken menu. An XML sitemap is for search engines and does nothing for accessibility. Link the HTML sitemap from the footer of every page.

An HTML sitemap is one of the simplest accessibility features a website can have: a single page that lists every section of the site as plain links, grouped under headings. It gives people who cannot use a complex menu, or who just think differently about where things live, a second route to every page. It is also one of the most misunderstood, because “sitemap” means two different things, and only one of them helps a person.

This guide covers what WCAG actually says about sitemaps, what a sitemap does not fix, how to build an accessible HTML sitemap page, and where the XML sitemap for search engines fits in.

HTML sitemap vs XML sitemap

The two share a name and very little else.

QuestionHTML sitemapXML sitemap
Who reads itPeopleSearch engine crawlers
FormatA normal web page of linksA machine-readable file
Typical address/sitemap//sitemap.xml
Linked fromThe site’s footer or navigationrobots.txt and Google Search Console
Helps withAccessibility (WCAG 2.4.5) and wayfindingDiscovery and crawling

An XML sitemap is invisible to visitors. Nobody tabs through it and no screen reader user is ever sent to it, so on its own it does nothing for accessibility. When accessibility guidance mentions a site map, it means the HTML page.

Sitemap accessibility: what WCAG requires

WCAG never requires a sitemap by name. It requires outcomes, and a sitemap is one of the accepted ways to reach a few of them.

2.4.5 Multiple Ways (Level AA)

This is the criterion a sitemap exists for. The text reads: “More than one way is available to locate a web page within a set of web pages except where the web page is the result of, or a step in, a process.”

The reason is that people find things differently. Someone using a screen magnifier may see only a sliver of a mega menu at a time. Someone with a cognitive disability may find a flat, labelled list easier than a hierarchy of hover menus. Someone using voice control may prefer to search. Offering more than one route lets each person use the one that works.

W3C lists six sufficient techniques and asks for two or more of them:

  • G125: links to navigate to related pages
  • G64: a table of contents
  • G63: a site map
  • G161: a search function
  • G126: a list of links to all other pages
  • G185: linking to every page on the site from the home page

Most sites already have one route, the main navigation. Adding a sitemap is often the cheapest way to provide the second, especially on sites too small to justify a search engine. The process exception means pages that only exist as a step in a flow, such as a checkout confirmation or a search results page, do not need a second route.

Source: W3C, Understanding 2.4.5 Multiple Ways

2.4.8 Location (Level AAA)

“Information about the user’s location within a set of web pages is available.” W3C lists a site map as a sufficient technique here too, next to breadcrumbs and marking the current page in the navigation with aria-current. Level AAA is not required by most policies, but a sitemap that mirrors the site’s structure helps people understand where a page sits.

Source: W3C, Understanding 2.4.8 Location

2.4.6 Headings and Labels (Level AA)

“Headings and labels describe topic or purpose.” This applies to the sitemap page itself. A sitemap that is one long, unbroken list of links is hard to scan; a sitemap grouped under clear headings lets screen reader users jump from section to section with their heading shortcuts.

Source: W3C, Understanding 2.4.6 Headings and Labels

3.2.3 Consistent Navigation (Level AA)

“Navigational mechanisms that are repeated on multiple web pages within a set of web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.” If the sitemap link lives in the footer, it should be in the same spot in the footer on every page, so people learn where to find it once.

Source: W3C, Understanding 3.2.3 Consistent Navigation

What a sitemap does not fix

2.4.1 Bypass Blocks is a different problem

You will see articles claim that a sitemap satisfies 2.4.1 Bypass Blocks. It does not. That criterion reads: “A mechanism is available to bypass blocks of content that are repeated on multiple web pages.” It is about letting a keyboard or screen reader user skip the header and menu on every page to reach the main content.

W3C’s sufficient techniques for 2.4.1 are a skip link at the top of the page, links to each area of the content, ARIA landmarks, and headings at the start of each section. A site map is not on the list. A sitemap is a separate page; it cannot help someone skip the dozens of menu links standing between them and the article they already opened.

Every page still needs its own way past repeated content. The usual answer is a skip link plus proper landmarks:

<body>
  <a class="skip-link" href="#main">Skip to main content</a>
  <header>
    <nav aria-label="Main">...</nav>
  </header>
  <main id="main">...</main>
  <footer>...</footer>
</body>

Source: W3C, Understanding 2.4.1 Bypass Blocks

It does not repair a broken menu

A sitemap is a second route, not a replacement for the first. If the main menu cannot be opened with a keyboard, has no visible focus, or traps focus, those are failures of other criteria (2.1.1 Keyboard, 2.4.7 Focus Visible, 2.1.2 No Keyboard Trap) and the sitemap does not excuse them. Fix the menu too; the accessible navigation menu guide includes a disclosure example and keyboard checks.

How to build an accessible HTML sitemap

W3C’s technique G63 sets the bar. A site map is a page that links to the site’s sections, and it is only valid if it is complete and current: a page “is not a valid site map” if it leaves out sections, organizes them differently from the site, or contains broken links. G63’s test procedure asks you to check that:

  1. the site contains a site map;
  2. each link in it leads to the matching section of the site;
  3. each page it links to contains a link back to the site map;
  4. every page on the site can be reached by following links that start at the site map.

Point 3 is the one people miss. The simplest way to satisfy it is a sitemap link in the site-wide footer, so every page carries it.

Source: W3C, Technique G63: Providing a site map

Example markup

Here is a complete sitemap page body for a small business site. It uses real HTML structure rather than styled divs, so assistive technology gets the hierarchy for free.

<main id="main">
  <h1>Site map</h1>
  <p>Every page on this site, grouped by section.</p>

  <nav aria-label="Site map">
    <h2 id="sitemap-services">Services</h2>
    <ul aria-labelledby="sitemap-services">
      <li><a href="/services/">All services</a>
        <ul>
          <li><a href="/services/web-design/">Web design</a></li>
          <li><a href="/services/seo/">Search engine optimization</a></li>
          <li><a href="/services/accessibility-audits/">Accessibility audits</a></li>
        </ul>
      </li>
    </ul>

    <h2 id="sitemap-articles">Articles</h2>
    <ul aria-labelledby="sitemap-articles">
      <li><a href="/articles/">All articles</a></li>
      <li><a href="/articles/html-sitemap-guide/">How to build an HTML sitemap</a></li>
    </ul>

    <h2 id="sitemap-company">Company</h2>
    <ul aria-labelledby="sitemap-company">
      <li><a href="/">Home</a></li>
      <li><a href="/about/">About</a></li>
      <li><a href="/contact/">Contact</a></li>
      <li><a href="/privacy/">Privacy policy</a></li>
      <li><a href="/accessibility/">Accessibility statement</a></li>
    </ul>
  </nav>
</main>

What each piece is doing:

  • One h1, then an h2 per section. Screen reader users can list the headings and jump straight to “Articles” (2.4.6). Keep heading levels in order; do not skip from h2 to h4 for styling.
  • Nested ul lists. Screen readers announce “list, 3 items” and the nesting level, which conveys the hierarchy that sighted users get from indentation (1.3.1 Info and Relationships).
  • A nav with its own aria-label. The page already has a main navigation landmark. Labelling this one “Site map” lets people tell the two apart in a landmarks list. Some teams leave the sitemap out of nav and rely on headings alone; either is defensible, but if you use nav, label it.
  • Link text that matches the page title. “Accessibility audits” tells you where the link goes. “Click here” or a bare URL does not (2.4.4 Link Purpose).
  • No hover-only or collapsed sections. Expandable sitemaps exist on very large sites, but every toggle then needs to be a real button with aria-expanded. For most sites, showing everything is simpler and more usable.

Keep it current

A stale sitemap fails G63. If your sitemap is a hand-written page, it will drift the first time someone adds a page and forgets. Generate it from the same source as your navigation or your CMS’s page list, so a new page shows up in the sitemap automatically. Most CMS platforms and static site generators can output a list of published pages, and many SEO plugins can render an HTML sitemap from it.

  • The footer of every page. This meets G63’s “link back” test and 3.2.3, because the footer is the same on every page. Label the link “Site map”.
  • Your accessibility statement. If you publish one, mention the sitemap as an alternative way to find content.
  • The 404 page. Someone who followed a dead link is exactly the person who needs a list of everything that does exist.

Sitemaps and the ADA

The Americans with Disabilities Act does not mention sitemaps, and no regulation requires one by name. What the law requires depends on who you are.

State and local governments. In April 2024 the Department of Justice published a rule under ADA Title II that makes WCAG 2.1 Level AA the technical standard for the web content and mobile apps of state and local governments, including their agencies, special districts, and contractors providing services on their behalf. WCAG 2.1 AA includes 2.4.5 Multiple Ways, so these sites need at least two ways to find each page, and a sitemap is an easy one. As of October 2026, ada.gov lists the compliance dates as April 26, 2027 for governments serving 50,000 people or more, and April 26, 2028 for smaller governments and special districts, after an interim final rule published April 20, 2026 extended them. Check the page for current dates before you plan around them.

Source: ADA.gov, Fact sheet: the 2024 web rule

Businesses open to the public. The Department’s March 2022 guidance says the ADA’s requirements apply to the web offerings of businesses under Title III, but “The Department of Justice does not have a regulation setting out detailed standards,” and businesses “have flexibility in how they comply.” WCAG is described as helpful guidance rather than a mandate. In practice WCAG 2.1 AA is the common benchmark, so meeting 2.4.5 is a sound choice, but I would not tell a business the ADA requires a sitemap. This is general information, not legal advice.

Source: ADA.gov, Guidance on web accessibility and the ADA

The XML sitemap, for search engines

An XML sitemap does not help visitors, but it is still worth having for SEO. It tells search engines which URLs you want crawled. Google’s requirements, from its documentation:

  • A single sitemap can hold up to 50,000 URLs or 50MB uncompressed. Larger sites split it and use a sitemap index file.
  • The file must be UTF-8, with values entity escaped.
  • Use full, absolute URLs, and list the canonical version of each page.
  • Google uses lastmod only if it is consistently accurate, meaning the date of the last significant change to the page. It ignores changefreq and priority.

A minimal file:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.com/services/accessibility-audits/</loc>
    <lastmod>2026-10-20</lastmod>
  </url>
</urlset>

Tell search engines where it is in two places. Add a line anywhere in robots.txt:

Sitemap: https://www.example.com/sitemap.xml

Then submit it in Google Search Console’s Sitemaps report, which shows when Google last read it and any errors. Submitting is a hint, not a guarantee that every URL is crawled.

Source: Google Search Central, Build and submit a sitemap

Most sites should have both: the HTML page for people, and the XML file for crawlers. They can be generated from the same list of pages, which keeps them in step.

HTML sitemap accessibility checklist

  • The site has an HTML sitemap page, not only sitemap.xml.
  • The site offers at least one other way to find pages (navigation, search, or related links), so 2.4.5 has two routes.
  • The sitemap lists every section and matches how the site is organized.
  • Every link works; nothing points to a removed page.
  • The page has one h1 and an h2 for each section, in order.
  • Links sit in real ul lists, nested to show hierarchy.
  • If wrapped in nav, it carries aria-label="Site map".
  • Link text matches each page’s title.
  • A “Site map” link sits in the same place in the footer on every page.
  • The sitemap is generated from the site’s page list, so it stays current.
  • Every page also has a skip link and landmarks for 2.4.1. The sitemap does not cover that.
  • The XML sitemap is referenced in robots.txt and submitted in Search Console.

Sources

Frequently asked questions

Is a sitemap required for WCAG compliance?

No. WCAG 2.4.5 Multiple Ways (Level AA) requires more than one way to find a page within a site. A sitemap is one accepted way; site search, a table of contents, links between related pages, and a list of all pages are others. W3C's sufficient techniques ask for two or more of them.

Does an XML sitemap help accessibility?

Not directly. An XML sitemap is a file for search engines, and people do not read it. For 2.4.5 Multiple Ways, the sitemap has to be an HTML page that visitors can reach and read, linked from the site like any other page.

What is the difference between an HTML sitemap and an XML sitemap?

An HTML sitemap is a page for visitors that lists the site's pages as links, grouped under headings. An XML sitemap is a machine-readable file at a URL such as /sitemap.xml that lists canonical URLs for search engines to crawl. Many sites have both, and they do different jobs.

Does a sitemap meet WCAG 2.4.1 Bypass Blocks?

No. 2.4.1 is about skipping content that repeats on every page, such as the header and menu. W3C's techniques for it are skip links, ARIA landmarks, and headings on each page. A sitemap is not one of them.

Which WCAG success criteria apply to a sitemap page?

2.4.5 Multiple Ways is the criterion a sitemap helps meet, and 2.4.8 Location (Level AAA) lists it as a sufficient technique. The sitemap page itself must also meet 2.4.6 Headings and Labels, and under 3.2.3 Consistent Navigation the link to it should sit in the same place on every page.

Does the ADA require a sitemap?

No law names a sitemap. The 2024 Department of Justice rule for state and local governments adopts WCAG 2.1 Level AA, which includes 2.4.5 Multiple Ways. For businesses, the Department's 2022 guidance says websites must be accessible but sets no specific technical standard.