[Libreoffice-bugs] [Bug 155447] Add accessible object attributes to LO spellcheck dialog components for reliable identification by ATs

2023-11-06 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155447

Michael Weghorn  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=13
   ||5236

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155447] Add accessible object attributes to LO spellcheck dialog components for reliable identification by ATs

2023-10-19 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155447

Michael Weghorn  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

--- Comment #2 from Michael Weghorn  ---
(In reply to Joanmarie Diggs from comment #0)
> Under the circumstances, here is my proposal to make things a bit better,
> both for Linux and for Windows: Add accessible object attributes to the LO
> spellcheck dialog components so that ATs could identify them. For instance:

>From what I can see, neither Gtk 4 nor Qt currently support setting object
attributes, but always return an empty set (Qt, [1]) or only report a very
limited set of predefined ones (Gtk 4, [2]).

I'm hesitant to implement something that only works for gtk3, so I tend to
think that implementing support in Gtk 4 and Qt would be a prerequisite in case
of depending on those attributes being present.

Maybe, an alternative might be to use the "AccessibleId" property of the
Accessible interface to identify it, and set that to the "id" attribute as
specified in the .ui file (cui/uiconfig/ui/spellingdialog.ui), currently (but
that could be adapted as needed):

* "SpellingDialog" for the dialog
* "suggestionslb" for the suggestions list
* "sentence" for the widget displaying the text/error

I haven't looked into that in detail yet, but from a first glance, it looks
like that should be doable with Gtk 3 and Qt (which uses the "full hierarchy
path" for the AccessibleId, so would probably have something like
"SpellingDialogsuggestionslb", but that could be
handled on Orca side.

Gtk 4 currently always reports an empty AccessibleId, but I could come up with
a MR suggesting to use the "buildable_id", which to me seems to fit with the
idea of what AccessibleId is there for.

> 
> 

For IAccessible2, that could still be mapped to an "accessible-id:;"
atttribute or somesuch if considered useful.

@Joanmarie: What do you think? Would that be helpful?


[1]
https://code.qt.io/cgit/qt/qtbase.git/tree/src/gui/accessible/linux/atspiadaptor.cpp?id=546208f0ff23819d216cbb5bf0b5daded79b454e#n1608
[2]
https://gitlab.gnome.org/GNOME/gtk/-/blob/7325121c63e5ab54d6cea483f932b60224146061/gtk/a11y/gtkatspicontext.c#L524-544
[3]

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 155447] Add accessible object attributes to LO spellcheck dialog components for reliable identification by ATs

2023-05-25 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=155447

Michael Weghorn  changed:

   What|Removed |Added

   Keywords||accessibility
 Ever confirmed|0   |1
 Blocks||101912
 Status|UNCONFIRMED |NEW
 CC||m.wegh...@posteo.de

--- Comment #1 from Michael Weghorn  ---
Sounds like a reasonable request to look further into.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=101912
[Bug 101912] [META] Accessibility (a11y) bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.