Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Report of incorrect a11y guidance for "Make Screen Reader Navigation Easier with the header Landmark"
See original GitHub issueOne of the forum users (Marconiusiii) has raised an issue about this accessibility lesson. Here are their remarks
This article/lesson is teaching a bad a11y practice. h1 elements do not belong in the header region since they are usually the first targeted element by screen reader users. Once I jump to the h1, I am expecting there to be page content ready to go when I start navigating normally element by element down the page. Putting the h1 in the header defeats the purpose of the h1 and the landmark since only repeated elements and object belong in the header, such as logos, navigation regions, search boxes, etc. The h1 will change with each page change, and navigating down from it should move me immediately into the page content, not contend with anything else in the header region.
Skip to content links generally aim for either the main region id or the h1 id, and if I land on an h2 in the main content, I feel like I’ve missed something and try navigating backwards to find the h1.
Please revise the practices being taught here and ensure that coders and designers don’t put their h1s incorrectly into header regions.
<body>
<header>
<!-- h1 elements do not belong here! -->
<h1>Training with Camper Cat</h1>
</header>
<main>
<!-- h1 elements belong right here! -->
<section id="stealth">
<h2>Stealth & Agility Training</h2>
<article><h3>Climb foliage quickly using a minimum spanning tree approach</h3></article>
<article><h3>No training is NP-complete without parkour</h3></article>
</section>
Affected page
Make Screen Reader Navigation Easier with the header Landmark
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I don’t think fixing the legacy challenges is all that important, we can leave those if we want but we should probably fix up the new CatPhotoApp and Cafe Menu projects.
Does this not defeat the purpose of a
header? Should we scrap theheaderall-together from this project?