https://bugs.documentfoundation.org/show_bug.cgi?id=109425
--- Comment #39 from V Stuart Foote <vstuart.fo...@utsa.edu> ---
@Andreas, Jim, *
So testing on Windows 10 Home 64-bit en-US with NVDA 2019.2 and todays TB77
Version: 6.5.0.0.alpha0+ (x64)
Build ID: 790b5de8941d8f8d98c73ed1343289d7220211ad
CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: default; VCL: win;
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
The additional GTK Focus events have restored reasonable keyboard navigation to
the NB, had a few sequencing issues within groupings, but so much closer now.
Thanks!
But for some reason the focus A11Y 'accessible events' are not fired when
advancing through the NB in its nested position in the app frame. But if you
reduce the width of the frame, collapsing the NB, the popup bar exposed with
the 'chevrons' exposes all of the accessible events.
What is different between controls held on the NB, versus the same controls
held in the overflow 'chevrons' popup that allows the UNO controls 'accessible
event' to fire?
And otherwise, continue to have issues with a non-functional F10 & F6 movements
when the main menubar is not exposed. Seems too fragile, and prone to losing
track of position in the UI. No recovery with keyboard, requiring a blind
mouse click into the document canvas to recover focus.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
