https://bugs.documentfoundation.org/show_bug.cgi?id=158522
--- Comment #2 from Petr Pařízek <[email protected]> --- Thanks for bringing this to my attention. I didn't know that this was a JAWS bug. And yes, I'm currently running an older version of JAWS. At this time, I can't run the newer version of JAWS so I can't test it for you right now. Had I known that it was fixed in a newer JAWS version, I wouldn't have reported it as a LO bug in the first place. For me a viable solution then is to keep using LO 7.4.7.2 and switch to a newer LO version when I'm able to run a newer JAWS version. (In reply to Michael Weghorn from comment #1) > What JAWS version are you using? > > Your descriptions sounds the same as what was reported on the accessibility > mailing list earlier: > https://listarchives.libreoffice.org/global/accessibility/msg01022.html > > That was a bug in JAWS: > https://listarchives.libreoffice.org/global/accessibility/msg01023.html > > This should be fixed in current JAWS versions, s. David's reply on the > mailing list: > https://listarchives.libreoffice.org/global/accessibility/msg01029.html > > Quoting from there: > > > Hello. As of yesterday JAWS 2023 is now reading text in the manner expected > > when navigating a > > Writer document using arrow key navigation. From the changelog: > > Resolved an issue with JAWS not reading text entered into a document in > > LibreOffice Writer. > > https://support.freedomscientific.com/Downloads/Fusion/FusionWhatsNew#enhancements > > Can you please retest whether this works as expected with the latest JAWS > version? -- You are receiving this mail because: You are the assignee for the bug.
