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

HGROUP revisited

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Fri, 14 Jan 2011 22:05:16 +0000
Message-ID: <AANLkTimY+6EcdHsCn4Ks60MuHMTknU_tb6-EDqnXG=rk@mail.gmail.com>
To: HTMLWG WG <public-html@w3.org>
Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, Cynthia Shelly <cyns@microsoft.com>, Ian Hickson <ian@hixie.ch>
The HTML5 editor has provided some clarification [1] on how he thinks
hgroup should be implemented in relation to accessibility roles and
properties:

for example:
this

<hgroup>
 <h1>The reality dysfunction</h1>
 <h2>Space is not the only void</h2>
</hgroup>

is to be conveyed as via accessibility APIs:

<h1>
<p>The reality dysfunction</p>
<p>Space is not the only void</p>
</h1>



The above directly contradicts he following statement in the HTML5
specification, as there is no differentiation between heading and
subheading:

"Other elements of heading content in the hgroup element indicate
subheadings or subtitles." [2]


[1] http://wiki.whatwg.org/wiki/Change_Proposal_for_ISSUE-129#Bug_10592:_Request_regarding_the_ARIA_role_of_heading_elements_inside_HGROUP_elements
[2] http://dev.w3.org/html5/spec/Overview.html#the-hgroup-element


-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Friday, 14 January 2011 22:07:12 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:21 UTC