IMHO also believe Variant 1 would benefit our Eve users who tend to customize their UI rather than taking defaults, and so benefit the majority of our users.
But it would be more complex for keyboard only users, and those dependent on a11y and assistive technology tools. The UI will always be driven from the keyboard by users. That facet requires explicit developer's attention to providing accessible events and sequencing of the controls to assure the new work flow(s) can actually be followed from keyboard. In addition developer must complete the widget/tool labeling and online help articles used for tooltips, and that a11y requires for annotation. While Variant 2 would be simpler to implement and less risky to fully complete, Variant 1 is the correct way to proceed--just be mindful of keyboard interactions and use without mouse/display. @Heiko, Bubli as GSOC mentor to Muhammet --please ensure keyboard/AT testing during development, and engage the keyboard and AT users during the QA process for use with ORCA, VoiceOver, and NVDA. Stuart -- View this message in context: http://nabble.documentfoundation.org/GSoC-17-Customization-tp4215466p4215811.html Sent from the Design mailing list archive at Nabble.com. -- To unsubscribe e-mail to: design+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted
