Improves accessibility by making scroll containers focusable using sequential focus navigation by changing their default tabIndex value from -1 to 0. Today, the tab key doesn't focus scrollers unless tabIndex is explicitly set to 0 or more. By giving scrollers a default tabIndex of 0, users who can't (or don't want to) use a mouse will be able to focus clipped content using a keyboard's tab and arrow keys.



Established standard

Status in Chromium


In development (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.


Search tags

tab key, keyboard focus, sequential navigation,

Last updated on 2021-05-09