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

Re: Moving longdesc forward

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Wed, 4 May 2011 17:48:47 +0200
To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Cc: Laura Carlson <laura.lee.carlson@gmail.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-ID: <20110504174847203999.e95bb1a4@xn--mlform-iua.no>
Benjamin Hawkes-Lewis, Wed, 4 May 2011 15:52:37 +0100:
> On Wed, May 4, 2011 at 2:37 PM, Leif Halvard Silli:
   ...
>> http://www.w3.org/mid/20110504152204634608.a973ed8c@xn--mlform-iua.no

> 
> Why we should constrain @longdesc to resources that are HTML/XML markup
> with an HTML root element?

To say that users plus user agents are likely to expect HTML ( = 
content with <html> as root element) and that they may not be able to 
properly/effectively handle other formats (which may require plug-ins, 
external programs etc), is just that - a warning and a recommendation - 
and not a constraint.

> This constraint would not prevent images, unstructured text, or
> text encoded in unrecognized vocabularies being supplied as text
> equivalents, it just requires them to be contained in a 
> lightweight HTML/XML wrapper.

The format recommendation/warning cannot prevent 'light wrapper' misuse 
- other language in the spec text prevent such misuse, it is supposed 
to be a description! But it can help authors to create descriptions 
that user and user agents can - technically - handle properly and 
effectively. 

Though, as this example shows, longdesc document should probably not be 
inside a framge page:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzahh/proxies.htm


Benjamin Hawkes-Lewis, Wed, 4 May 2011 15:54:39 +0100:
> On Wed, May 4, 2011 at 2:36 PM, Leif Halvard Silli:
>>> The purpose of @longdesc in the suggestex text is twofold:
>>> 
>>>     1. Structured text alternatives.
>>>     2. Long text alternatives.
>> 
>> Structured *and* (potentially) long.
> 
> Long OR structured.
> 
> If we think @longdesc should only be used where structured markup is
> required, we should revise the requirements and text to match.

'long descriptions' are short pieces - like this one by Laura: 
http://www.d.umn.edu/~lcarlson/research/ld/superimposeicon.html


If we agree to recommend HTML (as described above), then we can put the 
long/structured discussion to the side.
-- 
Leif Halvard Silli
Received on Wednesday, 4 May 2011 15:49:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:38 GMT