- From: Joshue O Connor <joshue.oconnor@cfit.ie>
- Date: Fri, 30 Oct 2009 16:02:52 +0000
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- CC: Jonas Sicking <jonas@sicking.cc>, John Foliot <jfoliot@stanford.edu>, Charles McCathieNevile <chaals@opera.com>, public-html@w3.org
Leif Halvard Silli wrote: > Joshue O Connor On 09-10-30 15.04: > >> Leif Halvard Silli wrote: >>> Leif Halvard Silli On 09-10-30 13.30: >>> >>>> Joshue O Connor On 09-10-30 12.24: >>> [...] >>> >>>> The purpose of ARIA seems to me to be to let the UA "compute" the A11Y >>>> layer on behalf of the author and the user. Whereas @longdesc as well >>>> as "normal fallback" (such as @alt content and the fallback of >>>> <object>) are "real" fallback that relies on regular hyper text. >>> >>> Therefore it seems more logical to me to include @longdesc into ARIA >>> than to introduce aria-link. >>> >>> Introducing longdesc into ARIA *and* make longdesc do - in ARIA - >>> whatever you envision that ARIA-link could do, would a) increase the >>> take up of longdesc, and b) be backward compatible and un-confusing. >> >> I don't really follow. As already @aria-describedby is a long >> descriptor, hampered only by its inability to ref a URI. > > How is it aria-describedby hampered, then, by not being a link, in your > view? What do you mean by "link"? I think what you primarely have in > mind is that we can include content that exist in another page. So, you > just want the ARIA enabled User Agent to be able to collect the long > description URI and present the content as part of the ARIA text > equivalent computation behaviour. Yes. Cheers Josh
Received on Friday, 30 October 2009 16:03:58 UTC