Homepage- The header element is nested inside the main element.

[shirsha]

The main content on the page is placed in a header element which is nested inside the main element.

[jnurthen]

The TF discussed this on May 24, 2022

Matt_King: oh there's a header around an H1, which isn't needed. and yes, header inside a main element doesn't seem right 11:49 jongunderson: back in the XHTML days, the header element defined the heading structure itself 11:50 jongunderson: i think it's odd it's not being used to create a banner landmark though 11:50 jongunderson: i'd say move the header element to the top, leave the H1 alone 11:50 Matt_King: i think this belongs in the other repo too 11:51 jamesn: so what's the bug, then? 11:51 Matt_King: the H1 is wrapped in a header; exposed as a banner 11:51 jamesn: that's a firefox bug, it's scoped to main vs generic so it's not getting exposed right 11:52 James Nurthen A header element is intended to usually contain the section's heading (an h1–h6 element or an hgroup element), but this is not required. The header element can also be used to wrap a section's table of contents, a search form, or any relevant logos. 11:52 <MarkMcCarthy> jongunderson: if they're using the headers this way, they're making banner landmarks 11:52 Matt_King: with voiceover and safari 11:53 s/Matt_King: with/jongunderson: with 11:53 Matt_King: chromium does not 11:53 Matt_King: so it's a gecko and webkit bug 11:54 jamesn: it's correct and allowed 11:54 jongunderson: it's allowed, but i don't think it's correct 11:54 jamesn: it contains the section' 11:54 s/section'/section's heading right? 11:55 Matt_King: main is a sectioning element right? 11:55 Matt_King: it conforms with the spec - Siri, what do you say? 11:55 siri: even though it conforms, but if it's not required i'd suggest removing it 11:55 jongunderson: +1 11:56 jamesn: i think we should also file bugs vs. the browsers, don't disagree about removing it 11:56 Matt_King: so could someone flag this with firefox and safari? 11:57 jamesn: browsers don't seem to expose it in the accessibility info - maybe it's NVDA and VoiceOver then? 11:57 Matt_King: maybe the accessibility tree itself has a bug then? 11:58 jamesn: remember - we're triaging :) 11:58 TOPIC: Meeting wrapup 11:58 jamesn: might not be as simple as filing bugs with the browsers 11:59 siri: i'll do some investigation