https://issues.apache.org/ooo/show_bug.cgi?id=122380
--- Comment #16 from V Stuart Foote <[email protected]> --- (In reply to Andre from comment #15) > @Stuart: In the bug description you write > "Otherwise while the tool bars can now be reached with keyboard navigation, > they are mute as to function." > I am not sure what that means. Can you explain? Simply that as in the the example, positioning with <F6>, the cursors, and the <TAB> key it is possible to navigate using keyboard only to the Properties -> Paragraph content panel and with series of <TAB>'s to position focus into each of the Indent toolbar widgets. Which is good and a change in that with earlier builds once in a content panel you were keyboard trapped and required a mouse click to be able to exit. The issue then became providing XAccessible role and accName details for AT, sounds like you've got that on track. On that,my note above to Steve Yin about the IAccessible2 and ATK, NSAccess bridges is that all will be dependent on what roles are assigned now to each GUI element, and what "annotation" of the element is made available through UNO Accessibility API (UAA). My hope is that you and Steve can collaborate to get the GTK objects "instrumented" with needed hooks, and going forward can fully incorporate changes to the accessibility APIs that have all continued to develop since UAA was laid down. There are additional role mappings for each API that will require the counterpart UAA be refined, the ATK AT-SPI2 is the furthest developed--but all three "bridges" will need to have comparable treatment including adjusting the core UAA roles to take advantage of the new APIs. Handling tables for example. There are a number of pending AT enhancement issues in Bugzilla. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
