`banner` landmark: must be top-level

Rule ID	Landmark 8
Definition	The `banner` landmark must be a top-level landmark.
Purpose	Top-level landmarks are the easiest to find and navigate to using assistive technologies. Banner content is usually the content at beginning of a page that repeats on most pages within a website.
Required	Yes for HTML5 and ARIA Techniques ruleset mapping
WCAG Success Criteria	1.3.1 Info and Relationships (Level A, Primary Success Criterion) Other Related Success Criterion: 2.4.1 Bypass Blocks (Level A) 2.4.6 Headings and Labels (Level AA) 2.4.10 10 Section Headings (Level AAA)
Rule Category	Landmarks
Scope	Element
Target Resources	`[role="banner"]` and top-level `header` element `header`
Techniques	When creating the landmark structure on the page, ensure that the `banner` landmark or `header` element is a top-level landmark (i.e., it is not contained within any other landmarks). A `header` element with the context of the `body` element or an element with `[role="contentinfo"]` attribute defines a `banner` landmark.
Informational Links	Accessible Rich Internet Applications (WAI-ARIA) 1.1 Specification: banner role HTML5: The HEADER element WAI-ARIA Authoring Practices 1.2: Landmarks WAI-ARIA Authoring Practices 1.2: Landmark Example W3C Web Accessibility Tutorials: Page Structure ARIA11: Using ARIA landmarks to identify regions of a page ARIA13: Using aria-labelledby to name regions and landmarks ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used

banner landmark: must be top-level