W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2012

Re: 48-Hour Consensus Call: InstateLongdesc CP Update

From: James Craig <jcraig@apple.com>
Date: Tue, 25 Sep 2012 14:53:14 -0700
Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, John Foliot <john@foliot.ca>, David Singer <singer@apple.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-id: <F6C1D98A-9653-43F8-B984-093B7197AE2F@apple.com>
To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
On Sep 25, 2012, at 5:15 AM, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> wrote:

> James Craig, Mon, 24 Sep 2012 21:10:25 -0700:
>> On Sep 24, 2012, at 7:21 PM, Leif Halvard Silli:
>>> So I don't think John's concern is "how to have it both ways". Rather, 
>>> it is how to make sure that users only get it a single way.
>> I don't think that was his point. Getting content a single way is 
>> only possible by having natively accessible forms of content, like 
>> accessible SVG, or MathML. Longdesc is a form of alternative content, 
>> which is, by definition, not a single way.
> Did not your accessible SVG example use a lot of ARIA? Is it then 
> "natively accessible"?

Sorry, I should have used a better term. Perhaps it'd be better to say "content with embedded accessibility" versus "content with some form of linked accessible alternative."

> There is a problem here: We can't compare a longdesc="" to iframe. 
> Longdesc is just a link.

I don't think that's always the case. Didn't IBM Home Page Reader implement longdesc as a temporary view? It may be okay to present longdesc as merely a link, but that shouldn't preclude us from comparing other presentations.
Received on Tuesday, 25 September 2012 21:53:43 UTC

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