Skip to Content (Press Enter)

This document is a draft, and is designed to show changes from a previous version. It is presently showing added text,changed text,deleted text,[start]/[end] markers,and Issue Numbers.

Hide All Edits   |   Toggle Deletions  |   Toggle Issue Numbers   |   Toggle [start]/[end] Markers   |   Show All Edits

Changes are displayed as follows:

-

Multiple Ways:
Understanding SC 2.4.5

2.4.5 Multiple Ways: More than one way is available to locate [begin add]a Web page [end add] [begin delete]content[end delete] within a set of Web pages [begin add]except [end add]where the Web Page is [begin delete]not [end delete]the result of, or a step in, a process. [2229] (Level AA)

The intent of this success criterion is to make it possible for users to locate content in a manner that best meets their needs. Users may find one technique easier or more comprehensible to use than another.

  • Providing an opportunity to navigate sites in more than one manner can help people find information faster. Users with visual impairments may find it easier to navigate to the correct part of the site by using a search, rather than scrolling through a large navigation bar using a screen magnifier or screen reader. A person with cognitive disabilities may prefer a table of contents or site map that provides an overview of the site rather than reading and traversing through several Web pages. Some users may prefer to explore the site in a sequential manner, moving from Web page to Web page in order to best understand the concepts and layout.

  • Individuals with cognitive limitations may find it easier to use search features than to use a hierarchical navigation scheme that be difficult to understand.

Resources are for information purposes only, no endorsement implied.

(none currently documented)

Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this success criterion. The techniques listed only satisfy the success criterion if all of the WCAG 2.0 conformance requirements have been met.

  1. Using two or more of the following techniques:

Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.

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

(No failures currently documented)

Key Terms

process

series of user actions where each action is required in order to complete an activity

Example 1: Successful use of a series of Web pages on a shopping site requires users to view alternative products, prices and offers, select products, submit an order, provide shipping information and provide payment information.

Example 2: An account registration page requires successful completion of a Turing test before the registration form can be accessed.

set of Web pages

collection of Web pages that [begin add]share a common purpose and that are created by the same[end add] [begin delete]have a specific relationship to each other and that are created as a body of work by an[end delete] author, group or organization [2213]

Note: Different language versions would be considered different [begin add]sets of Web pages[end add] [begin delete]bodies of work[end delete].

[begin delete]
[begin delete]

Example: A set of Web pages that make up a report, a test, an exercise, a catalog, or an application.

[end delete]
[end delete]
Web page

[begin add]a non-embedded resource [begin delete]that is referenced by a URI[end delete] [begin add]obtained from a single URI using HTTP[end add] plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent [end add] [begin delete]a resource that is referenced by a URI and is not embedded in another resource, plus any other resources that are used in the rendering or intended to be rendered together with it[end delete] [1948]

Note 1: Although any "other resources" would be rendered together with the primary resource, they would not necessarily be rendered simultaneously with each other.

Note 2: For the purposes of conformance with these guidelines, a resource must be "non-embedded" within the scope of conformance to be considered a Web page.

Example 1: A Web resource including all embedded images and media.

Example 2: A Web mail program built using Asynchronous JavaScript and XML (AJAX). The program lives entirely at http://example.com/mail, but includes an inbox, a contacts area and a calendar. Links or buttons are provided that cause the inbox, contacts, or calendar to display, but do not change the URL of the page as a whole.

Example 3: A customizable portal site, where users can choose content to display from a set of different content modules.

Example 4: When you enter "http://shopping.example.com/" in your browser, you enter a movie-like interactive shopping environment where you visually move about a store dragging products off of the shelves around you [begin add]and[end add] into a visual shopping cart in front of you. Clicking on a product causes it to be demonstrated with a specification sheet floating alongside.