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

(unknown charset) Re: Expanding longdesc use

From: (unknown charset) Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Fri, 16 Mar 2012 12:34:46 +0100
To: (unknown charset) David Singer <singer@apple.com>
Cc: (unknown charset) David MacDonald <david100@sympatico.ca>, HTML Accessibility Task Force <public-html-a11y@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>
Message-ID: <20120316123446737739.9bc3689e@xn--mlform-iua.no>
David, just wanted to add that @linked-anchor would be focused on 
reusing the @href, wheras @aria-describedby is focused on reusing the 
textual content.

Leif Halvard Silli, Fri, 16 Mar 2012 11:58:59 +0100:

> To be able to, effectively, reuse visual links - which I agree is a 
> noble goal, we would need not @longdesc and not @aria-describedAT [if 
> it would become just like @longdesc] but a new attribute - let's call 
> it @linked-anchor:
> 
> <img src=s alt=a linked-anchor=linked >
> <a id=linked href='long-description'>Image description.</a>
> 
> The effect of @linked-anchor should be to reuse the URL of the anchor 
> as longdesc link. Unless we add more rules for how it works - such as a 
> rule to ignore the longdesc effect if the next element is the linked 
> anchor, then the above link would be presented twice to AT users: Once 
> as longdesc link, and once in the normal flow.  But if the above link 
> got an @aria-hidden='true' or @hidden or style='display:none', then it 
> would only be presented once.
> 
> Such a @linked-anchor could be presented to users - AT user as well as 
> other users - exactly the same way that @longdesc is presented.
-- 
Leif H Silli
Received on Friday, 16 March 2012 11:35:27 UTC

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