Bug 148136 - Spelling dialog: Orca screen reader doesn't announce initial focus on "Not in dictionary" edit view
Summary: Spelling dialog: Orca screen reader doesn't announce initial focus on "Not in...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
7.4.0.0 alpha0+
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks: Spell-Checking a11y, Accessibility GTK3
  Show dependency treegraph
 
Reported: 2022-03-22 12:52 UTC by Michael Weghorn
Modified: 2023-04-09 05:12 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Weghorn 2022-03-22 12:52:40 UTC
With the change for tdf#135234 in place, initial focus in the spelling dialog is on the "Not in dictionary" field.

However, while e.g. the NVDA screen reader on Windows announces that field as focused when the dialog opens, the Orca screen reader on Linux with the gtk3 VCL plugin doesn't do so.

Steps to reproduce:

1) start the Orca screen reader
2) start Writer with the gtk3 VCL plugin
3) type some non-existing words
4) open the spell dialog by pressing F7

Actual result:

In the UI, the focus is on the "Not in dictionary" field. However, Orca does not announce it.
It is also not announced when using Orca's "Where am I" functionality.

Expected result:
Orca should announce the "Not in Dictionary" field with content, as is the case e.g. when switching focus to another window and back using Alt+Tab or when moving to that widget using the Tab key.

More details in the discussion in https://gerrit.libreoffice.org/c/core/+/131182
Comment 1 Michael Weghorn 2022-03-22 12:56:03 UTC
https://gerrit.libreoffice.org/c/core/+/131182 has more details on the cause (see there), quoting one comment:

> I have submitted a WIP/demo change at
> https://gerrit.libreoffice.org/c/core/+/131731 that causes the children for the
> drawing area to be created earlier, and with that (...) in place,
> focus is announced as desired.
> 
> However, that change is not meant to be submitted as is. I plan to take
> a closer look at how lifecycle for a11y objects in the gtk3 VCL plugin
> is supposed to work, then hopefully come up with a proper change. (I'll
> probably do that once I get back to tdf#87680, where the
> situation is somewhat similar.)