Initial commit
This commit is contained in:
@@ -0,0 +1,40 @@
|
||||
[Back to 2 Operable index](index.md)
|
||||
|
||||
# 2.4.1 Bypass Blocks
|
||||
|
||||
- Level: A
|
||||
- Guideline: 2.4 Navigable
|
||||
- Principle: 2 Operable
|
||||
|
||||
## What it is
|
||||
|
||||
A mechanism is available to bypass blocks of content that are repeated on multiple web pages.
|
||||
|
||||
## How to test
|
||||
|
||||
- Check: A mechanism is available to bypass blocks of content that are repeated on multiple web pages.
|
||||
- Use the sufficient techniques below as acceptable methods when applicable.
|
||||
|
||||
## Sufficient techniques (W3C)
|
||||
|
||||
- G1: Adding a link at the top of each page that goes directly to the main content area
|
||||
- G123: Adding a link at the beginning of a block of repeated content to go to the end of the block
|
||||
- G124: Adding links at the top of the page to each area of the content
|
||||
- ARIA11: Using ARIA landmarks to identify regions of a page
|
||||
- H69: Providing heading elements at the beginning of each section of content
|
||||
- PDF9: Providing headings by marking content with heading tags in PDF documents
|
||||
- H64: Using the title attribute of the iframe element
|
||||
- SCR28: Using an expandable and collapsible menu to bypass block of content
|
||||
|
||||
## Advisory techniques (W3C)
|
||||
|
||||
- C6: Positioning content based on structural markup
|
||||
- H97: Grouping related links using the nav element
|
||||
|
||||
## Resources
|
||||
|
||||
- WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#bypass-blocks
|
||||
- Understanding: https://www.w3.org/WAI/WCAG22/Understanding/bypass-blocks.html
|
||||
- Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#bypass-blocks
|
||||
|
||||
[Back to 2 Operable index](index.md)
|
||||
Reference in New Issue
Block a user