- From: Mayank via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Jul 2023 00:20:00 +0000
- To: public-css-archive@w3.org
agree with @Westbrook and @mikemai2awesome. i think the work to make `title` attribute accessible should be done *before* any work on the styling side is even started. as it stands, the `title` attribute is entirely useless not because of its inability to be styled, but because of its accessibility issues. i would hate to see `::tooltip` finalized and shipped when the accessibility discussion is still in limbo, because it would still be entirely useless. --- Two more tangential points i would like to point out. If the `content` property is the only way to change the tooltip, then it would get in the way of both of these. 1. while dismissing tooltips on <kbd>esc</kbd> key does technically help satisfy [SC 1.4.13 "Dismissible"](https://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html), it is not optimal. [user research](https://youtu.be/lb0_v7D4kbs?t=1436) done by Sarah Higley has found that a ❌ button inside the tooltip works better. 2. there needs to be a way to indicate if the tooltip is part of the element's accessible name (primary label) or its description (supplementary text). - while this could potentially be achieved using `content: attr(aria-label)`/`content: attr(aria-description)`, this is severely limiting because there are better, more widely-supported ways to add labels/descriptions. -- GitHub Notification of comment by mayank99 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8930#issuecomment-1644814905 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 July 2023 00:20:02 UTC