Thank you, I did not know.
Do you think this is an implementation or assistive technology issue or a standards issue? (Assuming it is desired that authors can use it without making sites inaccessible)
Is using a custom solution with JS a viable alternative?
The funny thing is I noticed this because the WCAG 2.2 page uses <abbr title> to explain what W3C stands for (see image, https://www.w3.org/TR/WCAG22/) and I was using a mobile device!
