Table of Contents

    Unless the service is a series of steps, there must be different ways for people to locate and navigate content. Different people will have different preferences, for example someone with a cognitive disability may prefer to browse a sitemap to locate content, whereas someone using magnification may prefer to use search instead of scrolling through a lengthy navigation block.

    Accessibility Requirements for 2.4.5 Multiple ways (AA)

    • Adding a sitemap page which links to every page on your website; and
    • Including a search function on every page (by adding it to the header); and
    • Providing a clear and consistent main navigation menu.

    Common mistakes for 2.4.5 Multiple ways (AA)

    • TBC

    Techniques for 2.4.5 Multiple ways (AA)

    HTML Technique

    Common Failures for 2.4.5 Multiple ways (AA)

    The following are common mistakes that are considered failures of Success Criterion 2.4.5 by the WCAG Working Group.

    FAQs for Multiple ways

    What are the examples of creating Multiple ways in a website?

    Provide a clear and consistent main navigation menu
    Include a search function on every page
    Add a sitemap page which links to every page
    Create a homepage that includes links to all the pages
    Include a table of contents page
    Provide repetition of important links by including those links in the footer
    Create a breadcrumb navigation for processes and sub-layered pages.

    Why is this necessary?

    Users have different preferences in how to navigate content and may rely on a specific technique that is easier to comprehend. Providing multiple ways to navigate content within a site or application ensures all users can find information in a way that best suits their needs.

    Related to 2.4.5 Multiple Ways (AA)

    2.4.1 Bypass blocks (A)

    2.4.2 page title (A)

    Useful resources for 2.4.5 Multiple ways (AA)

    Leave a Reply

    Your email address will not be published. Required fields are marked *