Issue 117542 - ACC: AT-SPI accessible tree omits objects which are not visible on the screen.
Summary: ACC: AT-SPI accessible tree omits objects which are not visible on the screen.
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOo 3.2.1
Hardware: PC Linux, all
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: accessibility, needhelp
Depends on:
Reported: 2011-03-25 09:31 UTC by bhatdv
Modified: 2014-04-02 11:16 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Accessible tree shows only 22 of the 25 paragraphs in the document. (106.50 KB, image/png)
2011-03-25 09:31 UTC, bhatdv
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description bhatdv 2011-03-25 09:31:31 UTC
Created attachment 76189 [details]
Accessible tree shows only 22 of the 25 paragraphs in the document.

Some objects at the end of a writer document are not included in the AT-SPI accessible tree. If a document has n objects, the accessible tree shows only (n-k) objects. When an assistive tool navigating the document reaches (n-k)th object, it wrongly concludes that the last object is reached and wraps to the top.

Steps to reproduce:
1. Create a writer document containing 20 paragraphs, each paragraph consisting of only one or two words and terminated by a new line. Save and close the document. 

2. Reopen the document. Move the cursor to the first line.

3. Start Accerciser accessibility explorer.

4. Go to the accessible tree view at top left. As shown in attached screen-shot, select the accessible object corresponding to the Document view, with role document frame. Make a note of the number of paragraphs shown in 'Children' column. Close Accerciser.

5. Repeat steps 1-4 with more paragraphs (21, 22, 23, 24, ...) till number of paragraphs in accessible tree (Step 4) are less than the number of paragraphs in the document (Step 1).

When I carried out the above steps, I got the following results:
Paragraphs in document       Paragraphs in accessible tree
20                           20
21                           21
22                           22
23                           22
24                           22

Contents of my writer document were as below -
Para  1
Para  2
Para  3
Para  4
Para  5
Para  6
Para  7
Para  8
Para  9
Para 10
Para 11
Para 12
Para 13
Para 14
Para 15
Para 16
Para 17
Para 18
Para 19
Para 20
Para 21
Para 22
Para 23
Para 24
Para 25
Comment 1 eric.savary 2011-03-25 09:36:41 UTC
@bhatdv: I had a quick look at the accessibility issues you reported by now. I think I can confirm them all against 3.3.
To be sure please test against 3.3 too in the future. 3.2.1 is outdated.
Thank You!
Comment 2 bhatdv 2011-06-09 10:36:02 UTC
The real problem is that the accessible tree contains only those objects which are visible on the screen at any instant, and ignores those which are above or below. This prevents Assistive Technology tools from accessing the full document. So it needs to be fixed on a priority basis.
Comment 3 bhatdv 2011-06-10 04:46:47 UTC
This bug is a major hurdle in the way of assistive tools like Orca screen reader trying to access the whole document. How much easy or difficult is it to fix? May we get a tentative target date for fixing it?
Comment 4 bhatdv 2011-06-27 08:47:37 UTC
FLOWS_FROM and FLOWS_TO relationships, however, link together all paragraphs and table cells in the document, visible or not.
Comment 5 Oliver-Rainer Wittmann 2012-06-13 12:25:55 UTC
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.
Comment 6 V Stuart Foote 2013-08-07 14:15:45 UTC
adding accessibility keyword for meta issue tracking