1849572 - Certain Cards from the Shopping sidebar cannot be reached using keyboard navigation

Status: RESOLVED INVALID

(Firefox :: Shopping, defect, P2)

Description

[Rares Doghi, Desktop QA]

Attachment: keyboard.mp4

Found in

• Nightly 118.0a1 (2023-08-21)

Affected versions

• Nightly 118.0a1 (2023-08-21)

Affected platforms

• ALL

Preconditions:
Set the browser.shopping.experience2023.enabled - TRUE
Set the browser.shopping.experience2023.optedIn - 1

Steps to reproduce

1. Reach the following links https://www.amazon.com/dp/B07V6ZSHF4?th=1
2. Use the tab key to reach each label or text from each card on the Shopping sidebar.

Expected result

• Each card Label and Text should be keyboard accessible.

Actual result

• The How reliable are these reviews cannot be reached using keyboard navigation.
• The Adjusted rating card cannot be reached using keyboard navigation.
• The Highlights from recent reviews cannot be reached using keyboard Navigation. (The user can only reach Show more button)
• The user cannot reach the Content from the "How we determine review quality" text. *(The user can only reah the Title and Link from that card)
• The user cannot reach the More To Consider Title from the card. (The user can reach the Link from that card).

Regression range
Not Applicable

Comment 1

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

:rdoghi, if you think that's a regression, could you try to find a regression range using for example mozregression?

Comment 2

[Anna Yeddi [:ayeddi]]

@Rares, if I understand correctly, all controls (buttons and links) can still be reached with the keyboard?

If so, this is an expected behavior, because we do not want to make inactive elements (like headings and text) focusable - it would increase the number of tab stops that the keyboard-only user has to make in order to navigate through the sidebar while there elements cannot be activated with a keyboard, thus are not expected to be focusable. The sidebar has focusable elements too which would allow a keyboard-only user to scroll the content with arrow keys. Inactive elements that are read-only may be very rarely made focusable to allow a user to copy their content, but I do not think this is the case here.

Comment 3

[Rares Doghi, Desktop QA]

Hi @Anna, the problem here is that the user is missing valuable information with screen readers, If he is using a screen reader and tries to use the keyboard navigation to go through the sidebar, he wont be able to reach the real Ratings of those reviews or the the Recent Highlights of it, he can only reach the Show more button or some links, which doesn't realy help people that are visually impaired.

On Mac we can use the Voice over to reach those labels but On Windows it will just jump from the X Close button straight to the Show more button.

Comment 4

[Anna Yeddi [:ayeddi]]

(In reply to Rares Doghi, Desktop QA from comment #3)

Hi @Anna, the problem here is that the user is missing valuable information with screen readers, If he is using a screen reader and tries to use the keyboard navigation to go through the sidebar, he wont be able to reach the real Ratings of those reviews or the the Recent Highlights of it, he can only reach the Show more button or some links, which doesn't realy help people that are visually impaired.

On Mac we can use the Voice over to reach those labels but On Windows it will just jump from the X Close button straight to the Show more button.

NVDA users can read all content with Down Arrow key or with Say All command (NVDA+a on laptop or NVDA+DownArrow on desktop) - in this case all non-interactive content is being announced as expected. Using Tab is reserved for navigating between interactive content (everything that is clickable with a mouse), and static text even when its as important as letter rating is still not expected to be included in the focus order (with Tab) but it is expected to be announced with arrow navigation (when a screen reader is running).

Comment 5

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

Sounds like this is an invalid issue, closing. Please reopen if I'm incorrect