https://bugs.documentfoundation.org/show_bug.cgi?id=170274
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Summary|Orca screen reader does not |Orca screen reader does not |read formattig changes when |read formatting changes |applied |when applied Ever confirmed|0 |1 CC| |[email protected] --- Comment #2 from Michael Weghorn <[email protected]> --- Not(In reply to Darrell Bowles from comment #0) > Description: > When applying formatting such as justifications, bold or anyother > formatting changes, Orca screen reader does not notify me when I have > applied the changes. > > Steps to Reproduce: > 1. First start orca by pressing super+alt+s. > 2. write someting like, this is a test and press enter. > 3. Select the line and then press control b. > 4. Orca does not say anything.1. Unless anything specific is missing from the LibreOffice side, that to me sounds like logic that might best be implemented in Orca instead of LibreOffice. The NVDA screen reader on Windows for example announces such changes. It does so by intercepting the corresponding keyboard shortcuts, sending them to the application and then announcing changes to the state of the relevant UI (e.g. the "Bold" toggle button) in the toolbar if it happens within a certain amount of time after sending the keyboard events. I currently don't know whether that would be a viable approach for Orca as well (e.g. whether it has such infrastructure to handle locale-specific keyboard shortcuts...) or whether a different approach would make more sense there. @Joanie: Do you possibly have any thoughts on that? For reference: NVDA commits implementing the feature there. https://github.com/nvaccess/nvda/commit/46a343685247ed7d1adfb737716590ec4be456a0 https://github.com/nvaccess/nvda/commit/20bdb39e6f83ef87726817cb1bad31fa7b0f73cb https://github.com/nvaccess/nvda/commit/8827e60ad494f0c3121364f01301cde2305a784a https://github.com/nvaccess/nvda/commit/661da4949f0205e0e25ac8b40ee5c30bf294e37c -- You are receiving this mail because: You are the assignee for the bug.
