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.
Adjacent interactive elements that do the same thing are not both included - unless the outcome is a form of dismissal.
Why It Matters
Duplicated links and buttons double the tab stops and the screen reader announcements for no added function, which is pure cost for keyboard and screen reader users.
A common pattern is having a component that includes a linked image and some linked text, where both links go to the same content. Someone using screen reading software can be disoriented from the unnecessary chatter, and a keyboard user has to navigate through more tab stops than should be necessary. Combining adjacent links that go to the same content improves the user experience.
When repetitive interactive elements are used, remove them from the focus and reading order.
Use a single link instead of multiple links to the same destination.
Recommended Practices (Upstream)
Combine repetitive links into a single interactive element.
W3C Working Group Status
W3C Maturity Status:developing
Track / Group:input-operation
The draft records no open editors' notes on this provision.
W3C Threads on This Provision
No GitHub issue in w3c/wcag3 carries this provision's label, so there
is no recorded discussion to show. Cross-cutting threads that name no
provision are listed on the
Discussions page.
WCAG 2.2 Criteria That Map Here
From this site's reviewed WCAG 2.2 → WCAG 3 map. The map is
an interpretation, not a W3C mapping: W3C has not published one yet.
No mapping recorded. No WCAG 2.2 criterion in
this site's map is recorded as a predecessor of this provision.
Adjacent interactive elements that achieve the same outcome are not included in the page/view.
:::except-when
- That outcome is a form of dismissal.
:::
:::note
A common pattern is having a component that includes a linked image and some linked text, where both links go to the same content. Someone using screen reading software can be disoriented from the unnecessary chatter, and a keyboard user has to navigate through more tab stops than should be necessary. Combining adjacent links that go to the same content improves the user experience.
:::