[Libreoffice-ux-advise] [Bug 69550] [UX] [a11y] Style keyboard shortcuts are undiscoverable

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=69550

--- Comment #9 from V Stuart Foote <vstuart.foote at utsa.edu> ---
Jay, *

(In reply to Yousuf (Jay) Philips from comment #8)
> (In reply to Tin Man from comment #0)
> > Style keyboard shortcuts are undiscoverable.
> 
> They are now discoverable with the introduction of the Style menu in 5.1.
> 

...

> 
> I propose closing this.

Having the Styles menu for Writer is a definite improvement (thanks Jay!). But
the menu in Writer is only assigning Paragraph and Character styles with
.uno:StyleApply actions. We can not style Frames, Pages or Lists from menu or
by short-cut/accelerator. 

Otherwise keyboard navigation does not seem to be fully resolved. Yes menu
elements have been done for Writer with additions to WriterCommands.xcu -- but
no similar menu with keyboard short-cuts/accelerators have been provided for
styling paragraphs/characters in Draw/Impress text blocks, nor in Calc cells.
The Format -> Styles in Calc is un populated. And the Format menu entries in
Draw/Impress do direct formatting of the drawing objects. 

Also, we've done nothing for Keyboard navigation in the Sidebar Styles &
Formatting (F11) deck, nor in the Sytles dropdown content panel of the
Properties deck.   In general for navigating the Sidebar we remain bound to
F10, F6 and a muddled mix of cursor and Tab movements. The very thing direct
short-cuts/accelerators would simplify.

So, IMHO don't see this as ready to close. Although it probably needs more
design and discussion of how best to provide full keyboard navigation for
Assistive Technology support.  

Stuart

=-ref-=
http://cgit.freedesktop.org/libreoffice/core/commit/?id=6c189a1eb90012789692344aa7dc418c7ec7f032

http://cgit.freedesktop.org/libreoffice/core/commit/?id=66a7292f2faf51cc0ba018771a5ab25e8d7b5929


As a suggestion for all interested--when assessing completeness of the UI
please try to navigate using just the keyboard (no mouse)--or better turn off
the display with reliance on just ORCA or NVDA or JAWS to sound your session
navigation. If you can't create useful documents without peeking we're not
meeting the needs of our Accessibility Tools dependent users. Likewise if
navigation is not clear consistent and concise across the modules.

-- 
You are receiving this mail because:
You are on the CC list for the bug.