https://issues.apache.org/ooo/show_bug.cgi?id=122455
--- Comment #5 from Andre <[email protected]> --- (In reply to V Stuart Foote from comment #4) > (In reply to Andre from comment #3) > > > Re general problems of tab order: I don't have the time to check each panel. > > But I am willing to make the necessary changes if somebody else has a > > concrete proposal, like the one for 1). > > > Understand, was planning on more systematically working through the entire > UI. Will update/reopen with any additional keyboard navigation issues I find. Great. I was hoping you would. > > > ... I have no reason to believe that this assumption is wrong. > > Therefore I will >not change the tab order in this panel (until I get > > convinced otherwise :-) > > Regards GTK wrapper navigation of the Styles & Formatting panel. Understand > it comes in as baggage with the existing frame <F11>, but the sidebar focus > "navigation" landing in the panel with the Paragraph toolbar and its tree > list active seems inconsistent for keyboard use of the sidebar. > Inconsistency impacts accessibility. > > So while it does not matter too much for GUI users of mouse navigation, for > keyboard navigation it would be more consistent to land on the Panel title > -> and <TAB> onto toolbar buttons (Paragraph would be expected as it is the > first on the toolbar), rather than dropping directly into the Paragraph tree > list. > > And landing focus on the Toolbar buttons then makes cursor navigation > between the Paragraph, Character, Frame, Page, List styles consistent. Again > GUI users are not affected as they point and click--keyboard users, > especially for AT require consistent behavior. > > Not clear to me how much of the Styles and Formatting panel is simple > wrapper of the <F11> GUI frame, but there do seem to be keyboard navigation > UX issues in existing GUI as well. You are right. It the panel is basically just a wrapper. Change the tab order of one and you change the tab order of the other as well. But this is not just a technical problem. Keyboard accessibility is not only an accessibility issue (in the sense of section 508). It is feature for all people who use the keyboard to accelerate their work. We have to find a compromise between consistency and speeding up your work flow. Maybe this is something that we should discuss on the dev list? -- You are receiving this mail because: You are on the CC list for the bug.
