[Bug 27092] The header element semantic scope is controversial

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27092

steve faulkner <faulkner.steve@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |faulkner.steve@gmail.com
           Assignee|dave.null@w3.org            |faulkner.steve@gmail.com

--- Comment #1 from steve faulkner <faulkner.steve@gmail.com> ---
(In reply to Klim Lee from comment #0)
> The spec states in 4.3.7:
> 
> "The header element represents introductory content for its nearest ancestor
> sectioning content or sectioning root element."
> 
> "When the nearest ancestor sectioning content or sectioning root element is
> the body element, then it applies to the whole page."
> 
> At the same time, header’s default ARIA role is “banner”, which is very
> different from “introductory content for nearest sectioning content”, and is
> “mostly site-specific, rather than page-specific content”. In fact, that
> means ATs should treat such headers as rather irrelevant to “nearest
> ancestor sectioning content”.

The header element only has a default role=banner when the header element  is
not a descendant of an article or section element, as per the HTML mapping
http://www.w3.org/html/wg/drafts/html/CR/dom.html#sec-strong-native-semantics
and as implemented in browsers:
http://stevefaulkner.github.io/html-mapping-tests/ except IE which has not
implemented the semantics yet.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 17 October 2014 18:40:35 UTC