Summary: | The accessible name of the spreadsheet document should not be its URL | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Joanmarie Diggs <jdiggs> |
Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEEDINFO --- | ||
Severity: | normal | CC: | m.weghorn |
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=159659 | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 36549 |
Description
Joanmarie Diggs
2023-11-01 16:24:13 UTC
Thanks for your bug report and sorry for coming up with a lot of questions for now. (In reply to Joanmarie Diggs from comment #0) > Expected result: The name should not be the URL. Do you have any suggestion what the name *should* be instead? > Accessible names should be short and meaningful. Exposing the URL should be > done via the Document interface and not the name. Can you point to a specification/documentation describing how to do that correctly? Looking at the XML spec of the AT-SPI Document interface [1], that interface has `GetAttributes` and `GetAttributeValue` methods which seem to be the most likely candidates, but what attribute name should be used? From what I can see, LO currently doesn't have an equivalent for the AT-SPI Document interface, and neither Gtk 4 nor Qt provide a way to do so, only Gtk 3 does (AtkDocument). From a first glance, I also didn't see anything equivalent for UIA or NSAccessibility/macOS, which might make it harder to argue that Qt should be adding an equivalent. Since I didn't have to do with it at all yet: Could object attributes for the document object be a potential alternative? (As described in bug 155447 comment 2 in more detail, Gtk 4 and Qt currently also don't currently seem to support object attributes, but my first impression is that it *might* be easier to argue for adding those, but I might be wrong.) > Impact: I'm on a mission to eliminate all of Orca's sad hacks. :) (...) That generally sounds like a great idea! :) And it also fits well with my plan to make LO more compliant with the platform specifications/expectations. :-) One of the main challenge I ran into so far is that I didn't find good documentation for the supported/expected attributes etc. for AT-SPI. For IAccessible2 there are [2] and [3]. Is there anything similar for AT-SPI? Or would it make sense to start something like this and properly document things, e.g. in the at-spi2-core repo where other documentation is being added? (What I did so far was mainly looking into what the gtk3 VCL plugin of LO and the Gtk library currently do, and what Orca does/expects, but it's IMHO not great to have to do that every time and the different implementations also don't always agree/match...) [1] https://gitlab.gnome.org/GNOME/at-spi2-core/-/blob/7cc4cee53ddbd22631fd110f0e5ce045dec2e411/xml/Document.xml [2] https://wiki.linuxfoundation.org/accessibility/iaccessible2/textattributes [3] https://wiki.linuxfoundation.org/accessibility/iaccessible2/objectattributes I asked for the AtspiDocument support here: https://gitlab.gnome.org/GNOME/gtk/-/issues/6197 The generic object attribute is here: https://gitlab.gnome.org/GNOME/gtk/-/issues/6196 Let's see what they say. Thanks! (In reply to Joanmarie Diggs from comment #2) > I asked for the AtspiDocument support here: > https://gitlab.gnome.org/GNOME/gtk/-/issues/6197 > > The generic object attribute is here: > https://gitlab.gnome.org/GNOME/gtk/-/issues/6196 > > Let's see what they say. Thanks! Thanks! |