https://bugs.documentfoundation.org/show_bug.cgi?id=107316
V Stuart Foote <vstuart.foote@utsa.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|medium |high
Status|RESOLVED |NEW
Keywords| |needsUXEval
CC| |cno@nouenoff.nl,
| |libreoffice-ux-advise@lists
| |.freedesktop.org,
| |philipz85@hotmail.com,
| |s.mehrbrodt@gmail.com,
| |szymon.klos@collabora.com
Resolution|DUPLICATE |---
See Also| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=10
| |2059
Ever confirmed|0 |1
Summary|Notebookbar keyboard |MUFFIN needs to provide GUI
|accessibility |keyboard access equal to
| |Menu and Toolbars
--- Comment #2 from V Stuart Foote <vstuart.foote@utsa.edu> ---
@Jay, Syzmon, Samuel, *
Repurposing this rather than reopening bug 102059
We need additional keyboard accelerator navigation. Only supporting the
*minimum* F6 cycling with <TAB> movements for keyboard navigation is limiting
the MUFFIN interfaces compared to Toolbar and Menus.
We are going to need mnemonic accelerators, and maybe even some assigned
shortcuts for the various Notebookbar GUI layout(s) to be comfortable for
keyboard and a11y users.
This in addition to finishing up work on bug 90195 an F10 shortcut for unhiding
the main menu bar.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 107316] MUFFIN needs to provide GUI keyboard access equal to Menu and Toolbars · 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.