landmarks-that-cannot-be-told-apart

This fails the run. Where it is wrong about your code, // ramonda-check-ignore <reason> on the line says so, and the reason is printed on every run.

Reported when one render has two or more landmarks of the same kind and none of them is named.

A screen reader offers landmarks as a LIST, and it is how somebody moves around a page without scrolling through it. A landmark with no accessible name is announced by its kind alone, so two of one kind read as "navigation, navigation" and the reader has to enter one to find out which it is, come back out, and try the other.

Give each one a name:

<nav aria-label="Primary">…</nav>
<nav aria-label="Footer">…</nav>

Do not put the word "navigation" in the name — the kind is already announced, and aria-label="Primary navigation" is read out as "Primary navigation navigation".

Where a visible heading already says what the section is, point at it instead and the two cannot drift apart: aria-labelledby={headingId}.

Only reported when NEITHER is named. One named and one unnamed are two different entries in the list, and can be told apart.

Next

• All rules — the other checks this one runs beside.
• Checking your app — how to run it, and what it proves.