Steps to reproduce:
1. Turn on Voiceover (Apple-F5)
2. Create new spreadsheet
3. Type something in a cell
4. Navigate the spreadsheet with arrows
Column and row not announced and if we move to a cell with content, that is also not read.
Column and row information should be announced as the user navigates cells. When a cell has content it should also be announced. Eventually voiceover announces busy and then the app crashes.
Platform (if different from the browser):
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/534.53.11 (KHTML, like Gecko) Version/5.1.3 Safari/534.53.10
Thank you very much for your bug report!
I have tried to reproduce this issue in order to confirm it, following your steps. However, as far as I can tell,
* LibreOffice 184.108.40.206 and
* LibreOffice 220.127.116.11,
both on Mac OS X 10.6.8, do not show the problem -- it seems to be fixed!
* If I navigate to an empty cell, I get announced: “cell C7” etc.
* If I navigate to a cell containing some text, e.g. “apple”, I get announced:
“apple, cell C7”
It does not make any difference if I use the mouse or the arrows to navigate the spreadsheet.
@ Chris Blouch:
Could you please test yourself a recent version of LibreOffice (3.5.6 or 3.6.1 or newer) and check if I have missed something or if this issue is really fixed?
(It is also possible that there is a problem with the Mac OS X version -- I use 10.6.8, you have used 10.7.3 for your test, but I don’t hope so; if necessary,
we must test this later.)
@ Alex Thurgood:
Hi Alex -- IIRC you have some experience with the MAC AT accessibility problems (you have filed bug 49576 - “Accessibility - MAC AT accessibility problems” ;-).
Could you please take a look at *this* bug?
According to my tests, it is already fixed in LibreOffice 18.104.22.168 and 3.6.3 or better, so we could close this bug as RESOLVED/WORKSFORME. But it would be very nice if you could double-check if my results are correct. (The original reporter did not answer to my question about the state of this bug, therefore I ask you to get a second opinion before closing the bug.)
Thank you very much!
Roman: I tried verifying this bug, but I'm not sure if I'm doing the right stuff, since I have very little experience with VoiceOver.
* turning on VoiceOver
* creating a new spreadsheet
* typing sth in a new cell
* navigating the spreadsheet with arrows
1. the OP writes that when navigating with arrows, cell column and row should be announced.
> that does not happen for me.
> it does announce that I'm on a textfield, but not which
2. More oddities (maybe another bug?): a text field is selected (D16) and that field also gets announced as being D16 textfield and editable. But when I move with the arrow keys (B9) the field I end on, does not get announced. Not sure if that is expected or intended.
3. OP writes that text in textfields should get read.
> when navigating to D7, no text is read. When I move around with the arrow keys, VoiceOver tells me "You are currently on Textfield, you can edit information bla bla bla" (loosely translated), but it does not announce column and row.
4. When I move around VoiceOver tells me, that I can navigate using ctrl + alt and arrow keys, but when I do that, nothing happens.
As I wrote, I thought this was an easy test, but it turns out, VoiceOver is rather difficult to grasp, if you are not used to it.
Hope this helps.
Sorry forgot to mention, testing was done on OS X 10.8.2 and LO 22.214.171.124.
Mac OSX 10.8.2
Version 126.96.36.199.alpha0+ (Build ID: f5cde53719544c7445ab6fdb465e332ac5678b0)
VoiceOVer thinks that the table area is empty and announces it as such even when there is content in a cell.
Adding Stuart to CC FYI as he's dealing with some of the accessibility issues.
This is fixed by patch provided in #54320. Not that the information spoken by VoiceOver is ideal (it behaves as if the cells had typing cursor active), but this specific issue is fixed.
Issue verified present without the patch on latest master on OS X 10.8.4 and fixed with the patch present on the latest master on OS X 10.8.4.
As Boris writes, the fix from https://bugs.freedesktop.org/show_bug.cgi?id=54320 should fix this here too. Setting to fixed.