W3C home > Mailing lists > Public > wai-xtech@w3.org > August 2010

Re: ISSUE 30 @longdesc use cases

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Mon, 23 Aug 2010 19:26:55 +0200
To: Jonas Sicking <jonas@sicking.cc>
Cc: Joshue O Connor <joshue.oconnor@cfit.ie>, HTML Accessibility Task Force <public-html-a11y@w3.org>, HTML WG <public-html@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>, Barry McMullin <barry.mcmullin@dcu.ie>, Laura Carlson <laura.lee.carlson@gmail.com>
Message-ID: <20100823192655413663.831e08d0@xn--mlform-iua.no>
Jonas Sicking, Mon, 23 Aug 2010 09:58:21 -0700:
> On Mon, Aug 23, 2010 at 5:02 AM, Joshue O Connor:

> Wouldn't this markup work?
> <img src="chart.png" alt="..." aria-describedby="chart-description">
> <p hidden id="chart-description">
>   long description here.
> </p>

So you want to redefine @hidden? The spec says - #the-hidden-attribute:

It is similarly incorrect to use this attribute to hide content just 
from one presentation  if something is marked hidden, it is hidden 
from all presentations, including, for instance, screen readers.

Elements that are not hidden should not link to or refer to elements 
that are hidden.

   For example, it would be incorrect to use the href attribute to link 
to a section marked with the hidden attribute. If the content is not 
applicable or relevant, then there is no reason to link to it.
It would similarly be incorrect to use the ARIA aria-describedby 
attribute to refer to descriptions that are themselves hidden. Hiding a 
section means that it is not applicable or relevant to anyone at the 
current time, so clearly it cannot be a valid description of content 
the user can interact with.
leif halvard silli
Received on Monday, 23 August 2010 17:27:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:51:43 UTC