Make the title attribute visible on keyboard focus
Reported by
da...@can-adapt.com,
Apr 5 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. create a mockup simple page with an anchor <a href="#" title="my test title">link text</a> OR Navigate to any page with a link that has a title element. 2. open page in Chrome 3. Tab to link What is the expected behavior? Title attribute should be visible on keyboard focus... not just as it is on hover What went wrong? The title shows up on hover but not on keyboard focus. Did this work before? No Chrome version: 65.0.3325.181 Channel: stable OS Version: OS X 10.13.3 Flash Version: WCAG 2.0 Requires all functionality to be available to keyboard users. The title attribute is not currently. The equivalent of hover for a keyboard user is focus. The lack of proper support for this is causing thousands of developers to implement resourse consuming custom tooltips to overcome this buggy behaviour in Chrome in order to conform with WCAG. Edge implements the title attribute properly.
,
Apr 10 2018
Thanks for filing the issue! @Reporter: could you please provide any sample test file/URL for reproducing the issue and bisecting this further in better way. Thanks!
,
Apr 13 2018
Here is the test page http://davidmacd.com/blog/chrome-title-bug.html
,
Apr 13 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 13 2018
,
Apr 16 2018
Able to reproduce the issue on reported chrome version 65.0.3325.181 and on the latest canary 67.0.3396.0 using Windows 10, Ubuntu 14.04 and Mac 10.13.1. Note: Considering titles not being shown over tab focus as an issue. As the issue is seen from M60(60.0.3112.0) considering it as Non-Regression and marking it as Untriaged. Requesting someone from Blink>Accessibility team to have a look into this.
,
Sep 7
Possibly reasonable, but low-priority feature request. > WCAG 2.0 Requires all functionality to be available to keyboard users. The title attribute is not currently. WCAG is a set of guidelines for web authors, not for user agents. This may be a good idea to consider implementing, but that justification doesn't work. Assistive technology like screen readers already expose the title attribute, and this is also trivially solved by a Chrome extension. I think that makes it a low priority. If we did decide to do this I think we'd want to coordinate with other browser vendors.
,
Sep 8
> Assistive technology like screen readers already expose the title attribute, and this is also trivially solved by a Chrome extension. I think that makes it a low priority. This is for keyboard users who are sighted, not screen reader users. > If we did decide to do this I think we'd want to coordinate with other browser vendors. Edge and IE have fixed this. To test, open IE 11 or Edge and hit the tab key on a control that has a title attribute... http://davidmacd.com/blog/chrome-title-bug.html |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by krajshree@chromium.org
, Apr 5 2018