WCAG 3.0 is an active W3C Working Draft in development by the AGWG. Requirements, assertions, the conformance model and reporting tiers are still being developed and may change. The latest published draft is the 10 September 2026 Working Draft; this site follows the editors’ draft, which also includes exploratory provisions.
developingAssertion
Location Within Product Review
Group: layout • Guideline: user-orientation
Summary in Plain English
An organisational assertion: the organisation states that it reviewed the conventions for showing the user's current location and used patterns that work both visually and programmatically.
Why It Matters
Knowing where you are is the precondition for deciding where to go next; it is easily lost in deep or dynamic interfaces.
It is often helpful for users to understand where within a digital product they are. There are many ways to achieve this, for example, a breadcrumb. Ideally this is consistently presented throughout the conformance scope but for some pages/views it may make less sense to include. For example, including a breadcrumb trail on the homepage or on pages that sit outside the hierarchy, for example a shopping cart.
Test Procedure from the W3C Draft
Upstream has a test heading for this provision but has not written
the procedure yet, and no test steps have been written here.
Generic advice would apply to almost any provision, so none is shown.
W3C Working Group Status
W3C Maturity Status:developing
Track / Group:layout
The draft records no open editors' notes on this provision.
W3C Threads on This Provision
1 GitHub thread carrying 0 comments,
fetched from w3c/wcag3 by the
tracker. Titles, numbers and states are the threads' own.
Nobody has read these threads and written up the positions yet, so
only the threads themselves are listed.
[Title, role, or organization] asserts that:
* We have reviewed conventions for presenting current location within the conformance scope.
* The presentation of current location within the conformance scope uses appropriate visually and programmatically patterns.
:::note
It is often helpful for users to understand where within a digital product they are. There are many ways to achieve this, for example, a breadcrumb. Ideally this is consistently presented throughout the conformance scope but for some pages/views it may make less sense to include. For example, including a breadcrumb trail on the homepage or on pages that sit outside the hierarchy, for example a shopping cart.
:::
::assertion-required
* title, role, or organization making the assertion (if different from the conformance claim)
* date of assertion (if different from the date of the conformance claim)
::assertion-recommended
* design log capturing decision to use specific approaches to current location patterns used within the conformance scope
* if a non-conventional design pattern is used, usability testing results that demonstrate the utility of the design approach taken