1879516 - The "No Thanks" and "Keep closed" buttons are not scrolled into View when the user reaches them with Keyboard navigation

Status: RESOLVED WORKSFORME

(Firefox :: Shopping, defect)

Description

[Rares Doghi, Desktop QA]

Attachment: scrollintoView.mp4

Found in

• Nightly 124.0a1 (2024-02-07)

Affected versions

• Nightly 124.0a1 (2024-02-07)
• Beta 123.0b8

Affected platforms

• Windows

Preconditions:
Reach about:config and set the following prefs:
browser.shopping.experience2023.enabled, set to true (doubleclick)
browser.shopping.experience2023.optedIn, set to 1 (doubleclick, input ‘0’, hit enter)
browser.shopping.experience2023.autoOpen.enabled - true
browser.shopping.experience2023.autoOpen.userEnabled - true

Steps to reproduce

1. Reach https://www.amazon.com/Lufeiya-Computer-Drawers-Storage-Shelves/dp/B0CJ8PZB31/ref=sr_1_6?keywords=desk&qid=1707480103&sr=8-6&th=1
2. Trigger the Keep Closed ? message in the sidebar.
3. Use Shift + Tab in order to reach the No Thanks and Yes Keep Closed buttons.

Expected result

• The 2 buttons from the keep Closed message should be scrolled into view when the user reaches them using Keyboard navigation.

Actual result

• Without NVDA the user would have no idea that it actually focuses on both buttons when navigating with the keyboard Shift+Tab keys or just
  with the Tab key.

Regression range
Not a Regression

Comment 1

[Anna Yeddi [:ayeddi]]

Since sighted keyboard users without screen readers (i.e. users of switch devices or users of magnification software) would not be able to locate the focus and know, what is focused and what could be activated, plus it is not clear how to revert the action if they, in fact, activate either of buttons, I'm marking this bug as access-s2.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:jhirsch, could you consider increasing the severity?

For more information, please visit BugBot documentation.

Comment 3

[Niklas Baumgardner [:niklas]]

Rares, are you still able to reproduce this?
I just tested on Windows and was not able to reproduce.

Comment 4

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

I wasn't able to repro the bug on mac, either. Closing; feel free to open if this is still reproducible.

Comment 5

[Rares Doghi, Desktop QA]

I was able to reproduce this issue again today in our latest Nightly build, but not in Release or Beta, but now i can't reproduce this issue in nightly either.
I was able to get a screen recording but after using the same steps I cant reproduce it at all.

Comment 6

[Rares Doghi, Desktop QA]

Attachment: NightClosed.mp4