Dieser Inhalt ist derzeit nur auf Englisch verfügbar
Audit identical-links-same-purpose
Ensure that links with the same accessible name serve a similar purpose
Impact:
Minor
WCAG-Konformität:
AAA
WCAG 2.4.9
Issue type:
needs review
Links with identical accessible names have equivalent purpose
This rule checks that links with identical accessible names resolve to the same resource or equivalent resources.
Content loading...
Autoren: Anne Thyme Nørregaard, Jean-Yves Moyen
Finanzierung: WAI-Tools
Applicability
This rule applies to any set of any two or more HTML or SVG elements for which all the following are true:
the elements are inheriting semanticlink nodes; and
the elements are in the same web page (HTML); and
the elements are included in an accessibility tree; and
the elements have matchingaccessible names that are not empty ("").
Note: The test target for this rule is the full set of link elements that share the same matchingaccessible name.
Expectation
When followed, the links in each set of target elements resolve to the same resource or to equivalent resources. Resolving the links includes potential redirects, if the redirects happen instantly.
Background
Assumptions
This rule assumes that the purpose of the links with identical accessible names would not be ambiguous to users in general when seen in context on the web page, which is the exception mentioned in Success Criterion 2.4.9 Link Purpose (Link Only). If the links are ambiguous to users in general, users of assistive technologies are not at a disadvantage when viewing the links out of context, e.g. on a list of links in a screen reader, which makes it more of a general user experience concern than an accessibility issue.
This rule assumes that, within the context of the test subject, the description provided by the accessible name of a link can only accurately describe one resource (notably, homonyms alone are not used as link names). Thus, if two or more links have the same accessible name but resolve to different resources, at least one of them does not describe its purpose.
Accessibility Support
This rule assumes that assistive technologies are exposing all links on the page in the same way no matter which document tree they are in. If an assistive technology requires the user to "enter" an iframe or a shadow tree before exposing its links, then it is possible for two links to have identical name but resolve to different resources without failing Success Criterion 2.4.9 Link Purpose (Link Only) (if said links are in separate documents or shadow trees).
Implementation of Presentational Roles Conflict Resolution varies from one browser or assistive technology to another. Depending on this, some inheriting semanticlink elements can fail this rule with some technology but users of other technologies would not experience any accessibility issue.
These two links resolve to resources that are not the same (different URLs), but the resources are completely identical, in this case the contact details being the same in two locations, thus serving the same purpose.
These two links go to pages where the content section is the same, but where the navigation options (bread crumbs and local sub menus) differ due to different placement in navigation hierarchy. In the example, the contact details are the same format but in different locations.
These two HTML a elements link to URLs that differ due to trailing slashes, but resolve to the same resource after redirects caused by user agent. The redirect means the URLs look different but load the same page.
These two links go to pages that contain different amounts of information and/or differently worded information, but fulfill the same purpose in relation to the link. In the example, the phone number is in the same format but in different locations.
These two links go to pages that have the same advertised key content but use different layouts. In the example, the contact details are the same format but in different locations.
These two HTML span element have an explicit role of link, and lead to the same resource. This example is showing ARIA markup for a link compared to the other HTML examples.
<htmllang="en"><spanrole="link"tabindex="0"onclick="location='/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index.html'"
>
Link text
</span><spanrole="link"tabindex="0"onclick="location='/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index.html'"
>
Link text
</span></html>
Passed Example 9
These two SVG a elements have the same accessible name and link to the same resource. The example is one SVG area but with 2 formats of links. One uses an image and the other uses text.
All three links have the same accessible name. The second link ("from the light") is only part of the light tree. When the shadow tree is attached to host and flattened, this link is overwritten and therefore not part of the flat tree (and thus not rendered). Hence, only the first and third link are considered by this rule and they both point to the same resource.
<ahref="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html">Contact us</a>
all the time.
<divid="host"><span
><ahref="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/admissions/contact.html"
>Contact us</a
>
from the light.</span
>
</div><script>const host = document.getElementById('host')
const shadowRoot = host.attachShadow({ mode: 'open' })
shadowRoot.innerHTML =
'<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html">Contact us</a> from the shadow.'</script>
<ahref="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html">Contact us</a>
from the top level.
<iframesrcdoc="<a href='/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html'>Contact us</a> from the iframe"
></iframe>
Failed
Failed Example 1
These two links have the same accessible name but go to different resources. They open completely different pages.
The same accessible name is used for two links going to web pages that are similar, but have different information in their content. The example given contains different contact details for each page. They have a similar purpose but do not match.
These two HTML span elements have an explicit role of link, but lead to resources that offer different content. The example given contains different contact details for each page. They have a similar purpose but do not match.
<htmllang="en"><spanrole="link"tabindex="0"onclick="location='/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html'"
>
Link text
</span><spanrole="link"tabindex="0"onclick="location='/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/admissions/contact.html'"
>
Link text
</span></html>
Failed Example 4
The same accessible name is used for image links going to different resources. They open completely different pages.
These span elements do not have a semantic role of link. They are not valid links.
<htmllang="en"><spanonclick="location='/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/page1.html'">
Contact Us
</span><spanonclick="location='/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/page2.html'">
Contact Us
</span></html>