mastodon - Link to source

Are you running Chrome 127 on Windows? I can use your help for a quick test.

1. Go to this URL:
cdpn.io/pen/debug/bGLrYBo

2. Zoom or resize so the table has a scrollbar at the bottom.

3. Without using your mouse, Tab to the table.

4. Use your arrow keys to scroll it left-right.

If it works, cool. If not, less cool. I have a case of someone where the keyboard scrollable containers feature added in Chrome 127 does not work.

CodePen - Caret Table

cdpn.io
in reply to Adrian Roselli

mastodon - Link to source

Adrian Roselli

If you read this from the Google Chrome Developer Blog, when do you expect this feature to be available?

Ref: developer.chrome.com/blog/new-…

#accessibility #a11y

Post title: “New in Chrome 127.” Index of topics in post shows “Keyboard focusable scroll containers.”
Heading: “Keyboard focusable scroll containers.” Circled in the second paragraph: “From now on scrollers are click-focusable and programmatically-focusable by default.”

New in Chrome 127  |  Blog  |  Chrome for Developers

Chrome 127 is rolling out now! With support for font-size-adjust, user activations propagated in the Document Picture-in-Picture API, keyboard focusable scroll containers and there's plenty more.
Chrome for Developers
#a11y #Accessibility
in reply to Adrian Roselli

mastodon - Link to source

Adrian Roselli

Confirmation that this feature is not really in 127:

“Currently, 10% of users see it. By 128, 100% of users should expect keyboard focusable scrollers to be enabled by default.”

“Because we need to be a bit nimble as we do that ramp-up, we didn't put all of the nitty gritty details of that ramp schedule into the blog post. But it's true that some people will see this feature enabled in M127, potentially up to a majority of users.”

So Chrome’s claim was 90% wrong.

toot.cafe/@aardrian/1128773450…

Adrian Roselli (@aardrian@toot.cafe)

I rather resent the fact that trillion dollar companies are relying on end users to perform #accessibility testing. Google, Microsoft (GitHub), Apple (Safari), Amazon, etc.
Toot Café
in reply to victor tsaran

mastodon - Link to source

Adrian Roselli

@vick21 “From now on scrollers are click-focusable and programmatically-focusable by default” is not the same as enabled for 10% of users today and then later up to 100%.

Given the feedback to the Chrome Developers blog post announcement language question that I asked here and elsewhere, I am not alone in thinking the feature was available for everyone.

@victor tsaran
⇧