W3C home > Mailing lists > Public > public-html-a11y@w3.org > February 2014

Re: Call for Consensus - Last Call responses on longdesc extension

From: Matthew Turvey <mcturvey@gmail.com>
Date: Mon, 17 Feb 2014 13:33:24 +0000
Message-ID: <CAFp5+ArY=yW87oHQusQ1xY2Y7_2QSHmP8eVcY62uTpPJTZNYxw@mail.gmail.com>
To: Charles McCathie Nevile <chaals@yandex-team.ru>
Cc: "public-html-a11y@w3.org" <public-html-a11y@w3.org>
On 17 February 2014 11:04, Charles McCathie Nevile
<chaals@yandex-team.ru> wrote:
> On Thu, 19 Dec 2013 21:50:18 +0400, Matthew Turvey <mcturvey@gmail.com>
> wrote:

>> What The Spec Needs To Do
>> -------------------------
>>
>> The spec needs to define when longdesc should be used i.e. what
>> problem longdesc solves. People reading the spec should be able to
>> tell when to use a longdesc link, instead of a normal link. The spec
>> does not currently explain what longdesc is actually for, or when to
>> use it. Some possible answers include:
>>
>> 1. a longdesc link should always be used instead of a normal link when
>> the destination includes a description of the image
>>
>> 2. a longdesc link should be used instead of a normal link when [some
>> other criteria that needs to be defined in the spec]
>>
>> 3. a longdesc link and a normal link should be used together when
>> [some other criteria that needs to be defined in the spec]
>>
>> 4. a longdesc link should be used instead of a normal link when the
>> description is only needed by some AT-users [define criteria authors
>> can use to decide a description is only needed by some AT-users]
>>
>> etc

> When there is a description available for an image included through an
> image element.

OK great, thanks for clarifying. Let's get that added to the spec.

Suggested text:
"A longdesc link should be used when there is a description available
for an image included through an image element."

-Matt
Received on Monday, 17 February 2014 13:33:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:37 UTC