Voiceover, the screen reading tool for the blind and visually impaired built-in to MacOs has problems reading in Writer. As soon as a line break is inserted or a new paragraph is inserted, it thinks it has encountered a new edit box resulting in, among other things that Voiceover is incapable of reading one whole document and that editing in a multiline document is impossible. This is a deal breaker for blind and visually impaired Voiceover users. Steps to reproduce: 1, load a multi line document such as a news paper article or a text with many lines and paragraphs into Writer. 2; make sure Voiceover is running, voiceover is toggled on and off by hitting cmd+f5. 3 using arrow keys, (not voiceover commands) read the text line by line. 4, observe that for every new line or paragraph break Voiceover says "edit box". Now try having voiceover read a whole document by pressing control+option+a. Note that Voiceover stops reading after the first line instead of reading the whole document. Expected results: Voiceover should treat the whole document as one single edit box instead of multiple edit boxes. Current behaviour: Voiceover treats a document as if it contains multiple edit boxes, one for each line and paragraph break it encounters.
On 10.11.5, with LO 5132 : I can only get each line to be read by VoiceOver if I click on each one with the mouse. The combo keys do not work to move the VoiceOver box downwards from the top of my test document, and only the first line gets read. Confirming
Accessibility support is pretty bad on Mac as far as LO and VoiceOver is concerned and progress in this department is unfortunately slow.
** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
This bug is still there in all its glory. Possibly it has been even worse. Now you can't move the focus by using only arrow keys but only with voiceover commands and even then Voiceover thinks that new lines or paragraphs are new edit boxes.
Dear Krister Ekström, 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
Created attachment 170272 [details] Test document
Retested on macOS 11.2.2, LO 7.1.1.2 Persisting. Reproduce: 1. open test document 2. open macOS system preferences > Accessibilty > VoiceOver (Activate VoiceOver) 3. CTRL + ALT + A to read entire document Currently For each new paragraph VoiceOver explains about text box and group areas. Expected Entire document should be read in one go. This works as expected in Pages.