W3C home > Mailing lists > Public > public-html@w3.org > June 2010

RE: aside and figure elements

From: Dean Leigh <dean.leigh@deanleigh.co.uk>
Date: Tue, 8 Jun 2010 15:29:17 +0100
To: "'Leif Halvard Silli'" <xn--mlform-iua@xn--mlform-iua.no>
Cc: "'Laura Carlson'" <laura.lee.carlson@gmail.com>, "'Bruce Lawson'" <brucel@opera.com>, "'Shelley Powers'" <shelleyp@burningbird.net>, "'HTML WG'" <public-html@w3.org>, "'HTML Accessibility Task Force'" <public-html-a11y@w3.org>
Message-ID: <003d01cb0716$fac12cf0$f04386d0$@leigh@deanleigh.co.uk>
Hi Leif,
>         To use aria-describedby
> 		(<article aria-describedby="aside-for-season1">)
>         does not seem correct for something that is supposed to be only
>         "content that is tangentially related".

I agree and I don't think aria-labelledby is intended for this purpose
(albeit in the other element) either.
aria-flowto could work but I am not sure how the users then gets back to the
article from the aside and again I am not sure this is what it was designed
for.

However, if the <aside> element is considered theoretically a child  (but
not in the DOM) of an element or group of elements then could the accessible
alternative be aria-owns?

aria-owns
Identifies an element (or elements) in order to define a visual, functional,
or contextual parent/child relationship between DOM elements where the DOM
hierarchy cannot be used to represent the relationship.

Regards,
Dean Leigh


> -----Original Message-----
> From: public-html-request@w3.org [mailto:public-html-request@w3.org] On
> Behalf Of Leif Halvard Silli
> Sent: 08 June 2010 14:52
> To: Dean Leigh
> Cc: 'Laura Carlson'; 'Bruce Lawson'; 'Shelley Powers'; 'HTML WG'; 'HTML
> Accessibility Task Force'
> Subject: RE: aside and figure elements
> 
> Dean Leigh, Tue, 8 Jun 2010 14:25:48 +0100:
> > Hi Leif,
> >>> <aside> cannot be moved to another context without losing a lot of
> >>> its original meaning. If you lose the link to the context - in any
> >>> meaning of "link" - the <aside> stops functioning as an aside.
> >
> > Again I would recommend using something like ID and for="" to link the
> > <aside> to its relevant content.
> 
> > <article id=season1> [ snip ] </article>
>    [ snip ]
> > <h1>Additional seasonal facts<h1> (possibly in the right column but
could
> be
> > anywhere on the page)
> > <aside for=season1>Spring is usually accompanied by birdsong</ aside>
> 
> > This keeps the relationship separate from presentation but accessible to
> > readers, UAs and easy to style with CSS.
> 
> Question: Does "something like ID and for=''" for this use case exist
> in WAI-ARIA?
> Answer: I could not see anything:
> 
> http://www.w3.org/TR/wai-aria/states_and_properties#state_prop_def
>         To use aria-describedby
> 		(<article aria-describedby="aside-for-season1">)
>         does not seem correct for something that is supposed to be only
>         "content that is tangentially related".
>         http://dev.w3.org/html5/spec/sections.html#the-aside-element
> 
> Otherwise, if the <aside> doesn't appear in its logical context (that
> is: nested inside the <article>, close to the issue that the issue that
> the <aside> is an aside to - as HTML5 says "related to the content
> _around_ the aside element"), then I guess you can just use an <a>
> element in order to link from (some place in) the article to the
> <aside>. You may also want to link back to article again as well .
> 
> Also, if you keep the <aside>s as logically/systematically ordered as
> you do here (with their own heading element), then it should be easy
> for anyone to find them.
> --
> leif halvard silli
Received on Tuesday, 8 June 2010 14:59:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:09 GMT