29301 2015-11-20 12:59:03 +0000 mapping header (nearest sectioning ancestor being body) to banner role conflits with HTML spec 2018-05-03 21:20:15 +0000 1 1 1 Unclassified ARIA HTML AAM 1.0 All All RESOLVED INVALID P2 normal --- 1 w3.org faulkner.steve jason surkov.alexander oldest_to_newest 124266 0 w3.org 2015-11-20 12:59:03 +0000 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. 129209 1 w3cbugzilla 2018-05-03 21:20:15 +0000 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