- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Mon, 2 May 2011 16:16:19 +0200
- To: Laura Carlson <laura.lee.carlson@gmail.com>
- Cc: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, W3C WAI-XTECH <wai-xtech@w3.org>, HTMLwg <public-html@w3.org>, Charles McCathieNevile <chaals@opera.com>, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Laura Carlson, Mon, 2 May 2011 06:41:13 -0500: > Hi Benjamin and everyone, > >>> I put your version of the spec into the spec text template [1], adding >>> one additional paragraph derived from HTML 4. It is: >>> >>> "Since an img element may be within the content of an a element, the >>> user agent's mechanism in the user interface for accessing the >>> "longdesc" resource of the former must be different than the mechanism >>> for accessing the href resource of the latter." >>> >>> This would make the logo and lightbox use cases possible. That do you >>> think? Ideas to improve that paragraph? >> >> My suggested text already says that UAs SHOULD provide access to the >> long text alternative. I don't believe more normative text is necessary. >> I do think that some advice about nesting would be useful, but I think >> it's best reserved for the "Rendering" section. >> http://dev.w3.org/html5/spec/rendering.html#links-forms-and-navigation > > Okay. Thanks Ben. I pulled that paragraph out of the spec text. > http://www.d.umn.edu/~lcarlson/research/ld-spec-text2.html > It can go into the rendering section unless people think that isn't a > good idea. Rendering issues should be part of the change proposal. No need to pull it out of spec text - just say where it should go. -- Leif H Silli
Received on Monday, 2 May 2011 14:20:03 UTC