Re: Tab role and required accessible name: WAI-ARIA 1.1 spec

>
> hN elements are ONLY to be used as an introduction to a section.  Which is
> nonsense, but whatever.


In HTML5 Hn other than the first in a section creates an implicit
section/sub section:

The first element of heading content in an element of sectioning content
> represents the heading for that section. Subsequent headings of equal or
> higher rank start new (implied) sections, headings of lower rank start
> implied subsections that are part of the previous one. In both cases, the
> element represents the heading of the implied section.


the use of implicit sectioning is discouraged

Authors are also encouraged to explicitly wrap sections in elements of
sectioning
> content, instead of relying on the implicit sections generated by having
> multiple headings in one element of sectioning content.


http://www.w3.org/TR/html5/sections.html#headings-and-sections


--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>

On 6 April 2015 at 13:40, Shane McCarron <shane@aptest.com> wrote:

> A comment on document structure:
>
> On Mon, Apr 6, 2015 at 2:31 AM, Birkir Gunnarsson <
> birkir.gunnarsson@deque.com> wrote:
>
>>
>> P.s. For the final draft, we need to make the role entries h2
>> headings, not h5, I find navigating the 1.1 spec very cumbersome due
>> to the skewed heading levels, but it is all about content right now,
>> not presentation.
>>
>>
> Actually, they shouldn't be a heading at all according to the ReSpec
> powers-that-be.  According to them, hN elements are ONLY to be used as an
> introduction to a section.  Which is nonsense, but whatever.
>
> However, in the current draft the roles are h3.  See
> http://w3c.github.io/aria/aria/aria.html for the current draft of ARIA
> 1.1 Core.
>
> --
> Shane McCarron
> Managing Director, Applied Testing and Technology, Inc.
>