Re: ISSUE-30 (Longdesc) Change Proposal

Jonas Sicking On 09-10-30 16.24:

> On Fri, Oct 30, 2009 at 7:02 AM, Joshue O Connor wrote:
>> Leif Halvard Silli wrote:
>>> I agree: That @longdesc is a link is the key. @longdesc has other
>>> advantages as well, but they are all linked (sic!) to the fact that it
>>> is a link.
>>>
>>> I wonder if it will be possible to make aria-describedby into a link,
>>> though. [...]
>> Yes, to give @aria-describedby the ability to reference a URI as well as
>> a IDREF would be a great advantage.
> 
> Why not simply say that if the IDREF points to an element that is a
> link, then that link provides the description.

If you want to single out *one* of the IDREFS that 
aria-describedby can contain as "the description", then why not 
rather use @longdesc for that?

I see no simplicity in being able to say "but if your 
aria-describedby IDREF points to a link then ... "

(I understand that I could have described this in a more LOL way. 
But sorry, I keep it dry.)

> This forces authors to consider putting the link to the description in
> the normal flow of the page, thus making it accessible to everyone,
> not just users of AT tools. Something which usually is a win.

+1 for supporting my idea that ARIA is for drawing links to things 
that is already in the page.

> For the cases when rendering the link is not desired, the link can
> simply be hidden using CSS or the @hidden attribute. 


See above about @longdesc.

>Or you can place
> the link in the <head> which is never rendered.

And at the same time making "</head><body>" obligatory? Do you 
make a user agent where an anchor in the <head> is possible? It 
ain't possible in Webkit, at least. Unless you meant to use 
<link>? I don't think this is a good idea.
-- 
leif halvard silli

Received on Friday, 30 October 2009 16:37:24 UTC