[Link] Empty Link

[coseeian]

Title

[Link] Empty Link

Description

An anchor () element on the page is missing any textual content or accessible name, so screen readers announce only its role (e.g., “link”) without any descriptive label. As a result, users will not be able to identify the purpose or destination of the link. Empty links can be confusing for screen reader users, keyboard users, and others relying on assistive technologies, as they have no way of knowing the purpose or destination of the link.

Steps to Reproduce

1. go to /reference/p5.sound/
2. Locate to the following element: ._linklabel_aobbt_1052 (CSS Selector)

Actual Behavior

• The element is a link () with no visible text content, and no accessible text through aria-label or other means.
• When tabbing to the link, a screen reader announces only “link” without any label or description.

Expected Behavior

• All links should have meaningful, descriptive text that communicates their purpose or destination—even when read out of context. This text should be perceivable either visually (through link text) or programmatically (via aria-label or similar attributes).
• When tabbing to the element, A screen reader should announce a meaningful label.

Environments

No response

Suggested Fix

If the link is necessary, provide descriptive text or an appropriate accessible label (e.g., aria-label="Read more about sound"). Remove the empty link or provide text within the link that describes the functionality and/or target of that link.

Reference

2.4.4 Link Purpose (In Context) (Level A)

What is your operating system?

None

Web browser and version

No response

[reshma045]

@coseeian I'd like to work on this issue. Can you assign it to me?

[reshma045]

Hi @coseeian can you please review my PR that I've linked to this issue?

[ugec67]

Hello maintainers! 👋 I’m a first-time contributor and very interested in contributing to this issue. Please let me know if I can take this up, and kindly assign it to me if it’s still available. Thank you in advance!

[ksen0]

Hi @ugec67 , looks like @reshma045 is still working on this one - but as in another issue, you're welcome to participate in that PR through discussion and review. Thank you both for your effort!