Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)

On Sep 15, 2012, at 7:55 PM, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> wrote:

> Charles McCathie Nevile, Sat, 15 Sep 2012 16:53:50 +0200:
>> On Sat, 15 Sep 2012 11:29:48 +0200, James Craig wrote:
> 
> James: I would suggest to combine @longdesc with iframe. See below.
> 
> But first: May be, if link focus worked better in Safari, you would 
> have taken another tone? ;-) Because, while a curb-cut is elegant, one 
> should not love the curb-cuts so much that one produces wheelchairs 
> that are incompatible with stair lifts. That would  seem very dumb. And 
> in that regard: It is OK to argue that something other than @longdesc 
> wold work better. However, due to bug 22261 - "Clicking on a non-text 
> input element does not give it focus",[1] Webkit and Chromium suffers 
> from the following: if one opens a longdesc link (e.g. with Webkit 
> based iCab) VoiceOver will start to read from the top of the page 
> instead of from the section where the particular longdesc was situated. 
> Something which takes away lots of flexibility with regard to longdesc. 
> And, in fact, it also impacts regular links as well - it is is real 
> hole in VoiceOver and Webkit's elegance.

The bug report you referenced above appears to be unrelated to longdesc or VoiceOver focus. Would you be willing to file a bug about the other two issues you mentioned?

In either case, it does not change my opinion of longdesc. 

…snip…

> But why not combine <iframe> with @longdesc? Roughly so: 
> 
>   <style>#iframe:target{display:block}</style></head><body>
>   <img src=i alt=text longdesc=#iframe >
>   <iframe id=iframe hidden="" src=description.html ></iframe>

I'll add that here as a suggested variant of longdesc when I add Charles' suggestion of longdesc pointing to a link.

James

Received on Wednesday, 19 September 2012 21:44:48 UTC