https://bugs.documentfoundation.org/show_bug.cgi?id=156657
--- Comment #3 from Joanmarie Diggs <[email protected]> --- I'm comment on the ARIA stuff later, but I wanted to respond to some of your comments now. Normally all objects that might be of interest should indeed be in the accessibility tree. The fact that they are not in the case of, say, Writer, is why Orca users (and NVDA users I believe) cannot use Structural/Quick-Key navigation in documents. Please expose more -- not less -- in the accessibility tree. I honestly don't know if thousands of paragraphs would grind the system to a halt or not. The change in Atspi sets the maximum number of children in descendable objects to 65536. I'll test later. If that makes the problem go away, my guess is thousands of paragraphs would still be ok. AtspiCollection is fast. The Calc table has 2,147,483,647 children. That's a bit more than "thousands". Regarding the status bar test. To be clear, that was just to force the bug to be reproducible. The changes I'm making to Orca will be to use AtspiCollection **any time the task is to find one or more descendants**. And Orca does that often enough -- including for its Flat Review feature which is notoriously non-performant. AtspiCollection will fix that. And Flat Review's purpose is to present on-screen objects, so documents are relevant. Unfortunately, AtspiCollection does not currently have API that says "please avoid looking in documents/giant tables/whatever for stuff." All accessible objects are treated the same (modulo Mike Gorse's change last night). -- You are receiving this mail because: You are the assignee for the bug.
