Re: Context of the main element

Hi Jeremy,


"Oh, none. I would imagine that any instances of the main element that
don't correspond to the main landmark (i.e. any instances that aren't
scoped to the document body) wouldn't have any special semantics for the
acc layer …they'd effectively be no different than divs."

what you appear to be saying is that structural elements such as
header/footer if not scoped to the body should have a presentational role
only. I don't think its that simple.

The vast majority elements and attributes have some sort of mapping to the
accessibility layer.

ARIA is not used in the mapping of  the vast majority of roles,states and
properties , representations of them are exposed in the accessibility APIs
in cases where  no roles, states and properties native to the API's are
defined.



regards
SteveF

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

> Steve wrote:
> > for example I don't see how your suggested changes will benefit users
> who consume the semantics, what will the semantics of nested main be when
> mapped to the acc layer?
>
> Oh, none. I would imagine that any instances of the main element that
> don't correspond to the main landmark (i.e. any instances that aren't
> scoped to the document body) wouldn't have any special semantics for the
> acc layer …they'd effectively be no different than divs.
>
> And that prompts the question "well, why not just use a div, then?" …which
> is a fair question. But seeing as HTML5 introduces a few other new elements
> that (I believe) don't have any effect on the outline or on the acc layer
> (e.g. header and footer within sectioning content), then the introduction
> of a new element like main seems like a good opportunity to give authors
> the option of using a dedicated element in place of a generic div.
>
> Cameron referred to this as "semantic sugar", which, while it was probably
> meant as a negative term, is actually a pretty good way of describe many of
> the new elements in HTML5.
>
> So my suggestion really just boils down to throwing a bone to authors.
>
> As for use cases: every single use of a header or footer within sectioning
> content (other than the body element) is also a potential use case for main.
>
> Jeremy
>
> --
> Jeremy Keith
>
> a d a c t i o
>
> http://adactio.com/
>
>
>