W3C home > Mailing lists > Public > public-html@w3.org > February 2013

Re: Context of the main element

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Fri, 1 Feb 2013 10:16:46 +0000
Message-ID: <CA+ri+Vn=F5PrpMni9s+_TxrRVh+qazzVAY7qxc5n2s2akfNw6w@mail.gmail.com>
To: Jeremy Keith <jeremy@adactio.com>
Cc: Gez Lemon <g.lemon@webprofession.com>, "HTML WG (public-html@w3.org)" <public-html@w3.org>
Hi Jeremy

>I'd like to hear from implementers about whether this is what they're
going to do anyway when they add support for the main element.

support for the role mapping is already in all current implementations as
per the W3C spec as I wrote the patch for webkit and included the acc
implementation. Henri Sivonen did the same for Firefox.

Unlike most implementations of new features the accessibility support was
added at the same time as parsing etc.

You can check how browsers expose main in your examples by downloading the
nightlies of webkit or firefox and use an accessibility object inspection
tool.

FYI each instance of main is exposed with a role=main in the acc layer.

So If you try a page with <main> in the nightlies in conjunction with  a
screen reader such as JAWS, NVDA or VoiceOver it recognises it as a main
landmark and announces it also allows navigation of it.

Note the chrome implementation is a little different as like some other new
HTML5 structural elements it does not expose specific accessible
description - what get announced (in Mac OS Ax), this is a known bug  in
chrome

regards
SteveF

On 1 February 2013 10:03, Jeremy Keith <jeremy@adactio.com> wrote:

> Gez wrote:
> > An unambiguous main content area might be visually evident, but not so
> > easy to find for screen reader users. When a screen reader user
> > navigates through the page and hears "Main" as a landmark, it's
> > important that they understand this is the start of *the* main
> > section, rather than the main section of a sub-section, as the
> > sub-sections are not announced at the same time due to verbosity
> > reasons.
>
> Right. And I'm not suggesting that every main element should be announced
> as a landmark: only the main element that is scoped to the document body.
>
> I'd like to hear from implementers about whether this is what they're
> going to do anyway when they add support for the main element.
>
> In other words, given a document like this (which is currently invalid,
> but browsers have to parse a lot of invalid documents), how would the
> browser figure out the bounds of the main landmark:
>
> <body>
>  Some unimportant stuff
>  <main>
>   This is where the real stuff starts
>   <article>
>    <main>Some more real stuff</main>
>   </article>
>  The real stuff wraps up
> </main>
> Some unimportant stuff
> </body>
>
> My guess is that browsers will just look at the first main element to
> figure where the main landmark starts (and ends). That second main element
> would, for the purposes of skip links, just be ignored.
>
> Am I right in that guess? Browser makers, let me know please.
>
> Anyway, if that's the case (i.e. parsers will have to figure out how to
> handle the situation of having more than main element in a document, even
> if the spec forbids it), then altering the spec to allow authors to use the
> main element within sectioning content wouldn't add any more overhead.
>
> Jeremy
>
> --
> Jeremy Keith
>
> a d a c t i o
>
> http://adactio.com/
>
>
>
>


<http://www.paciellogroup.com/resources/wat-ie-about.html>
Received on Friday, 1 February 2013 10:17:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 1 February 2013 10:17:59 GMT