Bug 155236

Summary: Status bar is missing when using NVDA screen reader
Product: LibreOffice Reporter: Ken Scott <natomaspiper>
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: vsfoote
Priority: medium Keywords: accessibility
Version: 7.5.3.2 release   
Hardware: x86-64 (AMD64)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 60251    

Description Ken Scott 2023-05-10 16:24:43 UTC
I am totally blind and use the Non Visual Desktop Access normally shorten to NVDA to operate my Windows 11 computer.  There seems to be two NVDA screen reader issues LibreOffice 7.5.3.  First, The installer in version 7.5.3.2 did not exposed the check box to add a desktop icon/shortcut.  I later had a sighted person install to the second problem.  This was version 7.5.3.3.  I do not know if the problem was fixed with that installer.  The second problem is that the status bar does not appear to be exposed to the NVDA screen reader.  The NVDA screen reader has a shortcut that verbally announce the content of status bar.  The shortcut is insert key plus the "end" key.  The does work in LibeOffice 7.5.3.3.  I also used the Windows F6 command to move through sections of the LibreOffice window in Writer.  NVDA announce the component landed on when using the F6 command.  The status bar is not announced.  I know from using other programs that NVDA will properly identify and announce the status bar content if the control is exposed through accessibility APIs.  I am therefore guessing that the problem is with LibreOffice 7.5.3.3.  I also had this problem with version 7.5.3.2 which is where all of this started.
Comment 1 V Stuart Foote 2023-05-14 01:48:04 UTC
This is already open as LibreOffice TDF issue bug 137075 and as NVDA github issue 11698 here: https://github.com/nvaccess/nvda/issues/11698

There is guidance for you on your nvda.groups.io posting
 
https://nvda.groups.io/g/nvda/topic/libreoffice_7_5_3_x_and_nvda/98856325

*** This bug has been marked as a duplicate of bug 137075 ***