This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The following NOTE section does currently occur after 4 pargraphs about how User Agents SHOULD or MAY handle the longdesc attribute: ]] Best practices for full descriptions of images are beyond the scope of this document, but there are many resources available.[[ Please, instead, move the above NOTE so that it occurs ommediately after the following paragraph: ]] Authors should put descriptions within an element which is the target of a fragment link (e.g. longdesc="example.html#description") if a description is only part of the target document. [[ Justification: * The cited NOTE section relates to authoring and should thus occur directly after the normative information on authoring. * It is particulary offputting that the cited NOTE section currently occurs directly after a paragraphs about how User Agents MAY treat invalid longdesc attributes. With the wrong glasses on, this could give the impression that is OK for authors to fill the content of @longdesec with textual content (rather than a URL).
Hmm. THe conflict here is whether to put the limited best practice notes into a group, or group them by audience (authors, user agents, ...) I'm happy to change the grouping to make it more audience specific. I'll try to do that for the next editors' draft which I hope to publish tomorrow.
(In reply to comment #1) > I'm happy to change the grouping to make it more audience specific. I'll try > to do that for the next editors' draft which I hope to publish tomorrow. Super!
This has been done as of https://dvcs.w3.org/hg/html-proposals/raw-file/0dd2e510d4e1/longdesc1/longdesc.html