Proposed Links with identical accessible names have equivalent purpose

Description

This rule checks that links with identical accessible names resolve to the same resource or equivalent resources.

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 semantic link nodes; and
the elements are in the same web page (HTML); and
the elements are included in an accessibility tree; and
the elements have matching accessible names that are not empty ("").

Note: The test target for this rule is the full set of link elements that share the same matching accessible 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.

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 semantic link elements can fail this rule with some technology but users of other technologies would not experience any accessibility issue.

Background

Bibliography

Accessibility Requirements Mapping

2.4.9 Link Purpose (Link Only) (Level AAA)
- Learn more about 2.4.9 Link Purpose (Link Only)
- Required for conformance to WCAG 2.0 and later on level AAA.
- Outcome mapping:
  - Any failed outcomes: success criterion is not satisfied
  - All passed outcomes: success criterion needs further testing
  - An inapplicable outcome: success criterion needs further testing

Input Aspects

The following aspects are required in using this rule.

Test Cases

These HTML files are used in several examples:

File /test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index.html:

<!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="utf-8" />
		<title>My University</title>
	</head>
	<body>
		<h1>Welcome to My University</h1>
		<p>We are currently working on getting our website up and running.</p>
	</body>
</html>

File /test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/redirect.html:

<!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="utf-8" />
		<meta http-equiv="refresh" content="0; URL='index.html'" />
		<title>Redirecting to another page</title>
	</head>
	<body></body>
</html>

File /test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index-copy.html:

<!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="utf-8" />
		<title>My University</title>
	</head>
	<body>
		<h1>Welcome to My University</h1>
		<p>We are currently working on getting our website up and running.</p>
	</body>
</html>

File /test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html:

<!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="utf-8" />
		<title>About - Contact</title>
	</head>
	<body>
		<nav label="main menu" style="text-align: right;">
			<a href="../about.html">About</a>
			<a href="../admissions.html">Admissions</a>
			<a href="../careers.html">Careers</a>
		</nav>
		<nav label="breadcrumb">
			<p>You are here: <a href="../about.html">About</a> / Contact us</p>
		</nav>
		<nav label="submenu" style="float:left">
			<h2>About</h2>
			<ul>
				<li style="list-style-type: none;"><a href="history.html">History</a></li>
				<li style="list-style-type: none;"><a href="employees.html">Employees</a></li>
				<li style="list-style-type: none;"><a href="contact.html">Contact</a></li>
			</ul>
		</nav>
		<main style="float:left; margin-left: 50px;">
			<h1>Contact us</h1>
			<p>Phone: (541) 754-3010</p>
		</main>
	</body>
</html>

File /test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/careers/contact.html:

<!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="utf-8" />
		<title>About - Contact</title>
	</head>
	<body>
		<nav label="main menu" style="text-align: right;">
			<a href="../about.html">About</a>
			<a href="../admissions.html">Admissions</a>
			<a href="../careers.html">Careers</a>
		</nav>
		<nav label="breadcrumb">
			<p>You are here: <a href="../careers.html">Careers</a> / Contact</p>
		</nav>
		<nav label="submenu" style="float:left">
			<h2>Careers</h2>
			<ul>
				<li style="list-style-type: none;"><a href="positions.html">Open positions</a></li>
				<li style="list-style-type: none;"><a href="benefits.html">Benefits</a></li>
				<li style="list-style-type: none;"><a href="contact.html">Contact</a></li>
			</ul>
		</nav>
		<main style="float:left; margin-left: 50px;">
			<h1>Contact us</h1>
			<p>Phone: (541) 754-3010</p>
		</main>
	</body>
</html>

File /test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/page1.html:

<!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="utf-8" />
		<title>Get in touch</title>
	</head>
	<body>
		<h1>Get in touch</h1>
		<p>Call us: (541) 754-3010</p>
	</body>
</html>

File /test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/page2.html:

<!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="utf-8" />
		<title>Contact us</title>
	</head>
	<body>
		<h1>Contact us</h1>
		<p>Phone: (541) 754-3010</p>
		<p>Email: email@university.com</p>
		<p>Telefax: (541) 754-3011</p>
	</body>
</html>

File /test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/page3.html:

<html lang="en">
	<head>
		<meta charset="utf-8" />
		<title>Get in touch</title>
	</head>
	<body style="background-color: blue; color: yellow">
		<h1 style="border: 1px solid yellow">Get in touch</h1>
		<p>Call us: (541) 754-3010</p>
	</body>
</html>

File /test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/admissions/contact.html:

<!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="utf-8" />
		<title>About - Contact</title>
	</head>
	<body>
		<nav label="main menu" style="text-align: right;">
			<a href="../about.html">About</a>
			<a href="../admissions.html">Admissions</a>
			<a href="../careers.html">Careers</a>
		</nav>
		<nav label="breadcrumb">
			<p>You are here: <a href="../admissions.html">Admissions</a> / Contact</p>
		</nav>
		<nav label="submenu" style="float:left">
			<h2>Admissions</h2>
			<ul>
				<li style="list-style-type: none;"><a href="positions.html">Visit</a></li>
				<li style="list-style-type: none;"><a href="benefits.html">Dates</a></li>
				<li style="list-style-type: none;"><a href="contact.html">Contact</a></li>
			</ul>
		</nav>
		<main style="float:left; margin-left: 50px;">
			<h1>Contact us</h1>
			<p>Phone: (541) 754-3011</p>
		</main>
	</body>
</html>

File /test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/redirect1.html:

<!DOCTYPE html>
<html lang="en">
	<head>
		<meta charset="utf-8" />
		<meta http-equiv="refresh" content="30; URL='index.html'" />
		<title>Redirecting to another page</title>
	</head>
	<body></body>
</html>

Passed

Passed Example 1

Open in a new tab

A set of two HTML a elements have the same accessible name and link to the same resource.

<html lang="en">
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index.html">Contact us</a>
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index.html">Contact us</a>
</html>

Passed Example 2

Open in a new tab

These two HTML a elements resolve to the same resource after instant redirect. The redirect means that the URLs look different but load the same page.

<html lang="en">
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index.html">Contact us</a>
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/redirect.html">Contact us</a>
</html>

Passed Example 3

Open in a new tab

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.

<html lang="en">
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index.html">Contact us</a>
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index-copy.html">Contact us</a>
</html>

Passed Example 4

Open in a new tab

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.

<html lang="en">
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html">Contact us</a>
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/careers/contact.html">Contact us</a>
</html>

Passed Example 5

Open in a new tab

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.

<html lang="en">
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/">Contact us</a>
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66">Contact us</a>
</html>

Passed Example 6

Open in a new tab

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.

<html lang="en">
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/page1.html">Call us</a>
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/page2.html">Call us</a>
</html>

Passed Example 7

Open in a new tab

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.

<html lang="en">
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/page1.html">Contact us</a>
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/page3.html">Contact us</a>
</html>

Passed Example 8

Open in a new tab

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.

<html lang="en">
	<span
		role="link"
		tabindex="0"
		onclick="location='/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index.html'"
	>
		Link text
	</span>

	<span
		role="link"
		tabindex="0"
		onclick="location='/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index.html'"
	>
		Link text
	</span>
</html>

Passed Example 9

Open in a new tab

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.

<html lang="en">
	<svg viewBox="0 0 100 100" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
		<a href="https://act-rules.github.io/" aria-label="ACT rules">
			<circle cx="50" cy="40" r="35" />
		</a>

		<a href="https://act-rules.github.io/">
			<text x="50" y="90" text-anchor="middle">
				ACT rules
			</text>
		</a>
	</svg>
</html>

Passed Example 10

Open in a new tab

A set of one SVG a element and one HTML a element that have the same accessible name and link to the same resource.

<a href="https://act-rules.github.io/">ACT rules</a>

<svg viewBox="0 0 100 100" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
	<a href="https://act-rules.github.io/" aria-label="ACT rules">
		<circle cx="50" cy="40" r="35" />
	</a>
</svg>

Passed Example 11

Open in a new tab

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.

<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html">Contact us</a>
all the time.

<div id="host">
	<span
		><a href="/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>

Passed Example 12

Open in a new tab

The browsing context of the iframe has the browsing context of the main document as an ancestor browsing context. Hence, they share the same top-level browsing context (namely, the browsing context of the main document) and are part of the same web page (HTML). Therefore, both links are considered and, since they refer to the same document, the rule passes.

<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html">Contact us</a>
from the top level.

<iframe
	srcdoc="<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

Open in a new tab

These two links have the same accessible name but go to different resources. They open completely different pages.

<html lang="en">
	<a href="https://act-rules.github.io/">ACT rules</a>
	<a href="https://www.w3.org/community/act-r/">ACT rules</a>
</html>

Failed Example 2

Open in a new tab

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.

<html lang="en">
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html">Contact us</a>
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/admissions/contact.html"
		>Contact us</a
	>
</html>

Failed Example 3

Open in a new tab

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.

<html lang="en">
	<span
		role="link"
		tabindex="0"
		onclick="location='/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html'"
	>
		Link text
	</span>

	<span
		role="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

Open in a new tab

The same accessible name is used for image links going to different resources. They open completely different pages.

<html lang="en">
	<a href="https://act-rules.github.io/"><img src="/test-assets/shared/act-logo.png" alt="ACT rules"/></a>
	<a href="https://www.w3.org/community/act-r/"><img src="/test-assets/shared/act-logo.png" alt="ACT rules"/></a>
</html>

Failed Example 5

Open in a new tab

These two SVG a elements have the same accessible name but link to different resources. They open completely different pages.

<html lang="en">
	<svg viewBox="0 0 100 100" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
		<a href="https://act-rules.github.io/" aria-label="ACT rules">
			<circle cx="50" cy="40" r="35" />
		</a>

		<a href="https://www.w3.org/community/act-r/">
			<text x="50" y="90" text-anchor="middle">
				ACT rules
			</text>
		</a>
	</svg>
</html>

Failed Example 6

Open in a new tab

These two links resolve to same resource after redirect, but the redirect is not instant. The user will notice the redirect due to a pause.

<html lang="en">
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/index.html">Contact us</a>
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/redirect1.html">Contact us</a>
</html>

Inapplicable

Inapplicable Example 1

Open in a new tab

These a and area elements have no href attribute. Thus they are not links and do not have a role of link.

<html lang="en">
	<a>Link text</a>
	<area aria-label="Link text" />
</html>

Inapplicable Example 2

Open in a new tab

These links have different accessible names. The rule only applies to identical accessible names, not to identical link destinations.

Note: It is a best practice for Success Criterion 2.4.9: Link Purpose (Link Only) that identical links have identical accessible names. This is however not a requirement.

<html lang="en">
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html">Reach out</a>
	<a href="/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/about/contact.html">Contact us</a>
</html>

Inapplicable Example 3

Open in a new tab

These span elements do not have a semantic role of link. They are not valid links.

<html lang="en">
	<span onclick="location='/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/page1.html'">
		Contact Us
	</span>

	<span onclick="location='/test-assets/links-with-identical-names-serve-equivalent-purpose-b20e66/page2.html'">
		Contact Us
	</span>
</html>

Glossary

Accessible Name

The accessible name is the programmatically determined name of a user interface element that is included in the accessibility tree.

The accessible name is calculated using the accessible name and description computation.

For native markup languages, such as HTML and SVG, additional information on how to calculate the accessible name can be found in HTML Accessibility API Mappings 1.0, Accessible Name and Description Computation (working draft) and SVG Accessibility API Mappings, Name and Description (working draft).

For more details, see examples of accessible name.

Note: As per the accessible name and description computation, each element always has an accessible name. When no accessible name is provided, the element will nonetheless be assigned an empty ("") one.

Note: As per the accessible name and description computation, accessible names are flat string trimmed of leading and trailing whitespace. Notably, it is not possible for a non-empty accessible name to be composed only of whitespace since these must be trimmed.

Equivalent resource

Non-identical resources can still be equivalent resources by equally complying to the expectation formed by the user when navigating to them, thus serving an equivalent purpose. This would usually involve that the advertised key content is the same.

Web pages and documents (e.g. PDFs, office formats etc.) may be equivalent resources, even if the resources:

are located on different URLs, including different domains
present different navigation options, e.g. through bread crumbs or local sub menus
contain different amounts of information and/or differently worded information
use different layouts.

If all resources cover the user’s expectations equally well, the resources are considered to be equivalent.

Note: The user’s expectations for the resource can be formed by different things, e.g. the name of the link leading to the resource, with or without the context around the link. This depends on the accessibility requirement that is tested.

Note: If the same content is presented in different formats or languages, the format or language itself is often part of the purpose of the content, e.g. an article as both HTML and PDF, an image in different sizes, or an article in two different languages. If getting the same content in different formats or languages is the purpose of having separate links, the resources are not equivalent.

Explicit Semantic Role

The explicit semantic role of an element is determined by its role attribute (if any).

The role attribute takes a list of tokens. The explicit semantic role is the first valid role in this list. The valid roles are all non-abstract roles from WAI-ARIA Specifications. If the element has no role attribute, or if it has one with no valid role, then this element has no explicit semantic role.

Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the accessibility support base line. For the purposes of executing test cases in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support.

Focusable

An element is focusable if one or both of the following are true:

the element is part of sequential focus navigation; or
the element has a tabindex value that is not null.

Exception: Elements that lose focus during a period of up to 1 second after gaining focus, without the user interacting with the page the element is on, are not considered focusable.

Notes:

The 1 second time span is an arbitrary limit which is not included in WCAG. Given that scripts can manage the focus state of elements, testing the focusability of an element consistently would be impractical without a time limit.
The tabindex value of an element is the value of the tabindex attribute parsed using the rules for parsing integers. For the tabindex value to be different from null, it needs to be parsed without errors.

Implicit Semantic Role

The implicit semantic role of an element is a pre-defined value given by the host language which depends on the element and its ancestors.

Implicit roles for HTML and SVG, are documented in the HTML accessibility API mappings (working draft) and the SVG accessibility API mappings (working draft).

Included in the accessibility tree

Elements included in the accessibility tree of platform specific accessibility APIs are exposed to assistive technologies. This allows users of assistive technology to access the elements in a way that meets the requirements of the individual user.

The general rules for when elements are included in the accessibility tree are defined in the core accessibility API mappings. For native markup languages, such as HTML and SVG, additional rules for when elements are included in the accessibility tree can be found in the HTML accessibility API mappings (working draft) and the SVG accessibility API mappings (working draft).

For more details, see examples of included in the accessibility tree.

Programmatically hidden elements are removed from the accessibility tree. However, some browsers will leave focusable elements with an aria-hidden attribute set to true in the accessibility tree. Because they are hidden, these elements are considered not included in the accessibility tree. This may cause confusion for users of assistive technologies because they may still be able to interact with these focusable elements using sequential keyboard navigation, even though the element should not be included in the accessibility tree.

Inheriting Semantic Role

An element with an inheriting semantic role of X is any element with a non-abstract semantic role that inherits from X, or is the same as X.

Example: An “inheriting semantic link” is any element that either has the semantic role of link or a semantic role that inherits from the link role, such as doc-biblioref.

Marked as decorative

An element is marked as decorative if one or more of the following conditions is true:

it has an explicit role of none or presentation; or
it is an img element with an alt attribute whose value is the empty string (alt=""), and with no explicit role.

Elements are marked as decorative as a way to convey the intention of the author that they are pure decoration. It is different from the element actually being pure decoration as authors may make mistakes. It is different from the element being effectively ignored by assistive technologies as rules such as presentational roles conflict resolution may overwrite this intention.

Elements can also be ignored by assistive technologies if they are programmatically hidden. This is different from marking the element as decorative and does not convey the same intention. Notably, being programmatically hidden may change as users interact with the page (showing and hiding elements) while being marked as decorative should stay the same through all states of the page.

Matching characters

A sequence of characters is considered to match another if, after removing leading and trailing space characters and replacing remaining occurrences of one or more space characters with a single space, the two sequences of characters are equal character-by-character, ignoring any differences in letter casing.

Namespaced Element

An element with a specific namespaceURI value from HTML namespaces. For example an “SVG element” is any element with the “SVG namespace”, which is http://www.w3.org/2000/svg.

Namespaced elements are not limited to elements described in a specification. They also include custom elements. Elements such as a and title have a different namespace depending on where they are used. For example a title in an HTML page usually has the HTML namespace. When used in an svg element, a title element has the SVG namespace instead.

Outcome

An outcome is a conclusion that comes from evaluating an ACT Rule on a test subject or one of its constituent test target. An outcome can be one of the three following types:

Inapplicable: No part of the test subject matches the applicability
Passed: A test target meets all expectations
Failed: A test target does not meet all expectations

Note: A rule has one passed or failed outcome for every test target. When there are no test targets the rule has one inapplicable outcome. This means that each test subject will have one or more outcomes.

Note: Implementations using the EARL10-Schema can express the outcome with the outcome property. In addition to passed, failed and inapplicable, EARL 1.0 also defined an incomplete outcome. While this cannot be the outcome of an ACT Rule when applied in its entirety, it often happens that rules are only partially evaluated. For example, when applicability was automated, but the expectations have to be evaluated manually. Such “interim” results can be expressed with the incomplete outcome.

Programmatically Hidden

An HTML element is programmatically hidden if either it has a computed CSS property visibility whose value is not visible; or at least one of the following is true for any of its inclusive ancestors in the flat tree:

has a computed CSS property display of none; or
has an aria-hidden attribute set to true

Note: Contrary to the other conditions, the visibility CSS property may be reverted by descendants.

Note: The HTML standard suggests setting the CSS display property to none for elements with the hidden attribute. While not required by HTML, all modern browsers follow this suggestion. Because of this the hidden attribute is not used in this definition. In browsers that use this suggestion, overriding the CSS display property can reveal elements with the hidden attribute.

Same resource

Two or more resources can be the same resource even though the URLs for them are different. This can be due to URL parsing, server settings, redirects and DNS aliasing.

If the parsed URLs for two resources are identical, the resources are the same resource.

Depending on the server, URLs can either be case-sensitive or case-insensitive, meaning that <a href="page1.html"> and <a href="Page1.html"> lead to either the same or two different pages.

Fully parsed URLs can be different, but still lead to the same resource after making the HTTP request, due to redirects and DNS aliasing. For example, these URLs are all fully normalized: http://example.com/, http://www.example.com/, https://www.example.com/. The server can however be configured to serve the same site for http and https, and the same site for example.com and www.example.com. This is common, but not guaranteed.

Some types of redirects are also caused by user agents, e.g. ensuring that http://example.com/ and http://example.com resolve to the same resource.

On the other hand, identical relative URLs do not necessarily resolve to the same resource, even if they are in the same web page (HTML). This happen because external content can be included through iframe and URLs in or out of it will resolve relatively to different base URLs.

Semantic Role

The semantic role of an element is determined by the first of these cases that applies:

Conflict If the element is marked as decorative, but the element is included in the accessibility tree; or would be included in the accessibility tree when it is not programmatically hidden, then its semantic role is its implicit role.
Explicit If the element has an explicit role, then its semantic role is its explicit role.
Implicit The semantic role of the element is its implicit role.

This definition can be used in expressions such as “semantic button” meaning any element with a semantic role of button.

WAI-ARIA specifications

The WAI ARIA Specifications group both the WAI ARIA W3C Recommendation and ARIA modules, namely:

Note: depending on the type of content being evaluated, part of the specifications might be irrelevant and should be ignored.

Web page (HTML)

An HTML web page is the set of all fully active documents which share the same top-level browsing context.

Note: Nesting of browsing context mostly happens with iframe and object. Thus a web page will most of the time be a “top-level” document and all its iframe and object (recursively).

Note: Web pages as defined by WCAG are not restricted to the HTML technology but can also include, e.g., PDF or DOCX documents.

Note: Although web pages as defined here are sets of documents (and do not contain other kind of nodes), one can abusively write that any node is “in a web page” if it is a shadow-including descendant of a document that is part of that web page.

Rule Versions

This is the first version of this ACT rule.

Implementations

This section is not part of the official rule. It is populated dynamically and not accounted for in the change history or the last modified date.

Implementation	Type	Consistency
Alfa (fully automated) 0.57.2	Automated tool	Partial
Alfa (semi-automated) 0.57.2	Semi-automated tool	Consistent
Axe DevTools Pro 4.37.1	Semi-automated tool	Partial
Axe-core 4.8.1	Automated tool	Partial
QualWeb 3.0.0	Automated tool	Partial

Description

Applicability

Expectation

Assumptions

Accessibility Support

Background

Bibliography

Accessibility Requirements Mapping

Input Aspects

Test Cases

Passed

Passed Example 1

Passed Example 2

Passed Example 3

Passed Example 4

Passed Example 5

Passed Example 6

Passed Example 7

Passed Example 8

Passed Example 9

Passed Example 10

Passed Example 11

Passed Example 12

Failed

Failed Example 1

Failed Example 2

Failed Example 3

Failed Example 4

Failed Example 5

Failed Example 6

Inapplicable

Inapplicable Example 1

Inapplicable Example 2

Inapplicable Example 3

Glossary

Accessible Name

Equivalent resource

Explicit Semantic Role

Focusable

Implicit Semantic Role

Included in the accessibility tree

Inheriting Semantic Role

Marked as decorative

Matching characters

Namespaced Element

Outcome

Programmatically Hidden

Same resource

Semantic Role

WAI-ARIA specifications

Web page (HTML)

Rule Versions

Implementations

Useful Links