Style keyboard shortcuts are undiscoverable. I'd suggest showing them to the right of the style name in the style combo box in a lighter color, similarly to how keyboard shortcuts are shown in menus.
Hi Mirek, (In reply to comment #0) > Style keyboard shortcuts are undiscoverable. F1, landing page > link to shortcuts .. > I'd suggest showing them to the right of the style name in the style combo > box in a lighter color, similarly to how keyboard shortcuts are shown in > menus. thanks - Idea looks fine. But do we have a metabug, or a overall project to create a plan before (suggesting to) impelment(ing) separate ideas? Cor
(In reply to comment #1) > Hi Mirek, > > (In reply to comment #0) > > Style keyboard shortcuts are undiscoverable. > > F1, landing page > link to shortcuts .. > > > I'd suggest showing them to the right of the style name in the style combo > > box in a lighter color, similarly to how keyboard shortcuts are shown in > > menus. > > thanks - Idea looks fine. > > But do we have a metabug, or a overall project to create a plan before > (suggesting to) impelment(ing) separate ideas? No. Given that there's very little developer interest in working on UX bugs, I see bitesized bugs as the only chance for getting anything solved. Do you have any suggestions on ways to get UX bugs solved?
Undiscoverable because they are not assigned. Beleive the Styles & Formatting probably should have an SytleCommand.xcu created, or at the least appropriate stanzas added to the GenericCommands.xcu configuration. In addition to UX issue this is a major Accessibility and keyboard navigation issue. Impacts the <F11> Sytles & Formatting Frame, as well as its rendering in the Sidebar. In an Accessibility context, "lighter color" is not a viable UX implementation, and is too far removed from the underlining used for accelerators assigned to Menus.
Removing comma from whiteboard (please use a space to delimit values in this field) https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Whiteboard#Getting_Started
The native accessibility bridges expose the lists of the 'Styles and Fomatting' <F11> pop-up panel when navigated with <TAB> and Cursor keys (U,D,L,R). But as noted there have never been 'accelerators' associated with any component of this toolbar panel. For accessibility it would be helpful if a consistent set of accelerators could be assigned to at least the major headings--e.g. the Paragraph, Character, Frame, Page and List styles. Also, it would probably be most functional if the 'accelerator' for each of these place active focus onto the panel list item of the currently active document cursor. Besides helping to encourage use of Style rather than Direct formatting in documents, this would greatly improve the work flow for keyboard users, notably folks needing Assistive Technology tool support. I.e. directly navigating onto the correct list item with a single keystroke, rather than multiple <TAB> and cursor movements listening for the right location.
Hi V Stuart, I just was about to close (mid air collision ;) ) this as duplicate of bug 62081 This since we discussed at the UX hackfest that keyboard shortcurts can be properly shown in split menus .. What do you think?
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval. Thank you and apologies for the noise
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.