Skip to content

Proposed Scrollable content can be reached with sequential focus navigation

Description

This rule checks that scrollable elements or their descendants can be reached with sequential focus navigation so that they can be scrolled by keyboard

Applicability

This rule applies to any [HTML element][] that has [visible][] in the [flat tree][], and for which at least one of the following is true:

Expectation

For each target element, at least one of the following is true:

Background

To ensure there is some element from which arrow keys can be used to control the scroll position, focus must be on or in a scrollable region. If scripts are used to prevent the keyboard events from reaching the scrollable region, this could still cause a keyboard accessibility issue. This must be tested separately.

This rule only applies to elements who scroll content in the same document. Elements such as iframes that embed other documents may also be scrollable, but for them it is the embedded document that scrolls, not the content in the same document. Such scenarios are tested separately with rules such as Iframe with negative tabindex has no interactive elements.

Assumptions

This rule assumes that all [scrollable elements][scrollable] with visible content need to be keyboard accessible. [Scrollable elements][scrollable] that do not need to be keyboard accessible, perhaps because their content is [purely decorative][], the scroll area is whitespace, or because scroll can be controlled in some other keyboard accessible way such as through a button or custom scrollbar, may fail this rule but still satisfy [success criterion 2.1.1 Keyboard][].

Accessibility Support

Some browsers will automatically make any [scrollable element][scrollable] focusable to ensure keyboard accessibility. However, the browser does not include these elements in [sequential focus navigation][] when it has a negative number as a tabindex attribute value.

Some browsers restrict scrolling to the content box of elements; while others allow to scroll the full border box, hence including the element’s padding. This results in some elements being scrollable with a browser but not with another.

Other Resources

Accessibility Requirements Mapping

Input Aspects

The following aspects are required in using this rule.

Test Cases

Passed

Passed Example 1

Open in a new tab

This [scrollable][] section element is included in [sequential focus navigation][] because it has a tabindex attribute set to 0.

<section style="height: 100px; width: 500px; overflow: scroll;" tabindex="0">
	<h1>WCAG 2.1 Abstract</h1>
	<p>
		Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more
		accessible. Following these guidelines will make content more accessible to a wider range of people with
		disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement,
		speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities
		and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines
		address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines
		will also often make Web content more usable to users in general.
	</p>
</section>

Passed Example 2

Open in a new tab

This [scrollable][] section element contains a link that is included in [sequential focus navigation][].

<section style="height: 100px; width: 500px; overflow: scroll;">
	<h1>
		<a href="https://www.w3.org/TR/WCAG22/#abstract">
			WCAG 2.1 Abstract
		</a>
	</h1>
	<p>
		Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more
		accessible. Following these guidelines will make content more accessible to a wider range of people with
		disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement,
		speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities
		and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines
		address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines
		will also often make Web content more usable to users in general.
	</p>
</section>

Passed Example 3

Open in a new tab

This [scrollable][] section element is [inert][] because of the modal dialog, so neither the section nor its descendant elements are included in [sequential focus navigation][].

<style>
	dialog:-internal-dialog-in-top-layer::backdrop {
    		background: rgba(1, 1, 1, 0.8);
	}
</style>
<section style="height: 100px; width: 500px; overflow: scroll;" tabindex="0">
	<h1>WCAG 2.1 Abstract</h1>
	<p>
		Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more
		accessible. Following these guidelines will make content more accessible to a wider range of people with
		disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement,
		speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities
		and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines
		address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines
		will also often make Web content more usable to users in general.
		<button id="ppButton" onclick="openDialog()">Read more about WCAG 2.2</button>
	</p>
</section>
<dialog id="ppDialog" aria-labelledby="dialogLabel">
	<h2 id="dialogLabel">WCAG 2.2</h2>
	<p>
		<a href="https://www.w3.org/TR/WCAG22/">WCAG 2.2</a>
	</p>
	<button id="cancel" onclick="ppDialog.close()">Cancel</button>
</dialog>
<script>
	const openDialog = () => {
		ppDialog.showModal();
		myFrame.tabIndex = '-1'
	}
	ppDialog.addEventListener('close', () => myFrame.tabIndex = 0)
	window.addEventListener('DOMContentLoaded', openDialog);
</script>

Failed

Failed Example 1

Open in a new tab

This [vertically scrollable][scrollable] section element is not included in [sequential focus navigation][], nor does it have any descendants that are.

<section style="height: 100px; width: 500px; overflow-y: scroll">
	<h1>WCAG 2.1 Abstract</h1>
	<p>
		Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more
		accessible. Following these guidelines will make content more accessible to a wider range of people with
		disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement,
		speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities
		and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines
		address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines
		will also often make Web content more usable to users in general.
	</p>
</section>

Failed Example 2

Open in a new tab

This [horizontally scrollable][scrollable] section element is not included in [sequential focus navigation][], nor does it have any descendants that are.

<style>
	section {
		height: 100px;
		width: 400px;
		overflow-y: auto;
		white-space: nowrap;
	}
	section > img {
		display: inline-block;
		width: 80px;
	}
</style>
<h1>Our sponsors:</h1>
<section>
	<img src="/test-assets/shared/w3c-logo.png" alt="W3C" />
	<img src="/test-assets/shared/eu-logo.svg" alt="EU" />
	<img src="/test-assets/shared/w3c-logo.png" alt="W3C" />
	<img src="/test-assets/shared/eu-logo.svg" alt="EU" />
	<img src="/test-assets/shared/w3c-logo.png" alt="W3C" />
	<img src="/test-assets/shared/eu-logo.svg" alt="EU" />
	<img src="/test-assets/shared/w3c-logo.png" alt="W3C" />
</section>

Inapplicable

Inapplicable Example 1

Open in a new tab

This section element has a computed [overflow][] of visible. Because of this its [scroll distance][scrollable] will be 0, regardless of the element’s content.

<section style="height: 95px; width: 500px;">
	<h1>WCAG 2.1 Abstract</h1>
	<p>
		Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more
		accessible. Following these guidelines will make content more accessible to a wider range of people with
		disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement,
		speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities
		and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines
		address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines
		will also often make Web content more usable to users in general.
	</p>
</section>

Inapplicable Example 2

Open in a new tab

This section element has a [scroll distance][scrollable] of 0 in both directions.

<section style="height: 95px; width: 500px; overflow: auto;">
	<p>
		<a href="https://www.w3.org/TR/WCAG22/#abstract">
			WCAG 2.1 Abstract
		</a>
	</p>
</section>

Inapplicable Example 3

Open in a new tab

This section element is not [scrollable][] because it has a computed [overflow][] of hidden.

<h1>
	<a href="https://www.w3.org/TR/WCAG22/#abstract">
		WCAG 2.1 Abstract
	</a>
</h1>
<section style="height: 95px; width: 500px; overflow: hidden;">
	<p>
		Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more
		accessible. Following these guidelines will make content more accessible to a wider range of people with
		disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement,
		speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities
		and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines
		address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines
		will also often make Web content more usable to users in general.
	</p>
</section>

Inapplicable Example 4

Open in a new tab

This [scrollable][] section element has no [visible][] content.

<p>This is what a scrollbar looks like:</p>
<section style="height: 20px; width: 500px; overflow-x:scroll;">
	<div style="width: 1000px; height: 1px;"></div>
</section>

Inapplicable Example 5

Open in a new tab

This section element has a [horizontal scroll distance][scrollable] that is less than its horizontal [padding][], and [vertical scroll distance][scrollable] that is less than its vertical [padding][].

<section style="height: 210px; width: 530px; overflow: scroll; padding: 30px 0 30px 30px;">
	<div role="heading" aria-level="1">WCAG 2.1 Abstract</div>
	<div style="width: 520px">
		Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more
		accessible. Following these guidelines will make content more accessible to a wider range of people with
		disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement,
		speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities
		and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines
		address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines
		will also often make Web content more usable to users in general.
	</div>
</section>

Inapplicable Example 6

Open in a new tab

This iframe element is not a scrollable element, but instead contains a nested browsing context that is scrollable. These must be tested separately.

<iframe src="https://www.w3.org/TR/WCAG22/#abstract" width="500" height="200"></iframe>

Glossary

Attribute value

The attribute value of a content attribute set on an HTML element is the value that the attribute gets after being parsed and computed according to specifications. It may differ from the value that is actually written in the HTML code due to trimming whitespace or non-digits characters, default values, or case-insensitivity.

Some notable case of attribute value, among others:

This list is not exhaustive, and only serves as an illustration for some of the most common cases.

The attribute value of an [IDL attribute][] is the value returned on getting it. Note that when an [IDL attribute][] [reflects][reflect] a content attribute, they have the same attribute value.

Inert

An [HTML or SVG element][] is inert if:

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

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 five following types:

Note: A rule has one passed or failed outcome for every [test target][]. When a tester evaluates a test target it can also be reported as cantTell if the rule cannot be tested in its entirety. For example, when applicability was automated, but the expectations have to be evaluated manually.

When there are no test targets the rule has one inapplicable outcome. If the tester is unable to determine whether there are test targets there will be one cantTell outcome. And when no evaluation has occurred the test target has one untested outcome. This means that each [test subject][] always has one or more outcomes.

Outcomes used in ACT Rules can be expressed using the [outcome property][] of the [EARL10-Schema][earl10-schema].

Scrollable Elements

A scrollable element is an [element][] with a horizontal scroll distance or a vertical scroll distance greater than 0.

note: Elements such as iframe which can render a [nested browsing context][] are not scrollable elements. The scrollbars on some iframe elements come from the content inside the [nested browsing context][].

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.

Content is defined in WCAG.

For more details, see examples of visible.

[dom attribute value]][dom-attribute-value]: https://dom.spec.whatwg.org/#concept-attribute-value ‘DOM Specification of Attribute Value’ [earl10-schema]: https://www.w3.org/TR/act-rules-format-1.1/#biblio-earl10-schema [element]: https://dom.spec.whatwg.org/#element ‘DOM element, 2021/05/31’ [enumerated attributes]: https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#enumerated-attribute ‘HTML Specification of Enumerated Attribute’ [flat tree]: https://drafts.csswg.org/css-scoping/#flat-tree ‘CSS draft, flat tree, 2020/04/03’ [html aam]: https://www.w3.org/TR/html-aam-1.0/#html-attribute-state-and-property-mappings ‘Specification of HTML attributes value mapping to ARIA states and properties’ [html attribute value]: https://html.spec.whatwg.org/multipage/dom.html#attributes ‘HTML Specification of Attribute Value’ [html element]: #namespaced-element [html namespaces]: https://infra.spec.whatwg.org/#namespaces ‘HTML namespace, 2021/05/31’ [html or svg element]: #namespaced-element ‘Definition of HTML or SVG element’ [idl attribute]: https://heycam.github.io/webidl/#idl-attributes “Definition of Web IDL Attribute (Editor’s Draft)” [inert]: #inert ‘Definition of Inert’ [namespaceuri]: https://dom.spec.whatwg.org/#dom-element-namespaceuri ‘DOM Element namespaceURI, 2021/05/31’ [nested browsing context]: https://html.spec.whatwg.org/#nested-browsing-context ‘HTML nested browsing context, 2020/04/03’ [numbers]: https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#numbers ‘HTML Specification of Number Parsing’ [outcome property]: https://www.w3.org/TR/EARL10-Schema/#outcome [overflow-x]: https://www.w3.org/TR/css-overflow-3/#propdef-overflow-x ‘CSS Overflow working draft, overflow-x, 2020/04/03’ [overflow-y]: https://www.w3.org/TR/css-overflow-3/#propdef-overflow-y ‘CSS Overflow working draft, overflow-y, 2020/04/03’ [overflow]: https://www.w3.org/TR/CSS22/visufx.html#overflow [padding-bottom]: https://www.w3.org/TR/CSS22/box.html#propdef-padding-bottom [padding-left]: https://www.w3.org/TR/CSS22/box.html#propdef-padding-left [padding-right]: https://www.w3.org/TR/CSS22/box.html#propdef-padding-right [padding-top]: https://www.w3.org/TR/CSS22/box.html#propdef-padding-top [padding]: https://www.w3.org/TR/CSS22/box.html#propdef-padding [purely decorative]: https://www.w3.org/TR/WCAG22/#dfn-pure-decoration [reflect]: https://html.spec.whatwg.org/multipage/common-dom-interfaces.html#reflecting-content-attributes-in-idl-attributes ‘HTML specification of Reflecting Content Attributes in IDL Attributes’ [scrollable]: #scrollable-element [scrollheight]: https://www.w3.org/TR/cssom-view/#dom-element-scrollheight ‘CSS working draft, Element.clientHeight, 2020/04/03’ [scrollwidth]: https://www.w3.org/TR/cssom-view/#dom-element-scrollwidth ‘CSS working draft, Element.scrollHeight, 2020/04/03’ [sequential focus navigation]: https://html.spec.whatwg.org/multipage/interaction.html#sequential-focus-navigation ‘HTML sequential focus navigation, 2020/04/03’ [space separated]: https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#space-separated-tokens ‘HTML Specification of Space Separated Tokens’ [success criterion 2.1.1 keyboard]: https://www.w3.org/TR/WCAG22/#keyboard [test subject]: https://www.w3.org/TR/act-rules-format-1.1/#test-subject [test target]: https://www.w3.org/TR/act-rules-format/#test-target [visible]: #visible [wai-aria specification]: https://www.w3.org/TR/wai-aria-1.2/#propcharacteristic_value ‘WAI-ARIA Specification of States and Properties Value’

Rule Versions

  1. Proposed version, 30 August 2023 (compare)
  2. Latest version, 30 August 2023

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 Report
Axe DevTools Pro 4.37.1 Semi-automated tool Consistent Axe DevTools Pro Report
Axe-core 4.10.2 Automated tool Consistent Axe-core Report
QualWeb 3.0.0 Automated tool Consistent QualWeb Report
Total Validator (+Browser) 17.4.0 Automated tool Consistent Total Validator (+Browser) Report
UsableNet AQA - WCAG 2.2 AA Auto 2.5.1 Automated tool Consistent UsableNet AQA - WCAG 2.2 AA Auto Report
UsableNet AQA - WCAG 2.2 AA Semi-auto 2.5.1 Semi-automated tool Consistent UsableNet AQA - WCAG 2.2 AA Semi-auto Report
Webmate Accessibility Workbench Automated tool Consistent Webmate Accessibility Workbench Report
Back to Top

This is an unpublished draft preview that might include content that is not yet approved. The published website is at w3.org/WAI/.