https://bugs.documentfoundation.org/show_bug.cgi?id=97313
--- Comment #16 from zahra <nasrinkhaksar3@gmail.com> ---
(In reply to Buovjaga from comment #15)
(In reply to zahra from comment #14)
hello.
i cant use safe mode because at least its not easy for blind people to use
it in the windows.
safe mode is not accessible or easy to use in previous versions of windows.
Just to be clear: I am not talking about the Safe mode of Windows, but
LibreOffice. It is a new feature in 5.3.
is it accessible for blind users?
but about safemode in windows, its for windows 8 and later accessible for blind
users.
how about the new feature in libreoffice 5.3?
could you please try nvda screen reader and report the result?
maybe it problem only occures on windows xp and maybe general for different
versions of windows.
but i only tested on xp and cant access to newer versions of windows.
you can download and test nvda 2016.4 from this link:
https://www.nvaccess.org/files/nvda/releases/2016.4/nvda_2016.4.exe
as i mentioned, i only use windows dialog for openning and saving in
libreoffice and dont use libreoffice dialog.
i mean the option in general setting.
but the problem only happens in windows dialog, not libreoffice.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 97313] Freezes using NVDA screen reader when I want to open a file by using control+o or in the file menu · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.