Created attachment 44225 [details]
Accerciser screenshot: Accessible tree view does not show sections of a document.
A section in writer document is not visible to AT-SPI. If a section is visible to AT-SPI and exposes ROLE_SECTION, assistive tools like a screen reader can use the information to improve accessibility of the document.
Steps to reproduce:
1. Start Libre Office writer. Create a new text document. Add a section. Add some text e.g. 'Content of section 1' into the section. Add another section. Add some text e.g. 'Content of section 2' into it. Save the document.
2. Start Accerciser accessibility explorer.
3. Go to the accessible tree view at top left. As shown in attached screen-shot, select the accessible object corresponding to the document just created. The tree shows only paragraphs under the document. There are no accessible container objects corresponding to the sections.
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Today I rechecked my observation with Libre Office dev 3.5.0 beta2 and found that the bug persists. I suggest that the bug be moved back to NEW status.
Dear bug submitter!
Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.
To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement
Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.
The bug is real. I noticed it in version 3.3.0 and submitted it with a supporting screenshot. I reconfirmed that the bug exists with version 3.5.0 beta2. It falls in the same category as bugs 35105, 35107, 35110, 35111, 35129 which you have reopened and changed to NEW.
reopening due to comment 7
Not reproduced with libo Version 22.214.171.124.beta1 (Build ID: 87906242e87d3ddb2ba9827818f2d1416d80cc7)
>>2. Start Accerciser accessibility explorer.
I suppose you talk the explorer displayed by F5 ?
>> The tree shows only paragraphs under the document.
I see my 2 sections below "sections"
>> There are no accessible container objects corresponding to the sections.
If I dubble clic on section 1, cursor is moved on the start of this section. (box before the text of my section)
I think it's the correct way, isn'it ?
>>Not reproduced with libo Version 126.96.36.199.beta1 (Build ID: >>87906242e87d3ddb2ba9827818f2d1416d80cc7)
Is there a confusion? It seems you are trying to reproduce on Windows 7 a bug which was reported with Linux.
>>I suppose you talk the explorer displayed by F5 ?
Are you referring to the navigator feature of Libreoffice which can be toggled on/ off with F5? No, my bug doesn't relate to it.
I mean Accerciser Accessibility Explorer (https://live.gnome.org/Accerciser). It is an interactive Python accessibility explorer for the GNOME Linux desktop. It uses AT-SPI to inspect and control widgets, allowing you to check if an application is providing correct information to assistive technologies and automated test frameworks.
>>I see my 2 sections below "sections"
>>If I dubble clic on section 1, cursor is moved on the start of this section.
>>(box before the text of my section)
>>I think it's the correct way, isn'it ?
Please run LibreOffice on Linux. Start Accerciser (Its a distinct app, not a part of LibreOffice. Now go to the accessible tree view at top left of Accerciser window and see if you can find two accessible objects with role 'section'.
Adding Need_Advice so that a developer checks this out. Hopefully we can confirm that this is our bug (or determine that it's not) shortly. Apologies for the report being so old and left in UNCONFIRMED status.
Thanks for your patience and continuing to provide details
Great bug report - no problem converting it to new - sorry, most of the QA team are not experienced in a11y :-)
This is really an enhancement request. Would you like some code pointers :-)
Corresponding Apache OpenOffice bug: https://issues.apache.org/ooo/show_bug.cgi?id=117260
Bug status NEW
Whiteboard: Removing 'Need_Advice'
I'm able to reproduce the bug in version 5.1.1.
I can read the content of the section with Orca (screen reader) but I've no information about I'm in a section because of this issue.