Bug 87157 - Buttons for uno commands grouped as Toolbars missing keyboard navigation (a11y)
Summary: Buttons for uno commands grouped as Toolbars missing keyboard navigation (a11y)
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: a11y
  Show dependency treegraph
 
Reported: 2014-12-09 15:09 UTC by V Stuart Foote
Modified: 2016-10-25 20:07 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description V Stuart Foote 2014-12-09 15:09:46 UTC
Multiple button wigets, with linked uno commands (mostly to set object mode), are assembled into toolbars--e.g. Basic Shapes now on the Standard toolbar. The toolbars can be activated/opened with keyboard movement--but then the individual buttons (mostly modal selections) can not be navigated and selected with keyboard cursor or tab movements. A UI and a11y issue, as actions performed with mouse movement and selection should mostly be supported with keyboard actions as well. Toolbar navigation is pretty fundamental UX.

arrowshapes.xml
basicshapes.xml
calloutshapes.xml
drawbar.xml
flowchartshapes.xml
starshapes.xml
symbolshapes.xml

/core/chart2/uiconfig/toolbar/
/core/reportdesign/uiconfig/dbreport/toolbar/
/core/sc/uiconfig/scalc/toolbar/
/core/sd/uiconfig/sdraw/toolbar/
/core/sd/uiconfig/simpress/toolbar/
/core/sw/uiconfig/sglobal/toolbar/
/core/sw/uiconfig/sweb/toolbar/
/core/sw/uiconfig/swform/toolbar/
/core/sw/uiconfig/swreport/toolbar/
/core/sw/uiconfig/swriter/toolbar/
/core/sw/uiconfig/swxform/toolbar/

Draw has some additional toolbar groupings
connectorsbar.xml
linesbar.xml
etc.
Comment 1 V Stuart Foote 2014-12-09 15:26:15 UTC
Sorry for the noise, if you enter into the toolbar correctly with an <F10> and multiple <F6> progressions to reach the correct toolbar, and then cursor/tab onto the split button for the grouped toolbar. On open of the grouped toolbar--cursor (R,L) does traverse the buttons. <TAB> and cursor (U,D) do not.

Not ideal, but it does work. I think the missing cursor Down tripped me up. Sorry for the noise.