Assigned
Status Update
No update yet.
Comments
an...@google.com
Hi test team, this appears to be a regression, making it a good candidate for bisection to quickly identify the root cause. Please remove 'Needs-Bisect' hotlist and provide a rationale if bisection isn't applicable; this feedback will improve the automated system.
ss...@google.com
Tested the issue on chrome version #134.0.6998.45 using Mac 15.3.1 as per steps provided in
Steps to reproduce
================
1. Enable VoiceOver and Launched chrome
2. Navigate to given url (https://codesandbox.io/p/devbox/unruffled-dawn-83h9yv , https://83h9yv-5173.csb.app/ )
3. Navigate output console element and Tab on it
Observed it reads the following - "Action 1" --> "Action 2" --> "Card A action" --> "Card B action" --> "Card C action"
Note:
1. Observed same behaviour when KeyBoardFocusableScrollers(#keyboard-focusable-scrollers) is set to Enabled and Disabled
2. Same behaviour is seen for chrome older M123 build
3. In firefox browser it reads the following- "Action 1" --> "Action 2" --> "Card A title" --> "Card A action" --> "Card B action" --> "Card C action"
Looping awogbemila@ to CC list for further inputs on this issue
Reporter@ Could you please review above observations and attached screencast for reference and please let us know if we missed anything. Could you please confirm firefox bowser behaviour as good and chrome bowser behaviour as bad?
Attaching screencast for reference
Thanks..!!
Steps to reproduce
================
1. Enable VoiceOver and Launched chrome
2. Navigate to given url (
3. Navigate output console element and Tab on it
Observed it reads the following - "Action 1" --> "Action 2" --> "Card A action" --> "Card B action" --> "Card C action"
Note:
1. Observed same behaviour when KeyBoardFocusableScrollers(#keyboard-focusable-scrollers) is set to Enabled and Disabled
2. Same behaviour is seen for chrome older M123 build
3. In firefox browser it reads the following- "Action 1" --> "Action 2" --> "Card A title" --> "Card A action" --> "Card B action" --> "Card C action"
Looping awogbemila@ to CC list for further inputs on this issue
Reporter@ Could you please review above observations and attached screencast for reference and please let us know if we missed anything. Could you please confirm firefox bowser behaviour as good and chrome bowser behaviour as bad?
Attaching screencast for reference
Thanks..!!
pr...@sprinklr.com
Hi, as mentioned in step 2, to reproduce the issue you need to "Enable VoiceOver Quick Nav and use arrow keys to navigate the page".
It seems like the above observations are when "Tab key" is used to navigate instead of "Arrow keys", can you please recheck with arrow keys in quick nav mode?
It seems like the above observations are when "Tab key" is used to navigate instead of "Arrow keys", can you please recheck with arrow keys in quick nav mode?
pe...@google.com
Thank you for providing more feedback. Adding the requester to the CC list.
di...@chromium.org
di...@chromium.org
I tried to reproduce with VoiceOver on. To navigate to the buttons, I have to use the TAB key. They arrow keys don't navigate. Once the focus is on an element inside the scroller, than using the UP/DOWN keys will move the scroll bar only. The elements can only be focused using TAB. reporter@, can you expand on how you are navigating using arrow keys?
ka...@google.com
Gentle ping
Reporter@ Could you please provide your inputs as perc commen#7
Thanks..!!
Reporter@ Could you please provide your inputs as perc commen#7
Thanks..!!
Description
Steps to reproduce the problem
Problem Description
Expected behaviour is that VO should read out "Action 1" --> "Action 2" --> "Card A title" --> "Card A action" --> "Card B title" --> "Card B action" --> "Card C title" --> "Card C action" This is read correctly in Safari and Firefox. It also works on Chrome when KeyBoardFocusableScrollers is manually disabled.
With KeyBoardFocusableScrollers enabled it reads the following - "Action 1" --> "Action 2" --> "Card A title Card A action Card B title Card B action Card C title Card C action" --> (Does not enter the scroll container at all)
If an aria-label (let's say "Scroll container") is specified on the scroll container then it reads the following "Action 1" --> "Action 2" --> "Scroll container" --> "Card A title" --> "Card A action" --> "Card B title" --> "Card B action" --> "Card C title" --> "Card C action"
Summary
KeyBoardFocusableScrollers causing issues with VoiceOver
Custom Questions
Which component does this fall under?
Blink>Scroll
Does this work in other browsers?
Yes - This is just a Chrome problem
Additional Data
Category: API
Chrome Channel: Not sure
Regression: Yes