https://bugs.documentfoundation.org/show_bug.cgi?id=158030
--- Comment #4 from Joanmarie Diggs <[email protected]> --- Nice! BTW, I just landed a change in Orca master which causes it to look for rowindextext and colindextext for Calc. Hopefully that will allow you to test your prototype. Currently if I up arrow in Calc, I see this in my debugging output: > (timestamp) - AXTable: Coordinates label for [table cell: 'C1']: For Google sheets, I see this: > (timestamp) - AXTable: Coordinates label for [table cell]: > (timestamp) - AXTable: Updated coordinates label based on [table row]: C1 The reason why is that the ARIA rowindextext property is supported on both cell and row. Related aside: Orca currently takes an all-or-nothing approach: Either both indices are provided or it doesn't use an alternative label for the coordinates. Whether or not Orca should be that picky is TBD. :) Anyhoo, Sheets exposes accessible row objects, so Orca checks there for the rowindextext before giving up. The rowindextext is indeed exposed by Sheets on the row, and we got the colindextext from the cell, so we're good. What I expect to see in the case of Calc, which does not expose accessible row objects, is: > (timestamp) - AXTable: Coordinates label for [table cell: 'C1']: C1 assuming you continue to expose the coordinates as the accessible name. If you stop doing that, I'd expect: > (timestamp) - AXTable: Coordinates label for [table cell]: C1 If you have a local implementation and don't see that in your debug.out from Orca, let's talk. :) -- You are receiving this mail because: You are the assignee for the bug.
