the tab key doesn't focus scrollers unless they explicitly got tabIndex >= 0. By giving scrollers a default tabIndex of 0, users who can't (or doesn't want to) use a mouse will be able to focus and read clipped content by using a keyboard's tab and arrow keys.
Link to “Intent to Implement” blink-dev discussion
None. Already implemented. The code change is small.
Link to Origin Trial feedback summaryNone.
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
See the CL's test.
Edge: No signals
Firefox: Shipped (a long time ago)
Safari: No signals
Web developers: Positive signals
Affects the tab order of documents that have overflow: scroll|auto-elements that contain clipped content.
Web pages developed with [keyboard] accessibility in mind already work around this difference to Firefox by manually overriding Chrome's default (tabIndex=-1) with tabIndex=0 on scrollers.
Web pages not developed with [keyboard] accessibility in mind will immediately become more accessible to users who cannot, or doesn't want to, use a mouse.
Is this feature fully tested by web-platform-tests?
The CL has wtp-like tests that we can upstream once testharness.js gets a browser-independent way to trigger sequential navigation.
Entry on the feature dashboard
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f46d0d9d-9f3a-4377-9d1f-b0a0f4b92eba%40chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAO_N0jea9x3aU3u6MxWZC5xrzjb_5thiD7A6ZJ2g8eezM3-HVA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/op.zr1yzqd3rbppqq%40cicero2.linkoping.osa.