Re: updated change proposal for issue 129 ARIA in HTML5

thanks Stephen,

2 points:

1. The example text content is not meant be indicative, I have changed it to

<hgroup>
<h2>Foo</h2>
<h3>Bar</h3>
</hgroup>

2. there are internal semantics conveyed visually
h2 has a default rendering that differentiates it from h3
and this is usually augmented by the use of CSS to further differentiate a
heading and subheading.

thus the heading/subheading semantics are lost to accessibility clients.

regards
stevef


On 1 February 2011 23:46, Stephen Stewart <carisenda@gmail.com> wrote:

> Hi,
>
> The section on hgroup[1] caught my eye, it seems to me to use a bad
> example:
>
> <hgroup>
> <h2>The problem</h2>
> <h3>Analysis</h3>
> </hgroup>
>
> This seems to define two sections, Problem and Analysis ("The problem
> Analysis" is very clumsy so it seems more likely to be two headings).
> hgroup is for headlines which associate n+1 H1-6 elements with one
> section, not two. If I were to substitute a more correct example I
> think most of the problems disappear in this section as per the
> author's own logic:
>
> <hgroup>
> <h2>Clinton Acquitted</h2>
> <h3>Perjury, obstruction charges defeated</h3>
> </hgroup>
>
> Taking away the layout that should read as "Clinton
> Acquitted<beat>Perjury, obstruction charges defeated", there are no
> internal semantics to convey other than the order of the words.
>
> [1]
> http://www.w3.org/html/wg/wiki/ChangeProposals/ARIAinHTML5#basis_for_defining_h1_to_h6_element_that_does_have_an_hgroup_ancestor
>
> HTH,
> Stephen
>
> On 1 February 2011 12:12, Steve Faulkner <faulkner.steve@gmail.com> wrote:
> > Hi all,
> > the html accessibility ARIA subteam have discussed the counter proposal
> > provided by the html5 editor.
> > We have updated our change proposal[1]
> >
> > We have removed any out of scope issues (for this proposal) and have put
> > issues of an editorial nature (in this proposal) to one side.  This does
> not
> > mean that we do not consider editorial changes are required, but that
> these
> > can be dealt with during last call.
> >
> > We have essentially boiled the change proposal down to what we consider
> the
> > most important issues that need to be resolved prior to last call.
> >
> > [1] http://www.w3.org/html/wg/wiki/ChangeProposals/ARIAinHTML5
> >
> > --
> > 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
> >
> >
>
>
>
> --
> Stephen Stewart
> carisenda@gmail.com
>



-- 
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