Hey Michael. The accessible description field is meant to be end-user consumable. So if the strings in question are end-user consumable (as opposed to a solution for, say, automated testing), I think that's ok.
That said, if the tips are especially verbose, perhaps exposing them via help text instead would make sense?? --joanie On Wed, 2024-06-19 at 08:35 +0000, Michael Weghorn wrote: > Hey joanie, > > On 2024-06-19 09:54, Joanmarie Diggs wrote: > > Hey Michael. > > > > I just removed _generateDescription (not just the part you cited) from > > the soffice script so the default logic will now be used. If Orca starts > > finding and presenting unhelpful descriptions in LibreOffice, let's > > remove those descriptions from LibreOffice. > > > > https://gitlab.gnome.org/GNOME/orca/-/commit/62e8a08fe27883cb46443da8078850627660cf17 > > Great, thanks a lot! > > One challenge when cleaning up might be that extended tooltips (that can > be enabled at "Tools" -> "Options" -> "General" -> "Help" -> "Extended > Tips") currently (mis)use the accessible description field in .ui files > as well and we might want to keep those, but that's something for which > we'll have to find a solution anyway. > > Michael -- To unsubscribe e-mail to: accessibility+unsubscr...@global.libreoffice.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/accessibility/ Privacy Policy: https://www.documentfoundation.org/privacy
