https://bugs.documentfoundation.org/show_bug.cgi?id=163989
Bug ID: 163989
Summary: Find bar text field does not appear in the
accessibility tree; something's emitting empty
notification events
Product: LibreOffice
Version: unspecified
Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Blocks: 36549
Steps to reproduce:
1. Launch Writer
2. Press Ctrl+F and type "foo"
3. Launch Accerciser and turn on event monitoring for object:text-caret-moved
events for soffice
4. Return to the find entry and left/right arrow among the letters in "foo"
5. When Accercisershows events for the text input, click on "[text | ]"
Expected results: clicking on "[text | ]" would cause Accerciser to show the
accessible object in the accessibility tree.
Actual results: clicking on "[text | ]" does nothing.
Notes:
1. The only reason I resorted to this is that I cannot find this text input
simply by examining the accessibility tree. So I figured it might have been
added somewhere unexpected.
2. If you're curious, repeat the steps above, but just write "foo" in the
document. When you click on "[paragraph | ]" in the resulting event, you're
brought to that object in Accerciser.
3. There doesn't yet appear to be any impact (at least not in Orca's main
branch). That might change depending on later sanity checks being added to
Orca.
4. As the selection in the document changes due to interactions within the find
input, a notification is firing the "showing" event causing Orca to say
"notification". But there's no presentable information in the accessible object
for Orca to present.
Michael: Could you please look into both issues? The announcement of
"notification" is annoying/pointless to users.
Related aside: I'm trying to add generic/global support for presenting
find-in-page/document results. If presenting the new document location is what
the notification is attempting to address, let's talk because there's a
different way this should be done, at least in the case of Orca. (New app
developer docs are on my todo list. :))
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=36549
[Bug 36549] [META] ACCESSIBILITY: Tracking bug for issues affecting a11y ATK
and GNOME Orca screen reader support
--
You are receiving this mail because:
You are the assignee for the bug.
