Inbox, Leeslijst and Instellingen have no h1 #230
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
An axe scan across all nine routes (added in #224 as
tests/e2e/landmarks.spec.ts) reportspage-has-heading-oneon three routes:The clean ones get theirs from
OverzichtShell.vue:26(<h1>{{ title }}</h1>) or write one directly. The three above have none:<h2>five times (Settings.vue:25,40,49,62,76) with no h1 above them.page-has-heading-oneis an axe best-practice rule, not a WCAG success criterion, so this is not a compliance failure. It does affect screen-reader users who navigate by heading: on these three routes there is no top-level heading to orient on, and on Instellingen the outline starts one level down.Needs a design call before implementation, which is why it is not folded into #224:
<h1>? A visible one changes the layout of the two busiest screens; a hidden one is invisible debt but matches the current design.<h1>Instellingen</h1>above the sections is the obvious fix and probably wants to be visible.Once settled, widen
RULESintests/e2e/landmarks.spec.tsto includepage-has-heading-one; the test is scoped tolandmark-one-mainandregiontoday precisely so this gap stays visible rather than being allowlisted away.