Spec for ToolTip accessibility changes (for WCAG 2.1) #4242
Conversation
ghost
requested review from
| Unless mentioned otherwise below, the tooltip is shown immediately and its size and position are governed by the placement properties described in [TO]. | ||
|
|
||
| ### Hover | ||
| A hover occurs when the mouse enters the parent element and stays there for a certain time, without any other activity. |
There was a problem hiding this comment.
In Xaml, tooltips show with touch while the parent item is pressed. As soon as the user lifts up their finger, the tooltip closes. Similar behavior to mouse hover but requires more effort by the user :) Feels like the correct touch behavior for WPF to use as well.
| The tooltip is opened after the hover time, whose value is a function of the `InitialShowDelay` and `BetweenShowDelay` properties, and whether another tooltip is already showing [TO]. | ||
|
|
||
| ### Keyboard focus | ||
| When you use keyboard navigation to move focus to the parent element, the tooltip opens. |
There was a problem hiding this comment.
This is only if the new ShowsToolTipOnKeyboardFocus property is set? But the other behaviors listed above are with/without that property?
(Just looking for clarifying text)
| You can override this behavior using the `ShowsToolTipOnKeyboardFocus` properties. | ||
|
|
||
| ### Keyboard shortcut | ||
| When the parent has keyboard focus, typing Ctrl+Shift+F10 opens the tooltip. |
There was a problem hiding this comment.
What happens if the app or the system has registered this key combo? Does the notification still reaches the app or this will be filtered out by the WPF framework? Is the app or the framework handling it first?
Also I assume we want this key combo to work for any app, written in whatever framework and language, so this hot key need to be identical across Microsoft products. Let's make sure we mention this to CELA.
There was a problem hiding this comment.
CELA defined this key combo, based on the implementation already in Office apps. So Office suggested this combo, CELA approved the suggestion. This key combination is coming from the overall platform-agnostic guidance doc.
There was a problem hiding this comment.
It comes from [FD], the spec that's driving "identical across MS products". CELA is probably the source.
ghost
locked as resolved and limited conversation to collaborators
5 participants
No description provided.