Skip to content

"Links with identical accessible names and context serve equivalent purpose" [fd3a94]: precise that the rule only looks for "same" context #1864

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 30, 2022
Merged

"Links with identical accessible names and context serve equivalent purpose" [fd3a94]: precise that the rule only looks for "same" context #1864

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
75e9687
Precise that contexts have to be the same elements
Jym77 Jun 16, 2022
d1213a1
Merge branch 'develop' into link-context-same
Jym77 Jun 23, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions _rules/links-with-identical-names-and-context-serve-equivalent-purpose-fd3a94.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
id: fd3a94
name: Links with identical accessible names and context serve equivalent purpose
name: Links with identical accessible names and same context serve equivalent purpose
rule_type: atomic
description: |
This rule checks that links with identical accessible names and context resolve to the same or equivalent resources.
This rule checks that links with identical accessible names in the same context resolve to the same or equivalent resources.
accessibility_requirements:
wcag20:2.4.4: # Link Purpose (In Context) (A)
forConformance: true
Expand Down Expand Up @@ -66,6 +66,8 @@ _There are no major accessibility support issues known for this rule._

This rule is designed specifically for [2.4.4 Link Purpose (In Context)][sc244], which requires the purpose to be clear within the context of a link. Because links that do not have this, also are not clear without that context, this rule maps to [2.4.9 Link Purpose (Link only)][sc249] as well. In order to adequately test the [expectation](#expectation), some of the passed examples do not satisfy [2.4.9 Link Purpose (Link only)][sc249].

This rule specifically targets links within the exact same context. Links with identical name that are in identical (but not the same) contexts also fail [2.4.4 Link Purpose (In Context)][sc244]. However, defining "identical context" unambiguously was not really possible and was left out of this rule.

### Bibliography

- [Understanding Success Criterion 2.4.4: Link Purpose (In Context)](https://www.w3.org/WAI/WCAG21/Understanding/link-purpose-in-context.html)
Expand Down Expand Up @@ -372,7 +374,7 @@ These two `span` elements do not have a [semantic role][] of link.

#### Inapplicable Example 5

These two HTML `a` elements have the same [accessible name][] and link to the [same resource][] but different [programmatically determined link contexts][programmatically determined link context].
These two HTML `a` elements have the same [accessible name][] and link to the [same resource][] but different [programmatically determined link contexts][programmatically determined link context]. Even if the contexts have identical content, they are not the same (the same elements).

```html
<html lang="en">
Expand All @@ -381,7 +383,7 @@ These two HTML `a` elements have the same [accessible name][] and link to the [s
<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index.html">Contact us</a> page.
</div>
<div>
You can find contact information in the
You can learn more in the
<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index.html">Contact us</a> page.
</div>
</html>
Expand Down