CARVIEW

MOTORHOMES

Select Language

HTTP/2 200 date: Thu, 09 Oct 2025 02:24:25 GMT content-type: text/html; charset=utf-8 content-encoding: gzip last-modified: Tue, 11 Oct 2016 20:23:50 GMT cache-control: max-age=31536000 expires: Fri, 09 Oct 2026 02:24:24 GMT vary: Accept-Encoding,Origin access-control-allow-origin: * x-backend: www-mirrors x-request-id: 98ba6be7bfe3165e strict-transport-security: max-age=15552000; includeSubdomains; preload content-security-policy: frame-ancestors 'self' https://cms.w3.org/ https://cms-dev.w3.org/; upgrade-insecure-requests cf-cache-status: BYPASS set-cookie: __cf_bm=jQ4cl8BKtKf1P5GHv3S2SDkCI77HCEK_L6HsuB6K_qs-1759976665-1.0.1.1-X__cDoMVPvim2V7fPK2kxWcTd20qiXQStrc_8VqCDV.CKUwS1nB2vC6nuwi9DRBmOeav8aIGyqbwMyaEmwFGcr4.MEjEH4THjs37kXxHYq0; path=/; expires=Thu, 09-Oct-25 02:54:25 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None server: cloudflare cf-ray: 98ba6be7bfe3165e-BLR alt-svc: h3=":443"; ma=86400 F66: Failure of Success Criterion 3.2.3 due to presenting navigation links in a different relative order on different pages | Techniques for WCAG 2.0

Skip to Content (Press Enter)

On this page:

F66: Failure of Success Criterion 3.2.3 due to presenting navigation links in a different relative order on different pages

Important Information about Techniques

See Understanding Techniques for WCAG Success Criteria for important information about the usage of these informative techniques and how they relate to the normative WCAG 2.0 success criteria. The Applicability section explains the scope of the technique, and the presence of techniques for a specific technology does not imply that the technology can be used in all situations to create content that meets WCAG 2.0.

Applicability

Applies to all technologies

This failure relates to:

Success Criterion 3.2.3 (Consistent Navigation)
- How to Meet 3.2.3 (Consistent Navigation)
- Understanding Success Criterion 3.2.3 (Consistent Navigation)

Description

This describes a failure condition for all techniques involving navigation mechanisms that are repeated on multiple Web pages within a set of Web pages (Success Criterion 3.2.3). If the mechanism presents the order of links in a different order on two or more pages, then the failure is triggered.

Examples

Failure Example 1: An XHTML menu presenting a series of links that are in a different relative order on two different pages

Examples of a navigation mechanism that presents links in a different order.

Page 1 Menu

Example Code:


<div id="menu"> 
    <a href="Brazil.htm">Brazil</a><br />
    <a href="Canada.htm">Canada</a><br />
    <a href="Germany.htm">Germany</a><br />
    <a href="Poland.htm">Poland</a> 
</div>

Page 2 Menu

Example Code:


<div id="menu"> 
    <a href="Canada.htm">Canada</a><br />
    <a href="Brazil.htm">Brazil</a><br />
    <a href="Germany.htm">Germany</a><br />
    <a href="Poland.htm">Poland</a> 
</div>

Resources

No resources available for this technique.

(none currently listed)

Tests

Procedure

Check to see if a navigation mechanism is being used on more than one Web page.
Check the default presentation of the navigation mechanism on each page to see if the list of links are in the same relative order on each Web page.

Note: "Same relative order" means that secondary navigation items may be in between the link items on some pages. They can be present without affecting the outcome of this test.

Expected Results

If #1 is true and #2 is false, then this failure condition applies and content fails the Success Criterion.

This Web page is part of Techniques and Failures for Web Content Accessibility Guidelines 2.0 (see the latest version of this document). The entire document is also available as a single HTML file. See the The WCAG 2.0 Documents for an explanation of how this document fits in with other Web Content Accessibility Guidelines (WCAG) 2.0 documents. To send public comments, please follow the Instructions for Commenting on WCAG 2.0 Documents.

Original Source | Taken Source