W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2013

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

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 26 Mar 2013 05:16:35 +0000 (UTC)
To: Ian Yang <ian@invigoreight.com>
cc: w3c-wai-ig@w3.org
Message-ID: <Pine.LNX.4.64.1303260509110.15713@ps20323.dreamhostps.com>
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.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 26 March 2013 05:16:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:48 UTC