[Libreoffice-bugs] [Bug 109425] Libreoffice Notebookbar is not exposing accessible events needed for screen reader users.
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Sat Nov 16 05:55:10 UTC 2019
https://bugs.documentfoundation.org/show_bug.cgi?id=109425
V Stuart Foote <vstuart.foote at utsa.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=10
| |7343
Priority|medium |high
CC| |raykowj at gmail.com
Severity|normal |major
--- Comment #13 from V Stuart Foote <vstuart.foote at utsa.edu> ---
On Windows 10 Home 64-bit en-US (1903) with NVDA 2019.1 and
Version: 6.3.3.2 (x64)
Build ID: a64200df03143b798afd1ec74a12ab50359878ed
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win;
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
and current master/6.5.0
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 8c85782bbe46963e2be32c3cb406982f1790fc2f
CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win;
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
Issue remains. And, if anything triggering of accessible events for a11y of the
NB has gotten worse.
Controls of the Notebookbar UI do not respond with accessible events. F10, F6
cycling is spotty. And there are keyboard navigation traps moving between
control groupings. While no movement on bug 107343, leave a11y dependent users
with no way to restore Main menu bar and its sounding keyboard navigation.
The Contextual single Notebookbar mode can not be reached with keyboard only
navigation.
In short--it is not suitable to task and really needs dev attention.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20191116/8b0dae6d/attachment-0001.html>
More information about the Libreoffice-bugs
mailing list