On 19 November 2015 at 10:33, Martin Janecke <w3.org@prlbr.com> wrote: > I object against the accessibility mapping of header (with the nearest > ancestor sectioning content or sectioning root element being body) to > the banner role > Hi Martin, apologies for not responding to your previous email about this, I overlooked it :-( The mapping you refer to is what is currently implemented in browsers (Safari, Chrome, Firefox, Opera) and is what is defined in the HTML5 Recommendation. Working draft content does not have to reflect working group consensus "Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. " It may be that the current mapping should be changed, but changing it in the spec does not make it so. Suggest you file a bug against the API mapping spec https://www.w3.org/Bugs/Public/enter_bug.cgi?product=ARIA&component=HTML%20AAM&version=1.0 about this as it will be on all of the editors radars and we can then elicit feedback from browser implementers, amongst others, and gather data about how <header>is used in wild and how its use maps to the banner role. -- Regards SteveF Current Standards Work @W3C <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>
Received on Thursday, 19 November 2015 11:13:43 UTC