Re: <header> / <footer> & ARIA (was: Re: Proposal: <content> element)

Hi Henri,

>It seems silly to have almost one-to-one mapping between the new HTML5
sectioning elements and ARIA landmarks but not quite one-to-one. Surely the
>reasonable thing to do here is to adjust either HTML 5 or ARIA or both.

I agree, this will involve the html working group and the protocols and
formats working group working  on a consensus solution.

regards
stevef


2009/8/28 Henri Sivonen <hsivonen@iki.fi>

> On Aug 28, 2009, at 13:32, Steven Faulkner wrote:
>
>  the example for footer in the html 5 spec does not fit the definition of
>> contentinfo in the ARIA spec.
>>
>
> It seems silly to have almost one-to-one mapping between the new HTML5
> sectioning elements and ARIA landmarks but not quite one-to-one. Surely the
> reasonable thing to do here is to adjust either HTML 5 or ARIA or both so
> that the following mapping holds:
>
> role=main == <main>
> role=contentinfo == <footer>
> role=banner == <header>
> role=navigation == <nav>
> role=complementary == <aside>
> role=search == <form> with <input type=search> descendant
>
> Of course, to make informed adjustments, the rationales for both the ARIA
> landmark set and the HTML5 element set need to be available for examination.
>
> --
> Henri Sivonen
> hsivonen@iki.fi
> http://hsivonen.iki.fi/
>
>
>


-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html