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

Re: Clarification of rational for deprecation of @longdesc and @summary

From: Joshue O Connor <joshue.oconnor@cfit.ie>
Date: Mon, 18 Feb 2008 13:52:52 +0000
Message-ID: <47B98DB4.7050909@cfit.ie>
To: Richard Schwerdtfeger <schwer@us.ibm.com>, Ian Hickson <ian@hixie.ch>, HTML WG <public-html@w3.org>, public-html-request@w3.org

Richard Schwerdtfeger wrote:
> If wai-aria goes in we have an aria-describedby property which can
> reference an area of the document allowing for the prose to be associated
> with the image. longdesc is almost never used as people want to use the
> same prose in the original document.

While using the described by property to do just as you outline sounds
great, use of @longdesc is slightly different is it not? As you know
often the @longdesc text is hidden from sighted users and may not be a
part of the main page content. The @longdesc contents are then used to
give more detailed and in depth descriptive prose etc. So this
supplements the image and may not always be found in the main part of
the text.

While using the described by property to do this may in some cases be
Ok, I think a more elegant implementation of @longdesc may suffice. This
would not be the case if the requirements for this or another property
were expanded. I think the problem with @longdesc is how it is currently
implemented, not really what it was flawed in its conception or because
it  is failing to be useful.

If the contents of @longdesc could therefore be buffered or pre-loaded
and then called by a user when they wish by some keystroke in their AT,
 and announced, without having to go to a new page and leave the current
page etc that would be great.

Anyway this is an interesting issue that should maybe be added to the
issue tracker.


Received on Monday, 18 February 2008 13:53:31 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:30 UTC