This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://www.w3.org/mid/B6CB855C5769484F862F4FB2CCFA50F402D545A7@VHAISHMSGJ2.vha.med.va.gov Since the title attribute can be applied to almost any element, reliable means will need to be provided to allow AT users and those who do not use a mouse, to be able to access that advisory information without being hampered by it. Not having access to tooltips is occasionally problematic now, but not being able to access information such as source reference information for a paragraph when located in a title attribute on an element that cannot gain keyboard focus will be even more of an issue. Also, here "description of an image" is listed as advisory information, continuing the confusion about where "alt" is appropriate and where "title" should be used. The description of an image is not "advisory" it is descriptive. The description of the purpose of an image might be advisory. For instance the image of a printer being used to send to a printer, should have alt="print" or alt="printer" but title="Click this button to send to a printer". [split out from bug 13590]
Yes, browsers will have to do things correctly. Is there a problem with the HTML spec here?
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: <http://dev.w3.org/html5/decision-policy/decision-policy.html>. Status: Rejected Change Description: no spec change Rationale: Please address comment 1.
Moving to HTML A11y TF component.
As per what Anne probably meant. This is an implementation bug, not a spec bug.