Design/Meetings/2017-01-19

Link
http://nabble.documentfoundation.org/Minutes-of-the-Design-Hangout-2016-Jan-19-tc4205777.html

Minutes
Jan 19, 2017; 6:19am Heiko Tietze-2 Minutes of the Design Hangout: 2016-Jan-19

Present: Jay, Tomaz, Szymon, Heiko

* Bookmark spelling/grammer findings + https://bugs.documentfoundation.org/show_bug.cgi?id=93073 + maybe a full overhaul of the dialog is needed but the idea sounds reasonable (Heiko) + don't see the point of adding it to the dialog, as comments/bookmark can be done right now as the dialog is modal (Jay) + looking for more opinions (Heiko) * Styles in Draw/Impress + https://bugs.documentfoundation.org/show_bug.cgi?id=94369 + https://bugs.documentfoundation.org/show_bug.cgi?id=101756 + Topic for 5.4? > absolutely (Jay) + Ideally create a mockup and a couple of predefined styles and find a dev (Jay) + Update the existing graphic styles (Tomaz) + textbox vs. shapes issue is styles are applied (Tomaz) + preview needed in sidebar (Heiko) + code base needs rework, e.g. no Ui file today (Tomaz) => keep it in the backlog

* Broken links + https://bugs.documentfoundation.org/show_bug.cgi?id=105187 + to interrupt the workflow by warnings is bad + Use message dialog, infobar, or (newly to introduce) callouts? + another option is to have a "don't show anymore" checkbox with the ordinary confirmation box, similar to the 'confirm file format' dialog when saving in non-odf (Jay) + like callout idea most and there is need for it (Tomaz) + infobar is rather for the whole document; and when it fades-out automatically the document would jump up  + Excel shows a small exclamation icon with a context menu for minor issues like numbers vs. text

* Accessibility guideline + http://nabble.documentfoundation.org/Guideline-for-navigation-tt4205277.html + https://bugs.documentfoundation.org/show_bug.cgi?id=100898 (was the reason to start this discussion) + Solution 1 (that's my understanding of keyboard navigation yet it's not the current status): + Navigate on the top level UI hierarchy per F6. Start with the main menu, followed by the open toolbars, and finally the sidebar. + Use arrow keys to navigation within main menu and toolbars, and execute the function per Enter. + Within the sidebar use arrow keys to traverse the tabs (e.g. Properties, Styles, Gallery etc.). Press Return to enter the deck. + Within the deck cycle through the content panels (e.g. Styles, Character, Paragraph etc.) per ctrl+tab/shift+ctrl+tab. + Within the content panel navigate between controls using tab/shift+tab (e.g. Alignment, Bullets,      Numbering etc. at Properties > Styles). + Use arrow keys to access controls that are part of a collection such as toggle buttons, lists, dropdowns (e.g. bold, italic, underline etc.). + Label all decks, content panels, controls/collections and provide mnemonic accelerator. + Go back to the document per Escape. + Solution 2 (what we have today and what Stuart describes in comment 5 of tdf#100898): + Navigate on the top level UI hierarchy per F6. Start with the main menu, followed by open toolbars, and finally the sidebar. + In the sidebar cycle through deck title, content panels, and sidebar decks using the arrow keys. + Enter the sidebar deck per return, or cycle through the content including the close button per tab/shift+tab. + Use arrow keys to access controls that are part of a collection such as toggle buttons, lists, dropdowns etc. + Make the content panel title part of the tab sequence to allow exit. + Label all decks, content panels, controls/collections and provide mnemonic accelerator. + Go back to the document per Escape. + definitely needs a guideline (Jay), and there was another bug.... + sidebar close/minimized should be taken into consideration (Jay) + Decks should be part of the F6 hierarchy meaning F6 lands at the deck (when it's open) and pressing F6 again goes to the tabs (Jay) => will create a gdoc for the discussion (Jay) https://docs.google.com/document/d/1oKabPLLVe9s53i475W1-v0QA7cxc_0oT0qfVr68KWjM/edit?usp=sharing