https://bugs.documentfoundation.org/show_bug.cgi?id=113488

Michael Weghorn <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #1 from Michael Weghorn <[email protected]> ---
(In reply to V Stuart Foote from comment #0)
> A rework of label structure for menus, context menus and toolbar button
> labels is being looked at for bug 108458. Perhaps in  conjunction with that,
> some structural change to facilitate use of tooltip/extended tooltips with
> keyboard navigation might be implemented.

I came across tdf#108458 in the context of
https://gerrit.libreoffice.org/c/core/+/136722 (v1), which then brought me here
again.

I don't really understand what the exact intention/request here is:

Is it to have the tooltips read out by default by screen readers when focusing
an item using the keyboard, e.g. by having them in the accessible name (or
accessible description)?

If so: At least Orca and NVDA have an option in their settings to announce
tooltips also, so I'm wondering whether it shouldn't be dependent on that
option whether or not tooltips are announced.

Since, IIUC, tooltips can contain rather long help texts, I tend to think that
not all users would want to have them announced every time (in particular when
experienced with the functionality currently being used), but a short label
might be enough then?
(And it would hopefully be possible to press some keyboard shortcut to have the
screen reader announce the tooltip on demand, but I don't know whether that's
currently implemented in the screen readers. Or is it, but LO doesn't provide
the information when the UI element has been accessed using the keyboard, as
opposed to when mouse-hovering over them?)


@Stuart: Could you possibly clarify a bit further what the request in this
ticket is (maybe also giving an example scenario of how that would be used)?

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to