What problem would this solve? Looking at a handle of websites [1], this doesn't seem to be a common web pattern and I'd worry this would just cause confusion to screen readers.

[1] news.bbc.co.uk, github.com, twitter.com, facebook.com, google.com, amazon.com

@Jdlrobson I agree that sometimes this policy is not implemented in the ordinary case, but in the case of logo change, nearly always a tooltip is shown like google doodle. I think it should be implemented as a "potential capability". I mean it can be implemented as an "option", that is, you "can" show a tooltip or leave it without any tooltip.

Screenreaders don't benefit from tooltips via title. For many years unchanged. While in read mode it gets expanded, in common user behaviour tab mode, it won't. Some resources:

• https://silktide.com/blog/i-thought-title-text-improved-accessibility-i-was-wrong/
• https://www.mediacurrent.com/blog/dont-rely-title-attribute-accessibility-seo

I wouldn't recommend using the title attribute. But it's possibly better to ask an avid user like @Graham87 if he would miss the “Visit the main page” expansion in the rare cases for the banner Wikipedia logo link.

Indeed, the tooltip wouldn't be helpful for screen reader users. I'm OK with the lack of tooltip in Vector2022 as it is (I just tested it).

And what is shown if the images are prohibited by the browser?

@Iniquity: If you set your browser not to show images, that is nothing to fix by adding a tooltip...

In T306339#7955531, @Aklapper wrote:

@Iniquity: If you set your browser not to show images, that is nothing to fix by adding a tooltip...

Thanks for your screen! It just seems to me that adding a tooltip to this would be useful.

@Jdlrobson Hi, but in my opinion the textual cause of a change in the Wikipedia logo should be strictly tooltipped (for example, the cause of change of the logo for reaching a milestone is tooltipped to clarify that).