If one creates a bulleted list, presses home to go to the beginning of the line and then presses left arrow to place focus on the bullet, nothing is spoken by Orca. It would be nice to have the screen reader speak bullet and even possibly describe the bullet such as something like "large square bullet."
Did some quick triage. When you left arrow to the bullet as described in the opening report, the caret moves but there is no accessible object:text-caret-moved event (for that matter, I don't see any other accessible events resulting). Thus Orca has no idea anything happened or that there's something to present.
In addition, the bullets are not part of the accessible text (which would explain the lack of caret-moved events). To verify: 1. Create a document with a bulleted list. 2. Launch Accerciser. 3. In Accerciser's object tree (on the left), select an accessible list item 4. In Accerciser's iPython console, type the following to get all the text: acc.queryText().getText(0,-1) Expected results: The text returned would include the bullet. Actual results: The text returned does not include the bullet.
Niklas Johansson committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=64bf04de183a63d32fddf9376307b7f991a4519a tdf#93139 Orca Screen Reader does not read bullet It will be available in 5.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Thank you for working on this bug. I can confirm that the bug is partially resolved. If I create documents in the ODT format, bullets are read correctly. However, if I save a file with bullets as a DOC file, close writer, and then open the document in writer again, the bullets are not read.
(In reply to am_dxer from comment #4) >However, if I save a file with bullets as a DOC file, close > writer, and then open the document in writer again, the bullets are not read. It seems that when a document is saved in doc file format the bullet characters are replaced with another character, the unicode character 61623 (U+F0B7), that is a bullet character in the Symbol set that Microsoft software usually use. I suppose that the conversion is done to be compatible with Microsoft Office. Question is what the best way to handle this is. At the moment LibreOffice exposes the character in question but for most fonts it is not a bullet character, so Orca does not interpret it as such. I wonder if the conversion is really needed or just a legacy from the past.
(In reply to Niklas Johansson from comment #5) > Question is what the best way to handle this is. At the moment LibreOffice > exposes the character in question but for most fonts it is not a bullet > character, so Orca does not interpret it as such. I wonder if the conversion > is really needed or just a legacy from the past. It looks like it is not just limited to plain bullets: From a quick test, the checkmark bullet winds up being U+FOFC. I assume this is true of the other bullet types. In addition, the replacement characters appear to be in the Private Use Area. And keep in mind we don't just want to speak the displayed symbol correctly, but also braille the displayed symbol correctly. Long way of saying: I'm extremely hesitant to hack around this in Orca. If the conversion is really needed -- or if you just don't know for certain -- how hard would it be for you to expose the unconverted (converted-back) symbol via AtkText? Orca won't check to see if you're "lying" to it. ;)
Niklas Johansson committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=e2ff5810f1578794aa2617e8d0b44d64642f8eca tdf#93139 Orca Screen Reader does not read bullet part 2 It will be available in 5.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Migrating Whiteboard tags to Keywords: (a11y -> accessibility)
Dear all, the problem appears with DOC document (cf. comment #4) in version 5.1.2. Best regards.
** 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
I have tested using the steps from comment #2 (my first experience with Accerciser). A bulleted list item with the text "Test 1" in an ODT-file is read as '• Test 1' The same item in a DOCX-file is read as '\ufb07 Test 1' The same item in a DOC-file is also read as '\ufb07 Test 1' Orca does indeed speak the bullet when in ODT, but not in DOC or DOCX format. Version: 6.0.6.2 Build ID: 1:6.0.6-0ubuntu0.18.04.1 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: nl-NL (en_US.UTF-8); 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 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
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