Re: ISSUE 30 @longdesc use cases

Jonas Sicking, Mon, 23 Aug 2010 16:34:55 -0700:
> 2010/8/23 Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>:
>> Jonas Sicking, Mon, 23 Aug 2010 11:52:48 -0700:
>> 
>>> I know @hidden and display:none hides content from screen readers when
>>> reading the general flow of the page. However, as I said, code
>>> inspection indicates that it does not prevent the content from being
>>> pointed to by aria-describedby. And my reading of the ARIA
>>> specification indicates that Firefox is correct in this
>>> implementation.
>> 
>> Where does ARIA 1.0 speak about @hidden?
> 
> It doesn't, hence I don't see that it would be affected by it.

That the document referred to as "HTML5" currently disallows things 
which works in ARIA, is well known: 
http://www.paciellogroup.com/blog/?p=585

But in which way are we talking about 'works' when it comes to using 
ARIA to link to @hidden elements?  

ARIA is probably silent about <noscript> as well. But what happens, in 
a script enabled Firefox browser, if aria-describedby points to a 
<noscript> element?  Pointing to <noscript> perhaps works. (???) But 
what if it points to a <script> or a <style> element? Hey, you may even 
let aria-describedby point to another IMG element - or even the very 
same IMG element! That it isn't forbidden – and that it works, if we 
only look at the linkage technicalities – does not mean that user 
agents are required to start reading the script or the style sheet. 
"Works" could simply mean that user agent tells the user that, sorry, 
that element is hidden and therefore will not be read. 
-- 
leif halvard silli