#OVERFLOW SCROLLING FULL#

Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content moreĪccessible. This scrollable section element is included in sequential focus navigation because it has a tabindex attribute set to 0. The following aspects are required in using this rule.

An inapplicable outcome: technique needs further testing.

All passed outcomes: technique needs further testing.

Any failed outcomes: technique is not satisfied.

Not required for conformance to any W3C accessibility recommendation.

Required for conformance to WCAG 2.0 and later on level AAA.

Learn more about 2.1.3 Keyboard (No Exception).

2.1.3 Keyboard (No Exception) (Level AAA).

An inapplicable outcome: success criterion needs further testing.

All passed outcomes: success criterion needs further testing.

Any failed outcomes: success criterion is not satisfied.

Required for conformance to WCAG 2.0 and later on level A and higher.

G202: Ensuring keyboard control for all functionality.

Understanding Success Criterion 2.1.1: Keyboard.

If scripts are used to prevent the keyboard events from reaching the scrollable region, this could still cause a keyboard accessibility issue. 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. This results in some elements being scrollable with a browser but not with another.

#OVERFLOW SCROLLING FULL#

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. 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 will automatically make any scrollable element focusable to ensure keyboard accessibility. Scrollable elements 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. This rule assumes that all scrollable elements with visible content need to be keyboard accessible.

It has a vertical scroll distance greater than the computed top or bottom padding of the elementĮach test target is either included in sequential focus navigation or has a descendant in the flat tree that is included in sequential focus navigation.It has a horizontal scroll distance greater than the computed left or right padding of the element or.

This rule applies to any HTML element that has visible children in the flat tree for which at least one of the following is true: This rule checks that scrollable elements can be scrolled by keyboard Applicability 2.1.3: Keyboard (No Exception) (Level AAA) Description

Overflow scrolling