https://bugs.documentfoundation.org/show_bug.cgi?id=163989
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression By| |Heiko Tietze CC| |heiko.tietze@documentfounda | |tion.org Keywords| |accessibility, bibisected, | |bisected, regression --- Comment #2 from Michael Weghorn <[email protected]> --- (In reply to Michael Weghorn from comment #1) > In any case, I agree that having a state-changed:showing(1, 0, 0) event for > a notification with no useful text doesn't sound like a good idea. Sending that event also when the label is empty happens since commit 48ba98a51f029cd14b5d982dab36eb581d40fef3 Author: Heiko Tietze Date: Wed Nov 29 14:29:57 2023 +0100 Resolves tdf#158412 - Don't show chevron in quick find bar https://gerrit.libreoffice.org/c/core/+/177523 is a potential fix to restore the previous behavior, but I don't know the involved code/logic for the search bar that well, so maybe Heiko has more thoughts there. A potential alternative might be to stop using the notification a11y role for that label and relying on the object:state-changed:showing event for that label for it to be announced and use an Announcement event directly, which was added to AT-SPI2 in https://gitlab.gnome.org/GNOME/at-spi2-core/-/commit/26835da29918be2c0da6c08fb70d893de22891d2 That would basically move the logic on when to (not) announce from Orca to LibreOffice itself. @joanie: Would using object:announcement be preferred over the current object:state:changed:showing logic or better to leave as is (and leave it to the screen reader to decide whether or not to announce the label text)? -- You are receiving this mail because: You are the assignee for the bug.
