Skip to main content

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

Adrian Roselli
Adrian Roselli
• •

I have filed a Chromium bug:
issues.chromium.org/issues/356…

If anyone here knows someone on the Chrome team, probably let them know their latest attempt to make scrolling areas focusable is not working for everyone.

#a11y #accessibility

Chromium

issues.chromium.org
#a11y #Accessibility
in reply to Adrian Roselli

victor tsaran
victor tsaran
• •
Thank you for doing all this investigative work. I passed the bug onto the team.
in reply to Adrian Roselli

Adrian Roselli
Adrian Roselli
• •

Updating this post with Chrome’s stutter-step release of this feature is becoming a part-time job:

adrianroselli.com/2022/06/keyb…


Keyboard-Only Scrolling Areas

I have spent a few years banging on about ensuring scrolling areas on a page are accessible to keyboard-only users.
Adrian Roselli
in reply to Adrian Roselli

Adrian Roselli
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

Adrian Roselli
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 Adrian Roselli

victor tsaran
victor tsaran
• •
Not sure what you are saying here. If it is rolling out as part of 127, and it is already available to 10%, then it will get to 100%, which will ultimately complete the 127 release. What am I missing? You can’t have a partial roll-out for one release and the rest in the next release.
in reply to victor tsaran

Adrian Roselli
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
in reply to Adrian Roselli

Adrian Roselli
Adrian Roselli
• •
@vick21 In other words, the post makes no mention of a partial release nor a rolling release.
@victor tsaran
in reply to Adrian Roselli

victor tsaran
victor tsaran
• •
Sorry, I am on all sorts of builds, but did the 127 release already rolled out completely? If not, then this is how Android / Chrome has always worked. The announcements are written with the complete roll-out in mind. I assume you have done your due diligence. I was just confused with the way your argument sounded to my ears.
in reply to victor tsaran

Adrian Roselli
Adrian Roselli
• •

@vick21 I guess I need to understand what a “complete roll-out” means.

Everyone who tested this for me was running a point release of 127. As far as I am concerned, that is a complete roll-out.

@victor tsaran
in reply to Adrian Roselli

victor tsaran
victor tsaran
• •
No, not really. Just because you have 127 on your computer does not mean everyone else has gotten it. It may take several days before most of the world gets the update. That’s how it always worked… There is probably a description of the process somewhere online. I know it puzzled me the first time I heard about the process.
⇧