WCAG 2.2 success criterion 2.4.1, Bypass Blocks, is a Level A requirement: a mechanism exists to bypass repeated blocks.
Read the criterion in the W3C Recommendation, WCAG 2.2 (opens in a new tab).
How BearScan checks it
A mechanism exists to bypass repeated blocks
Checked automatically: reads the HTML. Severity: medium. Without a skip link or landmark structure, a keyboard user traverses the same navigation on every page.
An approximation: A skip link passes, and so do landmarks (a main landmark and at least one other), which are WCAG's own sufficient technique for this criterion. Where nothing repeats the rule is not applicable, and axe-core's page-level check is not consulted: a site of one page that links to no other page of its own, or a page with no header, navigation or sidebar and fewer than 5 links. A page with no such region but more links than that may still hold an unmarked navigation block, so axe-core's result stands there. Whether the skip link's target exists is checked by axe-core.
How to fix it. Add a skip link as the first focusable element, and use header, nav, main, and footer landmarks so the structure is exposed.
All WCAG 2.2 criteria · Next: 2.4.2 Page Titled
Questions
Is WCAG 2.4.1 required by the ADA?
The ADA doesn't name a technical standard for businesses, but the Justice Department's 2022 guidance points businesses to WCAG, and its 2024 rule for state and local governments adopted WCAG 2.1 Level AA, which includes 2.4.1.
Can an automated tool check WCAG 2.4.1?
Mostly. BearScan checks it automatically (reads the HTML). A clean result still isn't proof every page passes, only the pages scanned.
How do I fix a WCAG 2.4.1 failure?
Add a skip link as the first focusable element, and use header, nav, main, and footer landmarks so the structure is exposed.