Re: Rethinking the necessities of ARIA landmark role "main" and HTML5 <main> element

Does Hixie's response make it any clearer to anyone why role=main or the
<main> element is redundant?

If so please explain.

with regards

--
SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
 <http://www.paciellogroup.com/resources/wat-ie-about.html>


On 26 March 2013 05:16, Ian Hickson <ian@hixie.ch> wrote:

> On Tue, 26 Mar 2013, Ian Yang wrote:
> > On Tue, Mar 26, 2013 at 12:43 PM, Ian Hickson <ian@hixie.ch> wrote:
> > >
> > > Mark it as such. For example, sidebars using <aside>, navigation
> > > blocks using <nav>, footers using <footer>, etc.
> >
> > I'm sorry, but I don't get it.
> >
> > Assume there is a user who is not interested in the <header>, <nav> and
> > <aside>. How could these markups help the user jump past themselves?
>
> The same way a landmark role would, or the way <h1>s would. The user agent
> or accessibility tool would provide a user interface to enable the user to
> navigate the document accordingly. For example, it's common for user
> agents to allow the user to jump to specific headings by pressing a key
> combination, or to skip to the next paragraph (skipping past any content
> in the current paragraph) by pressing a key combination. The same is
> possible for landmark roles or for skipping past uninteresting sections.
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>
>