https://bugs.documentfoundation.org/show_bug.cgi?id=140762
V Stuart Foote <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected],
| |[email protected]
--- Comment #8 from V Stuart Foote <[email protected]> ---
Michael, thanks for the fix!
Caolán and Tomaž have kept after these facets of AT, but there are lots of
places in the UI that need similar rework (e.g. provision of SVX strings) to
make the widgets meaningful to AT--rather than just sounding generic item IDs.
(In reply to Michael Weghorn from comment #7)
...
> Therefore, from how I understand it so far, the case covered here is
> different from what tdf#113488 covers.
>
That is fair, bug 113488 is about a difference in accessible event & focus
handling between keyboard only navigation vs what happens on mouse over or
mouse click.
Here once triggered, the focus driven accessible events did sound with keyboard
movement--they just had no meaningful descriptions.
That is fixed now, but still have the issue of difference between mouse-over or
click versus keyboard focus.
Focus requiring a mouse action is detrimental to AT. Keyboard only movements
need to provide similar accessible event triggers. And that is the crux of bug
113488 -- never silent, and best to expose the more descriptive text with every
keyboard movement inside a widget.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
