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 5834 - <area alt=""> has no author-level conformance requirement
Summary: <area alt=""> has no author-level conformance requirement
Status: VERIFIED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: NoReply
Depends on:
Blocks:
 
Reported: 2008-07-04 19:00 UTC by steve faulkner
Modified: 2010-10-04 14:45 UTC (History)
5 users (show)

See Also:


Attachments

Description steve faulkner 2008-07-04 19:00:30 UTC
current wording of spec[1]:

"If the area element has an href attribute, then the area element represents a hyperlink; the alt attribute, which must then be present, specifies the text."  

proposed addition:

"the content of the alt attribute must be a brief description of the link target."

or words to that effect. 

[1] http://www.w3.org/html/wg/html5/#the-area
Comment 1 Ian 'Hixie' Hickson 2008-07-04 20:02:52 UTC
That would be wrong. For example, if the image is three digits in a triangle formation, and each digit is a link, and links 1 and 2 go to a page that says "you lost" and link 3 goes to a page that says "you win", you would want the alt="" attributes to be "1", "2", and "3" respectively, not "you lose", "you lose" and "you win". Thus the target page doesn't have much to do with what the links say in this case.
Comment 2 steve faulkner 2008-07-04 20:43:37 UTC
(In reply to comment #1)
> That would be wrong. For example, if the image is three digits in a triangle
> formation, and each digit is a link, and links 1 and 2 go to a page that says
> "you lost" and link 3 goes to a page that says "you win", you would want the
> alt="" attributes to be "1", "2", and "3" respectively, not "you lose", "you
> lose" and "you win". Thus the target page doesn't have much to do with what the
> links say in this case.


ok the point being that the alt must contain an appropriate text alternative, which is clearly not stated curently.

so however you want to word it the, proposal is to provide a normative statement in regards to the content of the alt attribute.
Comment 3 Justin James 2008-07-05 04:34:41 UTC
I think that this is a bad proposal for all of the reasons that we had a utter mess with @alt in general a few months ago. Why should @alt for area describe the destination? Why should/could it not describe the image being used for the image map? Or something else entirely, such as, "please click the color that you like the best?"

Furthermore, why *must* @alt be omitted for area without @href? Again, why could it not simply be used to describe part of the image?

Folks, this topic keeps going around and around like a Canadian dime in a US vending machine. You can't have your cake and eat it too. Either make a bunch of granular attributes to *replace* @alt (such as @destination-description, @long-description, @short-description, etc.), or stop trying to dictate the contents of an immensely general attribute.
Comment 4 Ian 'Hixie' Hickson 2008-07-05 06:44:18 UTC
Yeah I guess the current text isn't really rigorous, it should give an author-level requirement for the alt="" attribute's value. I'll add something.
Comment 5 Ian 'Hixie' Hickson 2008-07-24 08:53:19 UTC
Added in r1932.
Comment 6 Maciej Stachowiak 2010-03-14 13:15:07 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, 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

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.