https://bugs.freedesktop.org/show_bug.cgi?id=70637
--- Comment #15 from V Stuart Foote <[email protected]> --- @Foss (In reply to comment #14) > V Stuart Foote: Do I understand Comment 11 correctly, that you suggest tab > should be moving from one box to the next and the remaining navigation > should be done with the arrow keys? Yes, the migration of GtkWidget UI based GUIs as used now for the StartCenter present new challenges for the devs as they need to implement logical keyboard navigation in addition to a mouse-driven GUI. A current fully implemented example would be the keyboard behavior in the GtkWidget based SideBar where landing on the Deck with <F6> movement a <TAB> enters the Title bar of the first content panel on the deck. Cursor <U,D> moves to next content panel title bar, or <TAB> enters the content panel, and additioonal <TAB> progress to command groupings, Cursor <U,D,L,R> position on specific buttons and list objects, <Enter> activates. <ESC> -- leaves current content panel and enters its title bar, <U,D> moves to next content panel title. This layout diagram from AOO gives an idea of the sidebar GtkWidget elements that must be navigable. https://wiki.openoffice.org/wiki/File:SidebarNames.png > > If so, I totally agree with that. Special commands like "shift + tab" are > barely known and won't be used a lot. In reality they are well known to keyboard based users. Because for consistency of use, keyboard navigation is fairly well standardized in the OO/AOO/LibreOfice family. As it is critical for support of Assistive Technologies it has to be well documented and is a major component of the QA process with each release cycle. Fortunately the norms are fairly well documented as noted in these LibreOffice references: https://help.libreoffice.org/Common/Shortcuts_Accessibility https://help.libreoffice.org/Common/General_Shortcut_Keys_in https://help.libreoffice.org/Writer/Shortcut_Keys_for_Writer https://help.libreoffice.org/Writer/Navigating_and_Selecting_With_the_Keyboard and similar for other modules. Divergence from these UX norms require QA actions to adjust the program or change documentation. >... So how to proceed? Should we open a > separtate bug for that? Already open as bug 71764, I've added you to CC for it. Stuart -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
