This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29301 - mapping header (nearest sectioning ancestor being body) to banner role conflits with HTML spec
Summary: mapping header (nearest sectioning ancestor being body) to banner role confli...
Status: RESOLVED INVALID
Alias: None
Product: ARIA
Classification: Unclassified
Component: HTML AAM (show other bugs)
Version: 1.0
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-20 12:59 UTC by Martin Janecke
Modified: 2018-05-03 21:20 UTC (History)
2 users (show)

See Also:

Attachments

Description Martin Janecke 2015-11-20 12:59:03 UTC 
HTML5 and HTML5.1 suggest to use the header element for grouping a heading with taglines, subtitles etc.
http://www.w3.org/TR/html5/common-idioms.html#sub-head
http://www.w3.org/TR/2015/WD-html51-20151008/semantics.html#sub-head

This is also in line with the definition of the header element, as I understand it:
http://www.w3.org/TR/html5/sections.html#the-header-element

Therefore it's reasonable to use the header element around the main
heading of a page. The aria banner role, however, is not suitable for
the page-specific main heading of a page.
http://w3c.github.io/aria/aria/aria.html#banner

But the current accessibility mapping for header (with the nearest
ancestor sectioning content or sectioning root element being body) is to
the banner role, defined in
http://w3c.github.io/aria/html-aam/html-aam.html#el-header-ancestorbody

Hence I see a conflict.

I suggest either to remove the association of the header element with
the banner role or to change the HTML spec and describe a new mechanism for the markup of taglines, alternative title etc.
Comment 1 James Nurthen 2018-05-03 21:20:15 UTC 
HTML AAM is no longer an ARIA Deliverable. If you wish to pursue this issue please file at https://github.com/w3c/html-aam/issues