Hi, Using Orca master, enabling accssibility in your desktop environment: 1. Open Insert, Index & table, Index & table 2. Choose "Customized index" as type 3. Check "styles" checkbox 4. Prss Apply the styles button A table appears. It is not described as a table. Then, while up and down arrow keys make the style list scroll, the user is not aware there are several columns, and right and left arrow keys do not anything. Another consequence is that if using Left and Right buttons, the style is moved from "non assigned" to another column, but the screen reader does not inform the user about this change, and browsing in the table does not the information per keyboard. We would expect the table to be considered as a table widget, and the user can browse via up, down, left and right keys through columns. Regards
I confirm the issue on LibreOfficeDev 6.3 built this week. Best regards, Alex.
I can reproduce this with Libreoffice 6.2.1. When inwoking Insert -> Table of Contents and Index -> Table of Contents, Index or Bibliography... from the menu bar in Writer a tabbed dialog comes up. On the Styles tab there are some comboboxes however their relations are not clear to me I think I need some hints in order to be able to use this part. When proceedingas instructed i.e. * Setting type to User defined * Checking Styles inside the Create from pannel * hitting Assign styles button I can see semi accessible tree table. Column and row headers are reported when navigating by using arrow keys however state of the checkboxes is not reported. Version: 6.2.1.2 Build ID: 6.2.1-1 CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: en-US (en); UI-Language: en-US Calc: threaded
Dear Jean-Philippe MENGUAL, 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
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/4e41879586fb24e925fb59dd06c43235f298e66d Related: tdf#123846 don't auto toggle radiobuttons with left/right It will be available in 7.5.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.
Under gtk, I think in 6.2 and earlier we had vcl widgets here and from 6.3 onwards we have gtk widgets. I don't know if the original report from Jean-Philippe is under gtk or not, comment #3 is wrt gtk though. Under gtk the widget is a true GtkTreeView but with orca I can see that the "style" column is read twice and the radiobuttons are not announced as toggling. I find that if I change the appname from "soffice" to anything else then the style column is read once and the toggle buttons are announced nicely. So I presume orca has some special handling for LibreOffice based on the appname and we're perhaps not getting the full benefit of the native gtk widgets a11y when we're using those. caolanm->jdiggs: I don't know if there is a way to help orca to not do special LibreOffice stuff when we're using real gtk widgets?
The LibreOffice script in Orca can check the toolkit and defer to the Gtk script if it's native Gtk.
Dear Jean-Philippe MENGUAL, 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