The 2025 TestParty Guide to WCAG 2.4.5 – Multiple Ways (Level AA)

Why did the website visitor bring a map, a compass, AND a search bar? Because they knew the site passed WCAG 2.4.5 – they had multiple ways to find what they needed!

WCAG 2.4.5 Multiple Ways requires that users can find web pages through more than one navigation method—like search, sitemaps, or menus. This criterion ensures people with cognitive disabilities, screen reader users, and anyone who gets lost in complex site structures can always find an alternative path to their destination.

Table of Contents

• What WCAG 2.4.5 Requires
• Why This Matters
• Quick Implementation Guide
• Common Mistakes to Avoid
• How to Test for WCAG 2.4.5
• How TestParty Helps
• FAQs

What WCAG 2.4.5 Requires

WCAG 2.4.5 mandates that every web page within a website must be reachable through at least two different navigation mechanisms.

Key requirements:

• Provide at least two ways to locate any page (search, sitemap, table of contents, navigation menu, related links, etc.)
• The exception: pages that are part of a process or workflow (checkout steps, multi-page forms) don't need multiple navigation methods
• Both navigation methods must be functional and accessible

What counts as a "way":

• Site-wide search functionality
• Hierarchical navigation menus
• Sitemap (HTML or XML accessible to users)
• Table of contents
• Breadcrumb trails
• Related links or "You might also like" sections
• A-Z indexes

Important exception: If a page is a step in a process—like page 2 of a checkout flow or step 3 of a loan application—you don't need to provide multiple ways to reach it. Users are expected to follow the linear process.

Why This Matters

Different people navigate websites in fundamentally different ways. Someone with a cognitive disability might struggle with hierarchical menus but excel with search. A screen reader user might prefer a sitemap over drilling through nested dropdowns. A user with motor impairments might find breadcrumbs easier than navigating back through menus.

Legal and compliance context:

WCAG 2.4.5 is a Level AA requirement, making it mandatory for ADA Title II compliance, Section 508 federal procurement, EN 301 549 (European standard), and the European Accessibility Act. Organizations that fail to provide multiple navigation methods face legal risk—particularly in industries like education, government, healthcare, and ecommerce where users must access critical information.

Business benefits:

Multiple navigation methods improve findability for everyone, not just users with disabilities. Better findability means lower bounce rates, higher conversion, and reduced support costs. Sites with robust search and clear sitemaps consistently outperform those with single-path navigation.

Quick Implementation Guide

Implementing WCAG 2.4.5 is straightforward—you likely already have some of these mechanisms in place.

1. Add site-wide search

Place a search box in your header or footer that appears on every page. Ensure it's keyboard accessible and has a visible label.

<form role="search" action="/search">
  <label for="site-search">Search this site</label>
  <input type="search" id="site-search" name="q" />
  <button type="submit">Search</button>
</form>

2. Create an HTML sitemap

Build a page that lists all major sections and pages of your site. Link to it from your footer.

3. Implement breadcrumb navigation

Show users where they are in your site hierarchy and let them jump back to parent pages.

4. Use consistent navigation menus

A persistent header or sidebar menu counts as one navigation method—but you still need a second method like search or a sitemap.

5. Add related links or contextual navigation

"Related articles," "See also," or "Popular pages" sections provide additional pathways.

Relevant WCAG techniques: G125 (providing links to navigate to related pages), G64 (providing a table of contents), G63 (providing a site map), G161 (providing a search function).

Common Mistakes to Avoid

Only providing navigation menus

A single navigation menu—even a comprehensive one—doesn't satisfy 2.4.5. You need a second method like search or a sitemap.

Broken or inaccessible search

A search box that doesn't work, returns no results, or isn't keyboard accessible doesn't count as a navigation method. Test your search functionality regularly.

Hiding sitemaps from users

XML sitemaps for search engines don't count—users need an HTML sitemap they can actually access and use. Don't bury it three clicks deep; link to it from your footer.

Forgetting mobile navigation

Your multiple navigation methods must work on mobile devices. A desktop-only sitemap or search feature that disappears on mobile violates this criterion.

How to Test for WCAG 2.4.5

Testing for multiple ways is primarily a manual review process, though automated tools can flag missing elements.

Manual testing checklist:

• Identify at least two distinct navigation mechanisms (search, sitemap, menu, breadcrumbs, etc.)
• Verify both mechanisms appear on all pages (except process/workflow pages)
• Test that search returns relevant results and is keyboard accessible
• Confirm sitemap or table of contents links are current and functional
• Check that navigation methods work on mobile and desktop

What automated tools catch:

Automated scanners can detect the presence or absence of search forms, sitemap links, and navigation landmarks. TestParty and similar tools will flag pages missing common navigation patterns.

What requires human judgment:

You need to manually verify that navigation mechanisms actually work—that search returns useful results, that sitemap links aren't broken, and that the two methods are genuinely different (not just two menus with different styling).

How TestParty Helps

TestParty's AI-powered platform automates detection of missing or broken navigation mechanisms and guides teams toward WCAG 2.4.5 compliance at scale.

What TestParty detects:

TestParty scans your site's DOM and source code to identify navigation patterns across all pages. It flags:

• Pages missing a second navigation method (no search, sitemap, or breadcrumbs when only a menu exists)
• Broken or inaccessible search forms (missing labels, non-functional submit buttons, keyboard traps)
• Sitemap links that return 404s or point to outdated pages
• Inconsistent navigation patterns across templates (navigation present on some pages but missing on others)
• Mobile-specific navigation failures where desktop methods don't translate to responsive views

TestParty's template-level analysis is especially powerful for ecommerce platforms like Shopify and WordPress—it identifies whether your theme provides multiple navigation methods by default or if you need to add them.

How TestParty suggests fixes:

For common 2.4.5 violations, TestParty generates concrete remediation guidance:

• Code snippets for adding accessible search forms to headers or footers
• Recommendations for sitemap plugins or generators appropriate to your CMS
• Breadcrumb implementation examples using structured data and semantic HTML
• Suggestions for related-link modules or contextual navigation components

Because navigation is a site-wide pattern, TestParty works at the theme and template level. When you fix a navigation issue in a master template, the fix cascades across hundreds or thousands of pages automatically—no need to remediate page by page.

Developer workflow integration:

TestParty integrates into CI/CD pipelines and pull request workflows to catch navigation regressions before they ship:

• Pre-merge checks flag when a code change removes a search form or breaks sitemap links
• Real-time feedback in IDEs alerts developers if a new template lacks multiple navigation methods
• Automated regression testing ensures navigation mechanisms remain functional after updates

This shift-left approach prevents 2.4.5 violations from reaching production, especially during redesigns or CMS migrations when navigation patterns often break.

Ongoing monitoring:

TestParty's dashboards track navigation compliance over time:

• Alerts when search functionality degrades or sitemap links break
• Reports showing which page templates or sections lack multiple navigation methods
• Audit-ready documentation demonstrating compliance with WCAG 2.4.5 for legal and procurement reviews

For organizations managing multiple sites or frequent content updates, TestParty's monitoring prevents navigation issues from creeping back in after remediation.

TestParty doesn't just flag problems—it provides the context and code-level fixes your team needs to implement multiple navigation methods correctly and maintain compliance as your site evolves.

Some TestParty features described in this article are currently under development. Visit TestParty.ai to learn more about our current capabilities and roadmap, or book a demo at TestParty.ai/book-a-demo to see TestParty in action.

Disclaimer: Some of this article was generated with Large Language Models (LLMs) and Artificial Intelligence (AI). There may be some errors and we advise you to consult with human professionals for detailed questions.

FAQs About WCAG 2.4.5

What is WCAG 2.4.5 in plain language?

WCAG 2.4.5 requires that users can find any page on your website using at least two different methods—like a search box and a sitemap, or navigation menus and breadcrumbs. This ensures people who struggle with one navigation method have an alternative.

Is WCAG 2.4.5 required for ADA compliance?

Yes. WCAG 2.4.5 is a Level AA criterion, and ADA Title II compliance (for state and local governments) and many court settlements require Level AA conformance. Federal agencies must meet it under Section 508, and it's mandatory under EN 301 549 and the European Accessibility Act.

Does a navigation menu count as one of the "multiple ways"?

Yes, a site-wide navigation menu counts as one method. However, you still need a second method—like search, a sitemap, or breadcrumbs—to satisfy 2.4.5. A menu alone isn't enough.

Do I need multiple ways to reach every single page, including checkout steps?

No. Pages that are part of a process or workflow (like checkout steps, multi-page forms, or sequential tutorials) are exempt. Users are expected to follow the process linearly, so you don't need to provide alternative navigation for those pages.

What's the difference between an XML sitemap and an HTML sitemap for WCAG 2.4.5?

An XML sitemap is for search engines and doesn't help users navigate your site—it doesn't count toward 2.4.5. An HTML sitemap is a user-facing page that lists your site's pages and links, and it does satisfy the requirement as one of your navigation methods.