W3C home > Mailing lists > Public > public-html@w3.org > April 2011

Re: role="subheading" or role="subtitle" to replace hgroup

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Fri, 8 Apr 2011 13:58:57 +0200
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: Bruce Lawson <brucel@opera.com>, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, HTMLWG WG <public-html@w3.org>
Message-ID: <20110408135857692344.852d3ede@xn--mlform-iua.no>
Steve Faulkner, Fri, 8 Apr 2011 12:32:27 +0100:
> hi bruce, 
> i would suggest that subheading could also be used on <p> or <div> or 
> even <span>
> the subheading attribute would expose the role, the role of the 
> element it is on would be overriden by the attribute.

* It doesn't make sense to say that a <span> could carry the 
@subheading/@hcaption attribute unless you also suggest that the 
heading caption could - as well - be the child of a <hn>. (So far 
you've suggested it could be the (adjacent) sibling of a <hn>.) Because 
it is very bad coding style to let a <span> be the adjacent sibling of 
a <hn>.

* The thinking would have been undersatndable if we were speaking about 
@role="subheading". But we are speaking about @subheading/@hcaption, 
for which you said there would be minted a @role value, anyway. So, if 
A11Y is all that matters, then authors could eventually use that 
role=subheading on the span/div, rather than @subheading/@hcaption.

* @subhead/@hcaption should probably be limited to <hn> elements.

Thought experiment: can't we just use role=presentation?

<h2 role="presentation">subheading</h2>

Why not? 

If role=presenation is not possible, then justification must be that 

 * _retains_ its "heading-ness"
 * _looses_ its outline-ability
 * _gets_ a caption relationship to its adjacent sibling

(Additionally, to use @role=presentation would be to mix the ARIA layer 
and the HTML layer.)
leif halvard silli
Received on Friday, 8 April 2011 11:59:28 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:12 UTC