Bug 135435 - ACCESSIBILITY: No information from screenreader in "check for updates" window
Summary: ACCESSIBILITY: No information from screenreader in "check for updates" window
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.5.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks: a11y-Windows
  Show dependency treegraph
 
Reported: 2020-08-04 14:05 UTC by Karl-Heinz Arkenau
Modified: 2023-10-15 03:16 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karl-Heinz Arkenau 2020-08-04 14:05:25 UTC
Description:
In the check for updates window no information is announced by screenreader. 

Steps to Reproduce:
1. open LibreOffice
2.mot to the help menü
3. Hit the check for updates item.
4. The window "check for updates" window opens, but only "movable window" is announced.

Actual Results:
screenreader says "moveable window"

Expected Results:
Screenreader announces the status of the update check and what else is in the window.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Needs screenreader to be reprocuced.
Comment 1 juergenkohler23 2020-09-03 07:19:19 UTC
I reproduced this bug with LibreOffice 7.0 and NVDA 2020.2.
Comment 2 juergenkohler23 2020-09-03 07:21:09 UTC
I forgot to mention that I was using Windows 10.
Comment 3 Matthias Doellert 2020-09-07 14:35:28 UTC
The bug could be reproduced.  Windows 10, Libre Office 7.0.0.3 (x64), NVDA 2020.2 and 2019.2.1
Comment 4 juergenkohler23 2020-09-10 07:16:27 UTC
Addition to my exact operating system information:

Windows
Edition	Windows 		10 Home
Version				1909
Operating system build		18363.1016

LibreOffice
Version:	7.0.0.3 (x64)
Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e
CPU-Threads: 	4; BS: Windows 10.0 Build 18363; UI-Render: Skia/Vulkan; VCL: win
Locale: 	de-DE (de_DE); UI: de-DE
Calc: 		threaded
Comment 5 juergenkohler23 2021-03-01 11:42:24 UTC
With NVDA+B, a part of the window is read out, but you still don't get to know what is actually decisive (the status message). Visualising the status window via an add-on does not work either. I tested this time with NVDA 2020.4.
Comment 6 Michael Weghorn 2021-10-14 08:28:00 UTC
Corresponding issue in NVDA issue tracker: https://github.com/nvaccess/nvda/issues/11683
Comment 7 QA Administrators 2023-10-15 03:16:09 UTC
Dear Karl-Heinz Arkenau,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug