1709855 - The infobar close ('x') buttons are not being read by NVDA when hovering over them with the cursor

Status: NEW

(Firefox :: Messaging System, defect, P3)

Description

[Daniel Bodea [:danibodea]]

Note

• When the user uses Firefox with NDA screen reader and he overs over the close ('x') button of an infobar, no vocal action is being read back to him.

Affected versions

• Nightly v90.0a1
• Beta v89.0b7

Affected platforms

• Windows 7
• Windows 10

Steps to reproduce

1. Open NVDA Screen Reader.
2. Launch browser.
3. Load http://dummysoftware.com/popupdummy_testpage.html
4. Hover with the cursor over the "x" button.

Expected result

• Some relevant tool-tip is currently being read back.

Actual result

• Nothing is being read to the user.

Regression range

• Not a regression, but a requirement for the new design regarding Screen Reader usability.

Additional notes

• When the user uses keyboard navigation (with NVDA or Windows Narrator) the 'x' button is read as "closed", but this does not happen on hover with NVDA (which is expected considering that it reads the strings on other buttons on them).
• Furthermore, a "close" is being read back when clicking the 'x' button (among other apparently spam information), but not on hover.

Comment 1

[Monica Chiorean]

Attachment: 2023-10-04_10h01_23.png

Same issue occurs for PDF infobar message. Close ('x') button is not read by NVDA on Win11/Win10.

Comment 2

[Monica Chiorean]

Attachment: 2024-03-19_12h57_34.png

Issue also occurs for Mailto infobar message. Close ('x') button is not read by NVDA on Win11/Win10.

Comment 3

[Anna Yeddi [:ayeddi]]

This button does not have any visible text always, NVDA will not read the text, which is a known issue with NVDA mouse tracking.

Since the button does have an accessible name provided (which can be checked in the Devtools Accessibility inspector), the lack of on-hover announcement, in this case, is the NVDA bug.

What we could do to make the user experience better is either:

1. to add an on-screen text next to color option circles, so there is an on-screen text (that is included in the option markup) - this should be announced by the NVDA.
2. to add an invisible <span> in the button as Calixte offered in the bug 1886964#c1 and in the attached patch. This would also work as an accessible name source for the button.

I'll triage it as access-s4 since this is not a delightful pattern in any case, but yet the issue is not as severe and is largely dependent on the assistive technology software.