aria-labels are ignored in Edge for buttons and links

[mieketd]

Brief summary

NVDA seems to ignore the accessible name in Microsoft Edge for buttons and links. When setting de accessible name via an aria-label, the element's content is still being read by NVDA, instead of the aria-label.

The accessible name in the accessibility tree is updated with the aria-label, but NVDA still reads the content of the button and link element. See attached screenshot.

Steps to reproduce

1. Open the Codepen link in Microsoft Edge browser. Codepen link: https://codepen.io/mieketd/pen/GgqzWWW
2. Start NVDA.
3. Navigate with TAB or 'arrow up/down' keys to the button and the link elements in the Codepen.
4. Listen to the button and link name being read by NVDA on entering the focus of the elements.

Actual behavior

NVDA reads the DOM element's content.

NVDA Speech:
"This button has no function other than being a button element. button"

NVDA Speech:
"This is a link element, it leads nowhere link"

Expected behavior

NVDA should read the accessible name.

NVDA Speech:
"This is the button's aria-label button"

NVDA Speech:
"This the link's aria-label link"

NVDA logs, crash dumps and other attachments

nvda_log_12feb2026_edge_aria-label-bug.txt

nvda_speechviewer_12feb2026_edge_aria-label-bug.txt

NVDA type

installed copy

NVDA version

2025.3.2 (2025.3.2.53588)

Have you tried any other versions of NVDA? If so, please report their behaviors.

No response

Windows version

Windows 11 Enterprise 10.0.26100 Build 26100

Name and version of other software in use when reproducing the issue

Edge version: 144.0.3719.115 (Official build) (64-bit)

Other information about your system

Running Windows without admin rights, I cannot run the COM Registration Fixing tool because of this.
NVDA installed via scoop.
Verified in Chrome and Firefox that this issue does not exist, it is purely an Edge bug for this issue report.

Does the issue still occur after restarting your computer?

I have restarted my computer and the issue still occurs

If NVDA add-ons are disabled, is your problem still occurring?

I have restarted NVDA with add-ons disabled and the issue still occurs

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

I have not run the COM Registration Fixing Tool