Proposed Bypass Blocks of Repeated Content
Description
This rule checks that each page has a mechanism to bypass repeated blocks of content.
Applicability
This rule applies to any HTML web page.
Expectation
For each test target, the outcome of at least one of the following rules is passed:
- Block of repeated content is collapsible; or
- Document has heading for non-repeated content; or
- Document has a landmark with non-repeated content; or
- Document has an instrument to move focus to non-repeated content.
Assumptions
- This rule assumes that the mean to bypass blocks is included in the content of the HTML web page. For example, server-side scripting, or a global “settings” page, can provide a functionality similar to Block of repeated content is collapsible by serving a modified version of the page; in which case this rule would fail but Success Criterion 2.4.1 Bypass blocks could nonetheless be satisfied.
- This rule assumes that
frame
andframeset
elements are not used, given that they are deprecated in HTML5. They can be used to organize content as per H70: Using frame elements to group blocks of repeated material and H64: Using the title attribute of the frame and iframe elements, in that case, this rule would fail but Success Criterion 2.4.1 Bypass blocks could nonetheless be satisfied. - This rule assumes that completely removing blocks of repeated content is sufficient to pass Success Criterion 2.4.1 Bypass blocks. However, providing an instrument to remove them without providing one to show them again is likely going to create other unrelated issues.
- This rule assumes that repeated content that is at the end of the page (and not followed any non-repeated content) can be bypassed by means provided by user agents (such as pressing the “End” key to scroll to the bottom of the page). Therefore, they do not need any other way of being bypassed and are ignored by this rule. If there isn’t a way to bypass them, this rule may pass while Success Criterion 2.4.1 Bypass blocks is not satisfied.
- This rule assumes that the language of each test target can be correctly determined (either programmatically or by analyzing the content), and sufficiently understood.
Accessibility Support
Techniques and solutions that identify blocks of content are sufficient ways of passing Success Criterion 2.4.1 Bypass blocks. They are, however, only beneficial for users who have ways of navigating with this information. For example, adding headings to a document will only help users who can “jump” from heading to heading (such a possibility can be provided by browsers, browsers plugins, screen readers, or other assistive technologies). Techniques and solutions based on links will benefit all users (for example, sighted keyboard users with no other assistive technology) and are therefore recommended.
If the instruments used to pass some of the atomic rules are not keyboard accessible, or not included in the accessibility tree, passing this rule can still leave many users without a way to bypass blocks of repeated content. WCAG’s definition of mechanism has a note saying that it “needs to meet all success criteria for the conformance level claimed”. This includes Success Criterion 2.1.1 Keyboard and Success Criterion 4.1.2 Name, Role, Value which are both at level A.
This rule only checks if there is a way to bypass at least one section of repeated content. On pages with several interleaved repeated and non-repeated content, this is not sufficient to satisfy Success Criterion 2.4.1 Bypass blocks. Checking for more sections to bypass was considered but rejected due to both the added complexity it would create, and the risk of failing on pages that might be correct.
Background
The instruments used to pass this rule (if any), must meet all level A Success Criteria in order to fully satisfy Success Criterion 2.4.1 Bypass Block. These extra requirements are left out of this rule, and should be tested separately.
Bibliography
- Understanding Success Criterion 2.4.1: Bypass Blocks
- Creating links to skip blocks of content:
- Grouping and identifying blocks of content:
To avoid using landmarks for the non-repeated content, which would satisfy Success Criterion 2.4.1 Bypass Block, this rule uses <div id="main">
in its test cases to indicate where non-repeating content exists. It is recommended to use the main
landmark instead. The aside
and nav
elements are each a block of repeated content due to the link inside the nav
element to a page with similar blocks of content.
Accessibility Requirements Mapping
2.4.1 Bypass Blocks (Level A)
- Learn more about 2.4.1 Bypass Blocks
- Required for conformance to WCAG 2.0 and later on level A and higher.
- 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
- Any
G1: Adding a link at the top of each page that goes directly to the main content area
- Learn more about technique G1
- Not required for conformance to any W3C accessibility recommendation.
- Outcome mapping:
- Any
failed
outcomes: technique is not satisfied - All
passed
outcomes: technique needs further testing - An
inapplicable
outcome: technique needs further testing
- Any
G123: Adding a link at the beginning of a block of repeated content to go to the end of the block
- Learn more about technique G123
- Not required for conformance to any W3C accessibility recommendation.
- Outcome mapping:
- Any
failed
outcomes: technique is not satisfied - All
passed
outcomes: technique needs further testing - An
inapplicable
outcome: technique needs further testing
- Any
G124: Adding links at the top of the page to each area of the content
- Learn more about technique G124
- Not required for conformance to any W3C accessibility recommendation.
- Outcome mapping:
- Any
failed
outcomes: technique is not satisfied - All
passed
outcomes: technique needs further testing - An
inapplicable
outcome: technique needs further testing
- Any
H69: Providing heading elements at the beginning of each section of content
- Learn more about technique H69
- Not required for conformance to any W3C accessibility recommendation.
- Outcome mapping:
- Any
failed
outcomes: technique is not satisfied - All
passed
outcomes: technique needs further testing - An
inapplicable
outcome: technique needs further testing
- Any
SCR28: Using an expandable and collapsible menu to bypass block of content
- Learn more about technique SCR28
- Not required for conformance to any W3C accessibility recommendation.
- Outcome mapping:
- Any
failed
outcomes: technique is not satisfied - All
passed
outcomes: technique needs further testing - An
inapplicable
outcome: technique needs further testing
- Any
Input Rules
Outcomes of the following rules are required as input for this rule.
- Document has heading for non-repeated content
- Document has a landmark with non-repeated content
- Block of repeated content is collapsible
- Document has an instrument to move focus to non-repeated content
Test Cases
Passed
Passed Example 1
This HTML web page is passing rule Block of repeated content is collapsible.
<html>
<head>
<script src="/test-assets/bypass-blocks-cf77f2/toggle-display.js"></script>
<title>The Three Kingdoms, Chapter 1</title>
</head>
<body>
<a href="#" onclick="toggleHidden('chapters-navigation')">Toggle table of content</a>
<nav id="chapters-navigation">
<ol>
<li><a>Chapter 1</a></li>
<li><a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Chapter 2</a></li>
</ol>
</nav>
<div id="main">
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
</div>
</body>
</html>
Passed Example 2
This HTML web page is passing rule Document has heading for non-repeated content.
<html>
<head>
<title>The Three Kingdoms, Chapter 1</title>
</head>
<body>
<nav id="chapters-navigation">
<ol>
<li><a>Chapter 1</a></li>
<li><a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Chapter 2</a></li>
</ol>
</nav>
<div id="main">
<h1>Three Heroes Swear Brotherhood at a Feast in the Peach Garden</h1>
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
</div>
</body>
</html>
Passed Example 3
This HTML web page is passing rule Document has a landmark with non-repeated content.
<html>
<head>
<title>The Three Kingdoms, Chapter 1</title>
</head>
<body>
<nav id="chapters-navigation">
<ol>
<li><a>Chapter 1</a></li>
<li><a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Chapter 2</a></li>
</ol>
</nav>
<main>
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
</main>
</body>
</html>
Passed Example 4
This HTML web page is passing rule Document has an instrument to move focus to non-repeated content.
<html lang="en">
<head>
<title>The Three Kingdoms, Chapter 1</title>
</head>
<body>
<a href="#main">Skip to main content</a>
<a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Read Chapter 2</a>
<aside id="about-book">
<p>The Romance of the Three Kingdoms is a 14th century historical novel.</p>
</aside>
<div id="main">
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
</div>
</body>
</html>
Passed Example 5
This HTML web page is passing rule Document has an instrument to move focus to non-repeated content.
<html lang="en">
<head>
<title>The Three Kingdoms, Chapter 1</title>
</head>
<body>
<nav id="local-navigation">
<a href="#bio-translator">Skip to translator's biography</a>
<a href="#about-book">Skip to information about the book</a>
<a href="#main">Skip to main content</a>
</nav>
<aside id="bio-translator">
<p>Yu Sumei is a professor of English at East China Normal University.</p>
</aside>
<aside id="about-book">
<p>The Romance of the Three Kingdoms is a 14th century historical novel.</p>
</aside>
<div id="main">
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
<a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Read Chapter 2</a>
</div>
</body>
</html>
Passed Example 6
This HTML web page is passing rule Document has an instrument to move focus to non-repeated content.
<html lang="en">
<head>
<title>The Three Kingdoms, Chapter 1</title>
</head>
<body>
<aside id="bio-translator">
<a href="#about-book">Skip to information about the book</a>
<p>Yu Sumei is a professor of English at East China Normal University.</p>
</aside>
<aside id="about-book">
<a href="#main">Skip to main content</a>
<p>The Romance of the Three Kingdoms is a 14th century historical novel.</p>
</aside>
<div id="main">
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
<a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Read Chapter 2</a>
</div>
</body>
</html>
Passed Example 7
This HTML web page is passing rule Block of repeated content is collapsible because it has no block of repeated content before non-repeated perceivable content. Note that this does not pass Technique SCR28: Using an expandable and collapsible menu to bypass block of content because the block of repeated content which is after the non-repeated content cannot be toggled.
<html lang="en">
<head>
<title>The Three Kingdoms, Chapter 1</title>
</head>
<body>
<div id="main">
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
</div>
<a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Read Chapter 2</a>
<aside id="about-book">
The Romance of the Three Kingdoms is a 14th century historical novel.
</aside>
</body>
</html>
Passed Example 8
This HTML web page is passing rule Document has an instrument to move focus to non-repeated content because the button is such an instrument. Note that it does not pass Technique G1: Adding a link at the top of each page that goes directly to the main content area nor Technique G123: Adding a link at the beginning of a block of repeated content to go to the end of the block because the instrument is a button, not a link.
<html lang="en">
<head>
<title>The Three Kingdoms, Chapter 1</title>
</head>
<body>
<button onclick="location.assign('#main')">Skip to main content</button>
<aside id="about-book">
<p>The Romance of the Three Kingdoms is a 14th century historical novel.</p>
</aside>
<div id="main">
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
<a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Read Chapter 2</a>
</div>
</body>
</html>
Passed Example 9
This HTML web page is passing rule Document has an instrument to move focus to non-repeated content because the link with target #brewitt-taylor
moves focus just before some non-repeated content after repeated content. Note that it does not necessarily pass Technique G124: Adding links at the top of the page to each area of the content because the <div id="main">
element is arguably a single “area of the content”, and the technique requires only one link per such area.
<html>
<head>
<title>Comparing translations of the Romance of the Three Kingdoms, Chapter one</title>
</head>
<body>
<nav id="local-navigation">
<a href="#local-navigation">Skip to local navigation</a>
<a href="#brewitt-taylor">Skip to Brewitt-Taylor's translation</a>
<a href="#roberts">Skip to Roberts' translation</a>
<a href="#yu">Skip to Yu's translation</a>
<a href="#about-book">Skip to information about the book</a>
</nav>
<aside id="about-book">
<p>The Romance of the Three Kingdoms is a 14th century historical novel.</p>
</aside>
<div id="main">
<p id="brewitt-taylor">
Three Heroes Swear Brotherhood in the Peach Garden (Translation by Charles Henry Brewitt-Taylor)
</p>
<p>
The world under heaven, after a long period of division, tends to unite; after a long period of union, tends to
divide.
</p>
<p id="roberts">Three Bold Spirits Plight Mutual Faith in the Peach Garden (Translation by Moss Roberts)</p>
<p>The empire, long divided, must unite; long united, must divide. Thus it has ever been.</p>
<p id="yu">Three Heroes Swear Brotherhood at a Feast in the Peach Garden (Translation by Yu Sumei)</p>
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
<a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Read Chapter 2</a>
</div>
</body>
</html>
Passed Example 10
This HTML web page is passing rule Document has an instrument to move focus to non-repeated content. Note that it does not necessarily pass Technique G124: Adding links at the top of the page to each area of the content because the both the nav
and aside
elements are arguably different “areas of the content”, and the technique requires exactly one link per such area.
<html lang="en">
<head>
<title>The Three Kingdoms, Chapter 1</title>
</head>
<body>
<nav id="local-navigation">
<a href="#local-navigation">Skip to local navigation</a>
<a href="#main">Skip to main content</a>
</nav>
<aside id="about-book">
<p>The Romance of the Three Kingdoms is a 14th century historical novel.</p>
</aside>
<div id="main">
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
<a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Read Chapter 2</a>
</div>
</body>
</html>
Passed Example 11
This HTML web page is passing rule Block of repeated content is collapsible. Note that it does not pass Technique SCR28: Using an expandable and collapsible menu to bypass block of content because the technique requires that the blocks can be toggled on and off, but here they can only be removed.
<html>
<head>
<script src="/test-assets/bypass-blocks-cf77f2/toggle-display.js"></script>
<title>The Three Kingdoms, Chapter 1</title>
</head>
<body>
<button onclick="hide('chapters-navigation')">Hide table of content</button>
<nav id="chapters-navigation">
<ol>
<li><a>Chapter 1</a></li>
<li><a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Chapter 2</a></li>
</ol>
</nav>
<div id="main">
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
</div>
</body>
</html>
Passed Example 12
This HTML web page is passing rule Document has an instrument to move focus to non-repeated content because the second link is such an instrument. Note that it does not pass Technique G1: Adding a link at the top of each page that goes directly to the main content area because the skip link is not the first focusable element on the page.
<html lang="en">
<head>
<title>The Three Kingdoms, Chapter 1</title>
</head>
<body>
<a href="https://act-rules.github.io/">ACT rules</a>
<a href="#main">Skip to main content</a>
<a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Read Chapter 2</a>
<aside id="about-book">
<p>The Romance of the Three Kingdoms is a 14th century historical novel.</p>
</aside>
<div id="main">
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
</div>
</body>
</html>
Failed
Failed Example 1
This HTML web page does not pass any of the input rules.
<html lang="en">
<head>
<title>The Three Kingdoms, Chapter 1</title>
</head>
<body>
<a href="/test-assets/bypass-blocks-cf77f2/chapter2.html">Read Chapter 2</a>
<aside id="about-book">
The Romance of the Three Kingdoms is a 14th century historical novel.
</aside>
<div id="main">
<strong style="font-size: 18pt">Three Heroes Swear Brotherhood at a Feast in the Peach Garden</strong>
<p>
Unity succeeds division and division follows unity. One is bound to be replaced by the other after a long span
of time.
</p>
</div>
</body>
</html>
Inapplicable
Inapplicable Example 1
This document is not an HTML web page.
<svg xmlns="http://www.w3.org/2000/svg">
<title>This is an SVG</title>
</svg>
Glossary
Block of content
A block of content in an HTML web page is a set of nodes from that page for which all the following are true:
- content: there is at least one node which is perceivable content in the block; and
- continuity: if two nodes are in the block, then any node between them (in tree order) is also in the block; and
- downward closure: if a node is in the block, then all its descendants are also in the block; and
- parent closure: if all children of a node are in the block, then this node is also in the block.
Block of repeated content
A block of content B, inside an HTML web page P, is a block of repeated content if both the following are true:
- distance 1: there exist an instrument in P which leads the user to another HTML web page P’ whose URL has a different host, port (including default port for special URL), or path; and
- repeated: there exist a block of content in P’ which is equivalent to B.
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.
Instrument to achieve an objective
An HTML element that when activated allows an end-user to achieve an objective.
Note: Any rule that uses this definition must provide an unambiguous description of the objective the instrument is used to achieve.
Just before a node
A node N is just before a node of perceivable content P if one of the following is true:
- N and P are the same node; or
- N is not perceivable content and there is no node of perceivable content between N and P (in tree order in the flat tree).
Several nodes may be just before a given node, especially if there are several non-perceivable content nodes next to each other.
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
orpresentation
; or - it is an
img
element with analt
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.
Non-repeated content after repeated content
A node is non-repeated content after repeated content if all the following are true:
- the node is perceivable content; and
- the node is not part of any block of repeated content; and
- the node is after (in tree order in the flat tree) at least one block of repeated content.
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.
Perceivable content
A node is perceivable content if all the following are true:
- the node is palpable content; and
- the node is either visible or included in the accessibility tree; and
- if the node is an element, it does not have a semantic role of
none
orpresentation
.
Perceivable content corresponds to nodes that contain information and are perceived by some categories of users.
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
ofnone
; or - has an
aria-hidden
attribute set totrue
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.
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
.
Visible
Content perceivable through sight.
Content is considered visible if making it fully transparent would result in a difference in the pixels rendered for any part of the document that is currently within the viewport or can be brought into the viewport via scrolling.
For more details, see examples of visible.
WAI-ARIA specifications
The WAI ARIA Specifications group both the WAI ARIA W3C Recommendation and ARIA modules, namely:
- Accessible Rich Internet Applications (WAI-ARIA) 1.1
- WAI-ARIA Graphics Module 1.0
- Digital Publishing WAI-ARIA Module 1.0
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.
Implementations
There are currently no known implementations for this rule. If you would like to contribute an implementation, please read the ACT Implementations page for details.
Changelog
This is the first version of this ACT rule.