https://bugs.documentfoundation.org/show_bug.cgi?id=108458
--- Comment #7 from V Stuart Foote <[email protected]> ---
(In reply to Yousuf Philips (jay) from comment #6)
> Sorry Stuart, didnt fully get the a11y issue you were trying to address.
> Where you saying that in addition to whatever tooltip that is read by the
> screen reader, some additional instructions should be read?
>
What I'm asking is that however the labeling is reworked--that function for
a11y be taken into account and made consistent as well.
For a11y we probably should be reading the descriptive tooltip for menu and
button objects. But currently 5.4.3, with keyboard movements (F10 -> F6 ->
<Tab/ShiftTab>; or <UP,DOWN,LEFT,RIGHT>) just the short button/menu label is
exposed.
This contrasts to mouseover behavior which gets the descriptive tooltip--or the
extended tooltip pulled from offline local help when installed (and
auto-enabled when an AT is in use).
Differences between keyboard and mouseover event triggers are probably
unavoidable--but as the labeling controls what is exposed to AT, it needs to
considered as well while reworking label structure--and ideally make keyboard
and mouseover expose the same tooltip/enhanced tooltip when traversing menus,
context menus, and toolbars when Assistive Technology tool support is enabled.
--
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
