Bug 81098 - Calc is not accessible to screen readers on Windows [a11y]
Summary: Calc is not accessible to screen readers on Windows [a11y]
Status: RESOLVED DUPLICATE of bug 81264
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.3.0.2 rc
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: a11y-Windows
  Show dependency tree / graph
 
Reported: 2014-07-09 10:41 UTC by Arnaud Versini
Modified: 2014-09-11 13:18 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Arnaud Versini 2014-07-09 10:41:24 UTC 
Hi,

We noticed that LibreOffice 4.3.0.2 is not accessible anymore on Windows:

Steps to reproduce :
- Launch calc with a screen reader (nvda for example), and open a document with content
- Move to another cells
- 

Expected :
- Screen reader should tell you cell coordinate

Current :
- No sound with cell coordinate
Comment 1 V Stuart Foote 2014-07-09 14:19:31 UTC 
Confirming.

On Windows 7 sp1, 64-bit en-US with NVDA 2014.2 with
Version: 4.3.0.2
Build ID: 14ed55896fdfcb93ff437b85c4f3e1923d2b1409

and similar with todays TB 39 build of master
Version: 4.4.0.0.alpha0+
Build ID: 3fdd4f069d5436cf39708004af7fda8175fbc4c2
TinderBox: Win-x86@39, Branch:master, Time: 2014-07-09_02:51:54

There is a focus issue on launch of Calc.

Simple to work around by navigate with F2 to formula bar and then back, the cell address and content is then announced. Further navigation with cursor (L,R,U,D) does announce cell address and numerical content.

If cell is empty it is still announcing "Zero" (bug 74441).

And, noticed today that non-numeric (text string) cell content incorrectly being rendered as "zero", it will render correctly from the F2 formula bar. Will open a new issue for this.
Comment 2 Jean-Philippe MENGUAL 2014-07-10 13:10:22 UTC 
Hi,

Our test was based on Windows XP. We saw a general problem as it doesn't happen only while running for the first time. Then, it doesn't affect only numerical data. So the bug seems deeper and larger, I think. Really it happens at no time.

Regards,
Comment 3 V Stuart Foote 2014-09-11 13:18:49 UTC 
merging as duplicate of bug 81264 which is on mab4.3

*** This bug has been marked as a duplicate of bug 81264 ***