Found in

• 119.0a1 (2023-09-13)

Affected versions

• 119.0a1 (2023-09-13)

Tested platforms

• Affected platforms: Ubuntu 20
• Unaffected platforms: macOS 12, Windows 10x64

Preconditions

• browser.shopping.experience2023.enabled:true
• browser.shopping.experience2023.optedIn:1
• screen reader enabled

Steps to reproduce

1. Open a random Amazon product.
2. Expand the How we determine review quality card.
3. Click on a random text.

Expected result

• Screen reader reads all text.

Actual result

• Only the selected row is read.

Regression

• Not a regression.

:ayeddi, is this behavior what we'd expect in a typical webpage, or have we marked up the contents of this component incorrectly?

It does sound to me that this would not be a blocking behavior. Unfortunately, I do not have access to an Ubuntu to test it with Orca yet, but per the markup in Win and Mac, it appears that the markup was done as expected (I have not seen any Linux-specific code for it) - this could be an Orca behavior.

:Jamie, do you think that may be a hittesting issue?

Punting to Eitan, as although I have a Linux vm, I can't test mouse tracking.

That said, if this happens on Linux but not on Windows, it's highly unlikely to be a Gecko hit testing issue.

I think this is how Orca (Linux's screen reader) works. When in web content it is in "browse mode" and it will read the content. In the sidebar it is using the system default "focus mode" which is meant for interactive content like controls. It is debatable what the default mode should be in that panel, but users encounter this frequently and quickly switch between modes using insert+a.