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 13667 - Title attribute is overloaded
Summary: Title attribute is overloaded
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: contributor
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2011-08-04 03:16 UTC by Greg Lowney
Modified: 2011-12-13 16:32 UTC (History)
7 users (show)

See Also:

Attachments

Description Greg Lowney 2011-08-04 03:16:44 UTC 
There is concern that the title attribute is overloaded with too many meanings. This prevents automation tools such as accessibility aids from distinguishing between to determine whether and how to present them to the user. There are also cases where the information may be better suited to rich content than to a simple text string, and may not be appropriate for the way existing browsers expose title attributes. Several specific bugs have been entered about different uses, but this bug covers the broad issue.
Comment 1 Michael[tm] Smith 2011-08-04 05:17:25 UTC 
mass-move component to LC1
Comment 2 Michael Cooper 2011-09-06 15:16:04 UTC 
Bug triage sub-team thinks HTML A11Y TF should track this.
Comment 3 Michael[tm] Smith 2011-11-20 15:28:55 UTC 
(In reply to comment #0)
> Several specific bugs have been entered about
> different uses, but this bug covers the broad issue.

If other more specific bugs have already been filed, what particular change to existing spec text are you proposing as a resolution for this bug itself?
Comment 4 Ian 'Hixie' Hickson 2011-11-24 03:05:49 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: Did Not Understand Request
Change Description: no spec change
Rationale: see comment 3