Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross references in Word not treated as links by NVDA #14957

Open
Qchristensen opened this issue Jun 2, 2023 · 2 comments
Open

Cross references in Word not treated as links by NVDA #14957

Qchristensen opened this issue Jun 2, 2023 · 2 comments
Labels
app/microsoft-office p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.

Comments

@Qchristensen
Copy link
Member

Steps to reproduce:

  1. Open Microsoft Word
  2. Insert a heading (control+alt+1)
  3. On a separate line, create a cross-link to it: alt+s, r, f, then down arrow to heading, press enter to insert the cross link then escape to close the dialog.
  4. Press NVDA+space to put NVDA in browse mode
  5. Press NVDA+f7 to open the elements list. Look for the link.

Actual behavior:

No link is detected. The cross reference DOES work as a link, but is not recognised as one by NVDA.

Expected behavior:

Cross references should be treated as links. This is a regression - it was initially included in 2016.4 with PR #6242. I suspect it has regressed since moving to UIA for Word?

NVDA logs, crash dumps and other attachments:

System configuration

NVDA installed/portable/running from source:

NVDA version:

2023.1 installed

Windows version:

Windows 11 (64-bit) Version: 22H2, Build: 22621.1702

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

Office 365 (64-bit) Version: 16.0.16327.20248

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?

@seanbudd seanbudd added app/microsoft-office p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation. labels Jun 8, 2023
@XLTechie
Copy link
Collaborator

XLTechie commented Mar 25, 2024

@Qchristensen can you check the first ("bad") table of contents in 14956example1.docx from issue #14956?

In this document, at least in Word 2019, the cross references are not spoken as links (which I assume is true in your example as well, although it isn't stated), but additionally they can not be interacted with as links in browse mode, which may be contrary to your results. Unless you are using a mouse, when you say:

The cross reference DOES work as a link, but is not recognised as one by NVDA.

@Adriani90
Copy link
Collaborator

Adriani90 commented Apr 4, 2024

Probably related to or even duplicate of #5896 and #14956.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app/microsoft-office p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Projects
None yet
Development

No branches or pull requests

4 participants