Navigational mechanisms that are repeated throughout content occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA)
This checkpoint involves designing a consistent layout that enables users to predict where repeated elements in content appear, allowing quick navigation. For example, a low-vision user may depend on a search field that appears in the same location on each page of a Web site. Or, to better locate the home link in the left navigation area, a low-vision user may depend on the link appearing in the same relative order on each of a Web site's pages.
This checkpoint does not restrict removing or adding content. It requires only that content that is repeated in multiple places remain in the same relative order. For example, links may be removed from the left navigation area of a Web site as a user navigates the site but the links that are present must remain in the same relative order.
Note: Individual non-web documents and software programs (not in a set) should mark this checkpoint N/A because it applies only to things that appear in a set. Refer to the definitions of set of documents and set of software programs to determine when a group of documents or software programs is considered a set, as well as the WCAG2ICT 3.2.3 guidance.
Refer to Understanding SC 3.2.3 for more information (external link to WCAG).
This paragraph appears generically in all checkpoints. Review the General techniques as well as other tabs applicable to your technology. Prioritize the use of technology-specific techniques, and implement the General techniques as needed. You are always required to find, understand and implement accessible code techniques to meet the checkpoint. The documented techniques and supplements are not exhaustive; they illustrate acceptable ways to achieve the spirit of the checkpoint. If numbered, techniques are in order of preference, with recommended techniques listed first. Where used, IBM information that complements the WCAG techniques is indicated as supplemental.
Any item in this section represents a technique deemed sufficient. Ensure you review WCAG Common Failures to avoid development mistakes.
There are no specific Web (HTML, ARIA, CSS) techniques for this checkpoint. Refer to the General techniques section.
This checkpoint applies to a set of software programs. Because sets of software that meet this definition appear to be extremely rare, there are no specific Mobile Native iOS techniques for this checkpoint (3.2.3).
This checkpoint applies to a set of software programs. Because sets of software that meet this definition appear to be extremely rare, there are no specific Eclipse techniques for this checkpoint (3.2.3).
This checkpoint applies to a set of software programs. Because sets of software that meet this definition appear to be extremely rare, there are no specific Windows-based (MSAA+IA2) techniques for this checkpoint (3.2.3).
Many links in this checklist reside outside ibm.com at the Web Content Accessibility Guidelines (WCAG) 2.1. W3C Recommendation 05 June 2018: http://www.w3.org/TR/WCAG21/
Copyright © 1994-2019 World Wide Web Consortium, (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University, Beihang University). All Rights Reserved.
Copyright © 2001, 2019 IBM Corporation