This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13725 - enable AT users to have access to contents of the title attribute (tooltip text)
Summary: enable AT users to have access to contents of the title attribute (tooltip text)
Status: RESOLVED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y Task Force (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: This bug has no owner yet - up for the taking
URL: http://www.w3.org/mid/B6CB855C5769484...
Whiteboard:
Keywords: a11y
Depends on:
Blocks: 13590
  Show dependency treegraph
 
Reported: 2011-08-10 03:12 UTC by Michael[tm] Smith
Modified: 2016-04-07 14:51 UTC (History)
8 users (show)

See Also:


Attachments

Description Michael[tm] Smith 2011-08-10 03:12:59 UTC
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]
Comment 1 Tab Atkins Jr. 2011-08-10 15:13:14 UTC
Yes, browsers will have to do things correctly.  Is there a problem with the HTML spec here?
Comment 2 Anne 2011-08-15 16:47:54 UTC
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.
Comment 3 LĂ©onie Watson 2014-06-26 11:22:50 UTC
Moving to HTML A11y TF component.
Comment 4 Charles McCathieNevile 2016-04-07 14:51:18 UTC
As per what Anne probably meant. This is an implementation bug, not a spec bug.