Operable / 2.4 Navigable
2.4.1Bypass Blocks
Level AProvide a way to skip repeated blocks of content, such as navigation menus, and jump straight to the main content -- for example with a skip link, landmark regions, or a proper heading structure. Without this, keyboard and screen reader users must navigate through the same repeated menu on every single page before reaching the content they came for.
Note
A detailed commentary for this success criterion is not yet available. In the meantime, this page lists related patterns, techniques, and links to the normative sources.
Related Techniques
Specific implementation techniques for meeting this success criterion. This site doesn't include the full text, so follow the links to the original W3C documents.
Sufficient Techniques(8)
- ARIA11: Using ARIA landmarks to identify regions of a page(opens in a new tab)waic.jp(opens in a new tab)
- G1: Adding a link at the top of each page that goes directly to the main content area(opens in a new tab)waic.jp(opens in a new tab)
- G123: Adding a link at the beginning of a block of repeated content to go to the end of the block(opens in a new tab)waic.jp(opens in a new tab)
- G124: Adding links at the top of the page to each area of the content(opens in a new tab)waic.jp(opens in a new tab)
- H64: Using the title attribute of the iframe element(opens in a new tab)waic.jp(opens in a new tab)
- H69: Providing heading elements at the beginning of each section of content(opens in a new tab)waic.jp(opens in a new tab)
- PDF9: Providing headings by marking content with heading tags in PDF documents(opens in a new tab)waic.jp(opens in a new tab)
- SCR28: Using an expandable and collapsible menu to bypass block of content(opens in a new tab)waic.jp(opens in a new tab)
Normative References
- Success Criterion 2.4.1 Bypass Blocks — WCAG 2.2(opens in a new tab)The normative requirement text.
- Understanding Bypass Blocks — W3C(opens in a new tab)Official guidance on intent, examples, and techniques.