NVDA Fails to Recognize Links with Embedded <strong> Tag Using NVDA+K #17363

cary-rowen · 2024-11-04T15:41:42Z

Steps to reproduce:

Open an HTML file in a browser containing an <a> tag with an embedded <strong> tag (see code example below).
Move focus to the link containing the <strong> tag.
Press NVDA+K.

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>NVDA Test</title>
</head>
<body>
    <p>
        <a href="https://example.com"><strong>Example Link with Strong Tag</strong></a>
    </p>
</body>
</html>

Actual behavior:

NVDA does not recognize this element as a link.

Expected behavior:

NVDA should correctly identify this element as a link and report href value.

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

2024.4

Windows version:

Windows 10 22H2 (AMD64) build 19045.5011

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

Chrome 130.0.6723.92

Other information about your system:

None

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

NVDA Fails to Recognize Links with Embedded <strong> Tag Using NVDA+K #17363

NVDA Fails to Recognize Links with Embedded <strong> Tag Using NVDA+K #17363

cary-rowen commented Nov 4, 2024

NVDA Fails to Recognize Links with Embedded <strong> Tag Using NVDA+K #17363

NVDA Fails to Recognize Links with Embedded <strong> Tag Using NVDA+K #17363

Comments

cary-rowen commented Nov 4, 2024

Steps to reproduce:

Actual behavior:

Expected behavior:

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

NVDA version:

Windows version:

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

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

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

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

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