Description: When testing with NVDA and using the tab key to navigate this dialog, two scroll panes are read without labels. Steps to Reproduce: 1. Press Alt+H to open the Help menu. 2. Select Check for Updates. 3. Press the Tab key to navigate between controls in the dialog. Actual Results: NVDA reads two scroll panes without announcing a label. Expected Results: These scroll bars should expose names to assistive technologies. Reproducible: Always User Profile Reset: Yes Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
Repro with NVDA 2016.4. Also, it did not read the contents of the Status scroll pane "LibreOfficeDev 5.4 is up to date". Win 10 Version: 5.4.0.0.alpha0+ Build ID: 7ed40deee74a9869b7da073ad473241187420ff8 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2016-12-30_23:18:54 Locale: fi-FI (fi_FI); Calc: group
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Repro in Version: 6.1.0.0.alpha0+ Build ID: 60ae5f530c3123341a8c2d49793693c2cd4521c2 CPU threads: 2; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-02-19_23:37:52 Locale: en-US (en_US); Calc: group
Dear am_dxer, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear am_dxer, 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
*** Bug 156929 has been marked as a duplicate of this bug. ***
Created attachment 189287 [details] Sample document with UNO edit controls Still reproducible, s.a. newly reported duplicate bug 156929. The dialog implementation is here: extensions/source/update/check/updatehdl.cxx It uses UNO controls, UnoControlEditModel for the panes that are not announced. Accerciser shows that the Text interface is not supported by that control, which might be the reason why it's not announced by screen readers. The same behavior can also be reproduced with the dialog in the attached sample doc ("Tools" -> "Macros" -> "Organize Dialogs" -> select the one from the doc -> "Edit" -> run preview). The single-line control supports the AT-SPI text interface w/ gtk3 on Linux and is announced by Orca just fine, the multi-line one is just announced as "blank"
(In reply to Michael Weghorn from comment #7) > The single-line control supports the AT-SPI text interface w/ gtk3 on Linux > and is announced by Orca just fine, the multi-line one is just announced as > "blank" Pending Gerrit changes which make the multi line edit expose the Text interface: https://gerrit.libreoffice.org/c/core/+/156400 https://gerrit.libreoffice.org/c/core/+/156401 https://gerrit.libreoffice.org/c/core/+/156402 As described in more detail in the commit message of the last change, these changes make Orca announce status ("LibreOfficeDev 24.2 is up to date.") when moving into the control using the Tab key. NVDA still says "Checking..." for that case, seems to be using the accessible name rather than the text (and that's outdated on Windows for some reason). The label (which this bug report is primarily about) is still not announced. Don't know whether there's even a way to define a labelled-by relation for UNO controls (or that would require redesigning the dialog more).
(In reply to Michael Weghorn from comment #8) > NVDA still says > "Checking..." for that case, seems to be using the accessible name rather > than the text (and that's outdated on Windows for some reason). That will be fixed by https://gerrit.libreoffice.org/c/core/+/156411 > The label (which this bug report is primarily about) is still not announced. > Don't know whether there's even a way to define a labelled-by relation for > UNO controls (or that would require redesigning the dialog more). Didn't see a way to set such a relation when getting over the UNO API doc, so looks to me like it might need more fundamental changes to the dialog, which I don't plan to work on right now. The previously mentioned changes will allow to retrieve the most relevant information at least, even if the labels are still not announced.
Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/9a559df3fe2f623ac4eace30cdfeabb3a747c0e9 tdf#104833 a11y: Don't use VCLXEdit in VCLXAccessibleEdit It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/847df831b1c46a257fd371c6a193387cc9c06c4b tdf#104833 Move VCLXMultiLineEdit to public toolkit header It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/a766f7555c55c73e2dfd167e66f1bf32c75de6df tdf#104833 a11y: Use VCLXAccessibleEdit for VCLXMultiLineEdit It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/a5593114bb409c93c7cf79a3abac0c60a8aebb18 tdf#104833 a11y Send name changed event for text controls It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Michael Weghorn from comment #9) > > The label (which this bug report is primarily about) is still not announced. > > Don't know whether there's even a way to define a labelled-by relation for > > UNO controls (or that would require redesigning the dialog more). > > Didn't see a way to set such a relation when getting over the UNO API doc, > so looks to me like it might need more fundamental changes to the dialog, > which I don't plan to work on right now. This aspect is still reproducible with current master Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1f3cc565a32452ef52d66fef33c551dffff814c3 CPU threads: 32; OS: Linux 6.16; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Pending change series to fix that: https://gerrit.libreoffice.org/c/core/+/191075 (and underlying changes in the series)
Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/04b5cdcca0a2a37ccff5896116b597afdf4f42ee tdf#104833 update check: Start using vcl::Window more directly It will be available in 26.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/96ba07a515e1c346bdfa2cd91e87fe7afdf56e91 tdf#104833 update check: Use ProgressBar methods directly It will be available in 26.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/670de20ab13031d0fd52dd5333b593dc8931d84d tdf#104833 a11y: Set mnemonic widgets in update check dialog It will be available in 26.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.