W3C home > Mailing lists > Public > public-html@w3.org > April 2011

Re: longdesc spec text

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Tue, 26 Apr 2011 13:33:36 -0500
Message-ID: <BANLkTi=kxk8WMmV5dcH5k47pQ70zxQkRPA@mail.gmail.com>
To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Cc: Geoff Freed <geoff_freed@wgbh.org>, Jan Richards <jan.richards@utoronto.ca>, W3C WAI-XTECH <wai-xtech@w3.org>, HTMLwg <public-html@w3.org>
Hi Ben,

> So something like:
>   The requirements on the alt attribute's value are described in the
> next section.
>   Some images benefit from a long text alternative that is either too
>   long to be included in the main flow of the document or requires
>   structured markup that cannot be included in an @alt attribute. Such a
>   long text alternative of the image, if it has one, may be referenced in
>   the longdesc attribute.
>   If the longdesc attribute is present, it must be a /valid URL
>   potentially surrounded by spaces/
> (http://dev.w3.org/html5/spec/urls.html#valid-url-potentially-surrounded-by-spaces).
>   To obtain the corresponding long text alternative link, the value of
>   the attribute must be resolved relative to the element. The link must
>   point to either a different document from the image or a /fragment/
> (http://dev.w3.org/html5/spec/history.html#the-indicated-part-of-the-document)
>   of the same document that does not contain the image. User agents
>   should allow users to access long text alternatives.
>   The longdesc IDL attribute must reflect the element's longdesc content
>   attribute.

Thank you very much for this, Ben.

So can people live with this? All comments and ideas for improvement
are very welcome.

We could put the user agent material in the rendering section. Thoughts?

Best Regards,
Laura L. Carlson
Received on Tuesday, 26 April 2011 18:34:03 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:36 UTC