1893738 - Nothing is announced by NVDA after hovering over card images and the "..." button on activity stream

Status: NEW

(Firefox :: New Tab Page, defect)

Description

[Anna Yeddi [:ayeddi]]

Attachment: Nothing is announced by NVDA after hovering over card images and the "..." button on activity stream

STR:

1. Ensure a NVDA screen reader is running
2. Hover over one of cards in the Thought-provoking stories section
3. Observe the announcement
4. Hover over one of the ... Open menu buttons on cards in the Thought-provoking stories section
5. Observe the announcement

Current:

1. Nothing is announced by NVDA after hovering over card images and the ... buttons on activity stream

Expected:

1. Card title would be announced when hovered, the button label would be announced when hovered

Note:

While a button or a link does not have any visible text always, NVDA will not read the label, 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. That's being said, it as access-s3 since this is not a delightful pattern in any case + the on-hover nature of the ... controls and lack of any alternative way to access their functionality (covered in bug 1893509) does show that the Firefox could do better even while there is an issue with the assistive technology software.

Recommendation is either:

1. to add an on-screen text (like the Save to Pocket button does which at least has this text announced on hover), so there is an on-screen text (that is included in the 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.

Comment 1

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

The severity field is not set for this bug.
:amy, could you have a look please?

For more information, please visit BugBot documentation.