Steve, I think the best algorithm:
· header elements contained within another ARIA landmark it should have a role of GROUP, otherwise role BANNER. · footer elements contained within another ARIA landmark it should have a role of GROUP, otherwise role CONTENTINFO. Note ARIA landmarks can be defined using elements (e.g. main, aside, section[aria-label | aria-labelledby]..) or by use of role values (e.g. div[role=main], div[role=complementary],..) What do you think? Jon From: Steve Faulkner [mailto:[email protected]] Sent: Friday, October 02, 2015 10:46 AM To: Gunderson, Jon R <[email protected]> Cc: [email protected]; Nick Hoyt <[email protected]>; Rich Schwerdtfeger <[email protected]> Subject: Re: FOOTER and HEADER elements defined as landmarks in HTML5 Hi Jon, I agree, from looking at usage of the elements that map to landmark roles, that some tweaking is needed (main usage being the least problematic by far, from recent data anaylisis 98% of pages using <main> use 1) Can you provide some idea of the logic for such restrictions to be implemented in browsers? for example "only the first header in DOM scoped to the body is mapped to banner" "only the last footer in DOM is mapped to contentinfo" Would these result an acceptable majority of use being covered? here are some example pages conatining header and footer http://www.html5accessibility.com/HTML5data/header-footer/index-all.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.html5accessibility.com_HTML5data_header-2Dfooter_index-2Dall.html&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=bfvxRqSNs_8PUhbl6ZQ5-CC13OIQMG03z4np6VAN-c8&s=gx8sqTfb34dwY7DUh8CNHu0CC5ZftMKxb15lXD4Mv4o&e=> -- Regards SteveF Current Standards Work @W3C<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.paciellogroup.com_blog_2015_03_current-2Dstandards-2Dwork-2Dat-2Dw3c_&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=bfvxRqSNs_8PUhbl6ZQ5-CC13OIQMG03z4np6VAN-c8&s=xGvL1xqSDSiSkY4BhlMG2VEowbC2iqECfpICatjPsP8&e=> On 1 October 2015 at 17:06, Gunderson, Jon R <[email protected]<mailto:[email protected]>> wrote: Steve, I would like to file an issue with the current API mappings for the HEADER and FOOTER. Right now they will be defined as a BANNER or CONTENTINFO landmarks, except when they are descendants of ARTICLE or SECTION elements. http://www.w3.org/TR/html-aapi<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_TR_html-2Daapi&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=bfvxRqSNs_8PUhbl6ZQ5-CC13OIQMG03z4np6VAN-c8&s=1pKBuNHDkt_xWakL7-8j4SZLtvIQHt2CG0-bKyH9QNA&e=>/ I am curious why other sectioning elements like ASIDE, MAIN and NAVIGATION were not also included. My main concern is that many people use the HEADER and FOOTER elements outside of ARTICLE and SECTION elements, and I don’t think they mean to create BANNER and CONTENTNFO landmarks. Typically a page only needs at most one of BANNER and CONTENTINFO landmarks, so I think it should be harder to make them automatically using the HEADER and FOOTER elements. We have a set of rules related to BANNER and CONTENTINFO landmarks: 1. Must be top level landmark 2. Only one 3. Restriction of what can be in the landmarks Rule Details: http://fae20.cita.illinois.edu/rulesets/rc/#id_h3_ID_LANDMARKS Look forward to your response, Jon
