Apache OpenOffice (AOO) Bugzilla – Issue 117542
ACC: AT-SPI accessible tree omits objects which are not visible on the screen.
Last modified: 2014-04-02 11:16:09 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
@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!
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.
@es 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?
FLOWS_FROM and FLOWS_TO relationships, however, link together all paragraphs and table cells in the document, visible or not.
getting rid of value "enhancement" for field "severity". For enhancement the field "issue type" shall be used.
adding accessibility keyword for meta issue tracking