NVDA with MathCAT Unnecessarily Announces Document Section Number After Speaking Display Math Expressions in Word 365

[brichwin]

Description

When using the NVDA screen reader configured with the MathCAT plugin in Microsoft Word (Windows OS, Word 365 desktop app), an annoyance occurs when reading display math expressions. After display math expressions are spoken, a "Section n" announcement is made where n appears to represent the current section number. The announced section number is sometimes incorrect, frequently reverting back to "Section 1" when in later sections of the document.

The "Section n" announcement does not occur when in-line math expressions are spoken.

This issue does not occur at all when using the JAWS screen reader with MathCAT, which speaks math expressions of any type without appending any unnecessary section number announcement.

In a document of any length, the unnecessary section announcement creates a cognitive burden for users, as the repetition of "Section n" announcement becomes distracting and tiresome.

Steps to Reproduce:

• Open a Word document with multiple sections.
• Add both inline and display math expressions in different sections of the document.
• Use NVDA with MathCAT to navigate through the document.
• Observe that NVDA announces "Section n" after display math expressions, and that the section number is not always correct.

Version Info

OS Version

-- OS Name: Microsoft Windows 11 Enterprise
-- Version: 10.0.22621 Build 22621
-- Locale: United States

Microsoft Word Version

-- Microsoft 365 Apps for enterprise
-- Version 2402 (Build 17328.20588 Click-to-run)

JAWS Version

-- JAWS Professional Version 2024.240.2 with MathCAT enabled.

NVDA Version

-- NVDA Version 2023.3.4 (2023.3.4.31265)

Demonstration Video and Sample File

• Here is a short video demonstrating the issue: Video: "Section n" Announced After NVDA+MathCAT Speaks a Display Math Expression in MS Word 365 (3 minutes)
• Word file used in the video: This Is a Multisection Document.docx

[MaryStores]

I have verified this issue.