Page content

``` No `role` is needed: a bare `

` scoped to `` or `

` is a `complementary` landmark. Inside sectioning content (`

`, `

`) it is one only when it has an `aria-label` or `aria-labelledby`, which is what the HTML accessibility mapping specifies. Nothing in either file alone is wrong, and a file-scoped markup linter cannot see this, since the nesting only exists once the layout's `

` and the page's `complementary` are composed across files. Not flagged: - A route with no `banner`/`main`/`complementary`/`contentinfo` landmark at all. - Nesting through an intermediate, non-landmark component: if `+page.svelte` places `` inside `

`, and `Sidebar.svelte` itself renders `role="complementary"`, that nesting is out of scope. Detection is counting-only per file, plus the direct layout-`` case, not a full call-graph trace through every intermediate component. ## Why it matters Assistive technology exposes `banner`, `main`, `complementary`, and `contentinfo` as landmarks a user jumps between with a keystroke, on the assumption each is a distinct, top-level region of the page. A landmark nested inside another loses that meaning: it disappears from landmark navigation, or reads as content of the outer landmark instead of the region it's meant to be. ## How to fix Move the nested landmark out so every landmark composes at the top level of the route: ```svelte +layout.svelte

Site navigation

{@render children()}

``` ```svelte +page.svelte

Page content

``` ## Mode differences Landmarks are collected in both modes, but from different sources, so results can differ: - **Source analysis** (the CLI, the dashboard's static baseline) composes the route's layout chain with its resolved local components to detect nesting. It cannot see nesting introduced by an unresolvable component (`node_modules`, a dynamically chosen component). - **Source analysis** (the CLI, the dashboard's static baseline) also decides whether a `

`/`