Why it matters
- A screen-reader user jumps to the content by its heading or its
<main>; a keyboard user by a "skip to content" link. Without any of them, they go through the whole menu on every page. - WCAG 2.2 asks for a way to bypass blocks repeated on several pages (success criterion 2.4.1, level A). Headings, landmarks and skip links each meet it.
Example
<div class="menu"> <a href="/oud/">العود</a> <a href="/musk/">المسك</a> <a href="/amber/">العنبر</a> <a href="/rose/">الورد</a> </div>
<nav aria-label="التصنيفات"> <a href="/oud/">العود</a> <a href="/musk/">المسك</a> <a href="/amber/">العنبر</a> <a href="/rose/">الورد</a> </nav> <main> <h1>عطر العود الملكي</h1> <p>عطر عود ملكي بتركيز عالٍ، في زجاجة من 50 مل.</p> </main>
How to fix
Mark up the page's parts with the elements made for them, and give the content a heading:
html
<nav aria-label="التصنيفات">…</nav>
<main>
<h1>عطر العود الملكي</h1>
…
</main>- A skip link as the first thing in
<body>also works:<a href="#content">انتقل إلى المحتوى</a>.
How we detect
- We render the page and run axe-core 4.13.0's
bypassrule in each engine. - It finds a page that has none of these: a heading, a landmark, or a link to a place on the same page. axe never decides this rule alone, since a heading may be there and still not help, so we ask a person to look and never deduct it.
- axe's
regionrule (all content inside landmarks) is a best practice, not a WCAG criterion, and we do not run it.