Keyboard Navigation stops working when reaching a Product details page on Amazon
Categories
(Core :: Layout, defect)
Tracking
()
Accessibility Severity | s2 |
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox118 | --- | unaffected |
firefox119 | --- | wontfix |
firefox120 | --- | wontfix |
People
(Reporter: rdoghi, Unassigned)
References
(Regression)
Details
(Keywords: access, regression)
Attachments
(3 files)
Found in
- Nightly 120.0a1 (2023-10-11)
Affected versions
- Nightly 120.0a1 (2023-10-11)
- Beta 119.0b7
Affected platforms
- Windows
Steps to reproduce
- Reach amazon.com.
- Search for a Desk.
- Click the First product in order to reach the Product details page.
- Wait for the page to load.
- Use F6 in order to switch focus to address bar.
Expected result
- The user should be able to switch focus to the Address bar with F6.
The user should be able to reach any items with the TAB key
Actual result
- After the Page loads the F6 button loses functionality.
Clicking inside the page content and then using the tab key has some form of keyboard navigation but is not the normal highlighted navigation we see when the bug does not occur.
Regression range
13:51.97 INFO: Last good revision: 7b7144975b319945642a90653847a06d03f111b7
13:51.97 INFO: First bad revision: e43370e4259f61e0c264dbcef8b45e2862b3c5e8
13:51.97 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=7b7144975b319945642a90653847a06d03f111b7&tochange=e43370e4259f61e0c264dbcef8b45e2862b3c5e8
Updated•1 year ago
|
Reporter | ||
Comment 1•1 year ago
|
||
Reporter | ||
Comment 2•1 year ago
|
||
Hi @Emilio, can you take a look at this issue it seems that Bug 1847929 is causing it.
Comment 3•1 year ago
|
||
This looks like a duplicate of bug 1856497, which just landed. Is it reproducible on nightly / latest beta?
Reporter | ||
Comment 4•1 year ago
|
||
This happens in early beta as well 119.0b1, After getting a regression range it seems that Bug 1847929 is the cause of it. I did notice that Navigating with the Tab key also breaks.
Comment 5•1 year ago
|
||
I don't seem to be able to reproduce this on Nightly. Going to here which is the first desk that shows up, pressing F6 goes to the review checker, and pressing F6 again to the urlbar, am I missing something?
Reporter | ||
Comment 6•1 year ago
|
||
For me it happens in Nightly 120.0a1 (2023-10-12) , I reach a desk, wait for the product details page to load and then hit F6.
If I hit F6 while the page is loading, its reaching the URL bar for the first time but after it fully loads it stops working. I got another screen recording of it from our latest nightly build.
Please take a look at my screen recording
Reporter | ||
Comment 7•1 year ago
|
||
Comment 8•1 year ago
|
||
Can you paste me the particular URI where you see this? Does it happen on all product pages or just in some of them?
Leaving ni? to investigate regardless, thanks.
Updated•1 year ago
|
Reporter | ||
Comment 9•1 year ago
|
||
Here is a URL where it happens : https://www.amazon.com/Lufeiya-Small-White-Desk-Drawers/dp/B0CB5H4JT1/ref=sr_1_1_sspa?keywords=desk&link_code=qs&qid=1697188383&sourceid=Mozilla-search&sr=8-1-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&psc=1
I will attach a new video youll see exactly after refresh when the f6 works because it reaches the url bar twice, and after the page stops loading the F6 just stops working. After the refresh I keep hitting F6 until i stop recording.
Reporter | ||
Comment 10•1 year ago
|
||
Updated•1 year ago
|
Comment 11•1 year ago
|
||
setting up access-s2 severity since the issue would be blocking for keyboard-only users. I hope this was fixed by the bug 1847929 though
Comment 12•1 year ago
|
||
I still can't reproduce this on nightly at all, withe either my regular profile or my clean profile... Rares, does latest nightly show the same issue? Anything I might be missing?
Reporter | ||
Comment 13•1 year ago
|
||
I was reproducing this in Nightly before but it no longer occurs in our latest Nightly Build 20231016192851 or our latest Beta build.
Closing this issue with Works for me and reopen if it starts to reoccur. Thanks @Emilio
Updated•1 year ago
|
Description
•