13667 2011-08-04 03:16:44 +0000 Title attribute is overloaded 2011-12-13 16:32:53 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED NEEDSINFO a11y P2 normal --- 1 gcl-0039 contributor cooper ian laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 52308 0 gcl-0039 2011-08-04 03:16:44 +0000 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. 53794 1 mike 2011-08-04 05:17:25 +0000 mass-move component to LC1 56387 2 cooper 2011-09-06 15:16:04 +0000 Bug triage sub-team thinks HTML A11Y TF should track this. 60206 3 mike 2011-11-20 15:28:55 +0000 (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? 60429 4 ian 2011-11-24 03:05:49 +0000 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