1893725 - Links of cards on the discovery stream on the about:newtab are missing context

Status: NEW

(Firefox :: New Tab Page, defect)

Description

[Anna Yeddi [:ayeddi]]

Attachment: Only the title of the link is announced by NVDA, without a context when navigated with Tab

STR:

1. Ensure a screen reader is running
2. Using keyboard alone, navigate to one of cards in the Thought-provoking stories section and focus it with Tab
3. Observe the announcement
4. In browse mode of a screen reader (i.e. by using Down Arrow with NVDA and ctrl+opt+Down Arrow by default with VoiceOver) review the content of each card

Current:

1. (with Tab) Only the title of the link is announced by a screen reader while the short URL, description, and sponsored tag (when present) are skipped while they are all visually included in the focused element, i.e. the card on the screenshot visually has the following content (marked what's ignored/announced):
   1. business.walmart.com URL [skipped]
   2. Catch these Lightning Deals title [announced]
   3. Save up to 65% in the Walmart Business flash sale. text [skipped]
   4. Sponsored by Walmart Business footer text [skipped]
2. (with browsing) The title of the link is injected at the beginning of the card and then repeated after the URL that creates a redundancy and does not follow the visual reading order.

Expected:

1. (with Tab) Each link should provide a context for a . Otherwise, screen reader users may While it does not have to be visually marked up as a link, it could be referred from the hyperlink via aria-describedby, or included in the grouping like <article>
2. (with browsing) Avoid redundancy in the announcement and ensure the visual reading order of the page is followed by the programmatic reading order

Recommendation:

use any of the Card guidance provided by Adrian Roselli's blog or Heydon Pickering's Inclusive Components

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.