I thought this was a recent regression, relating to current work, but it's not so putting back in backlog for more assessment. It looks like the title attribute was intentionally removed in bd8339865 (T264355@Jdrewniak do you remember the reason?

Moving to sprint board in order to group with other tooltip issues

Let's talk about this in estimation. My understanding is this is an intentional design decision to remove the tooltip - possibly as it's redundant (often the same as the placeholder text). I recognize it's different, but it's not clear to me what problem we'd be solving by restoring it. @alexhollender_WMF any thoughts?

In legacy Vector:

In modern Vector if we were to retain it:

@Suzukaze-c thanks for pointing this inconsistency out.

@Jdlrobson in legacy vector the tooltip seems to show the keyboard shortcut:

aside from exposing the shortcut I'm not sure what the value is, though maybe it's related to accessibility? @Volker_E @Sarai-WMDE @bmartinezcalvo

note that Google search has a similar tooltip:

Awaiting input about accessibility value.

My understanding is that we mainly use the title attributes for providing short descriptive text and instructions for accesskeys, I don't believe there's any other value besides that. Modern Vector has icons buttons, where the title attribute is slightly more useful, but in this case I believe it's mostly a matter of consistency with legacy Vector.

From an accessibility point of view 'title' attributes generally aren't recommended, they aren't read by most screenreaders and have poor browser support, among other issues. Not to say that's an argument to get rid of the title attributes, just that they dont add any value specific to accessibility (ideally we'd provide the same descriptive text and instructions via accessible tooltips rather than title attributes)

Agreed, from a pure accessibility perspective probably not. From a consistency point of view, if we feature this (seemingly power user) feature in other places (Vector 2022?) of the interface, why getting rid of it in some place without pain?
The value I see and I've mostly understood this is, that users simply get informed in a non-obstructed way about speeding up their user journey by using accesskeys. How many users are using it/learning to use it is on a different page without data.

In T291671#7751646, @Jdlrobson wrote:

T291671#7377209 @Jdrewniak do you remember why we removed it?

Line 69 of App.vue in bd833986599 features this comment /** The access key informational tip for search. */

Change 802820 had a related patch set uploaded (by Bernard Wang; author: Bernard Wang):

[mediawiki/skins/Vector@master] Add back search title to WVUI component

https://gerrit.wikimedia.org/r/802820

Change 802820 merged by jenkins-bot:

[mediawiki/skins/Vector@master] Add back search title to WVUI component

https://gerrit.wikimedia.org/r/802820

Test Result - Beta

Status: ✅ PASS
Environment: beta
OS: macOS Monterey
Browser: Chrome, Firefox
Device: MBP
Emulated Device:NA

Test Artifact(s):

QA Steps

✅ AC1: Search tooltip should appear after hovering over search field.