2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
SC 2.4.1 Bypass Blocks is part of the accessibility principle Operable because all users must be able to easily navigate the Web site, including bypassing repetitive information in order to get to the main content. This SC impacts users who are without or have limited vision, have limited language, cognitive, and learning abilities, limited manipulation, or limited reach and strength.
The intent of this SC is to ensure a method is provided to skip blocks of repeated content so that a user can move directly to the main page content without having to hear or tab through repetitive information. The method to bypass blocks of content must be operable from a keyboard.
Repeated blocks of content are defined as content that appears on other pages within a website prior to the main page content itself. This means that the repetitive content must appear on more than a single page for this SC to apply. Some examples of blocks of content are navigation links and menus, page headers, banners, header graphics, and advertising frames. Further, small repeated sections such as words, single links, or phrases are not considered blocks of text that must meet this SC.
When implemented correctly, SC 2.4.1 Bypass Blocks ensures users can easily and quickly reach the main content of the Web page.
Ways in which an author can allow the user skip blocks of repeated content include:
- Adding a link (such as a link to skip to the main content) to bypass all repeated block content and jump directly to the main page content.
- Grouping blocks of repeated content in a way that could be skipped by:
- Using an expandable menu to bypass blocks of content.
- Grouping repeated content in a frame in each Web page with a descriptive title to allow users to use frame navigation keystroke to navigate all Web page content and choose which frames they want to interact with, allowing them to bypass repeated content. Note: Frames are not supported in HTML 5.0 or by all browsers.
Methods that rely on AT to bypass blocks of content do not support all AT users. Those methods will not work, for example, for users with low vision who rely on a web browsers built-in zoom features. The following WCAG techniques require additional AT to function as bypass methods and are not considered sufficient for meeting this SC:
- Providing heading elements at the beginning of each section of content.
- Using ARIA landmarks to identify regions of a page.
Impact of Nonconformance with SC 2.4.1 Bypass Blocks
| Type of Disability | Description of Impact |
|---|---|
| 302.1 Without Vision | Users who are blind cannot use a mouse to interact with electronic content and typically use an assistive technology, such as a screen reader, to get audible or other alternative output for the information represented visually. To be able to navigate the content, understand its structure and relationships, and understand the meaning of content represented in graphics and images, the content must provide textual and programmatic cues in addition to the content presented purely visually. |
| 302.2 With Limited Vision | Users with limited vision may have widely different visual perception. Individuals with limited vision may or may not use assistive technologies. Therefore, in addition to textual and programmatic cues necessary for assistive technologies, ICT must also present content consistently and predictably. Users who view content with magnifiers may not pick up alerts, warnings, or other content if such content is presented outside of a consistent and predictable navigation pattern or if the content is not itself viewable at large magnification. Content that becomes distorted when magnified can also prevent some users with limited vision from being able to understand or interact with the content. |
| 302.7 With Limited Manipulation | Some users may not be able to perform actions that require fine motor control (clicking and dragging), path dependent gestures (pattern-based passcodes), or simultaneous actions (Ctrl + Alt + Del). Providing alternative means to perform the same actions, such as entering the size specifications in an input field to resize an object or allowing sequential key entries, can enable users with limited manipulation to interact with the same content. |
| 302.8 With Limited Reach and Strength | Some users may lack sufficient strength to perform actions such as squeezing, grasping, or depressing a hardware control. Some users, including those in wheelchairs or of shorter stature, may not be able to reach controls that are placed too high or too far away from where a user would access the device controls or interface. ICT designers and developers must consider a broad range of statures, strength and dexterity limitations, and the needs of wheelchair users in order to provide interfaces that are operable with limited reach and/or strength. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Some users require more time than average to process information while others may find complicated instructions difficult to follow. Furthermore, some ICT content can distract or overwhelm users, preventing them from being able to interact with or understand other ICT content. Designers and developers of ICT must consider a broad range of cognitive abilities in order to provide ICT that is simple and easy to use. |
Applicability of Success Criteria 2.4.1 Bypass Blocks
| Technology | Applicability of SC 2.4.1 Bypass Blocks |
|---|---|
| Web | Mechanisms to bypass blocks of content that are repeated on multiple Web pages often include, “skip” links, hotkey navigation to specific points or areas of a page. Other methods, such as buttons and/or coded scripts to facilitate navigation around repeated blocks of content might also be used. |
| Software | Per the Revised Section 508 Standards, 2.4.1 Bypass Blocks DOES NOT APPLY to non-Web software. |
| Office documents | Per the Revised Section 508 Standards, 2.4.1 Bypass Blocks DOES NOT APPLY to non-Web documents. |
| PDF documents | Per the Revised Section 508 Standards, 2.4.1 Bypass Blocks DOES NOT APPLY to non-Web documents. |
| Mobile Native | Per the Revised Section 508 Standards, 2.4.1 Bypass Blocks DOES NOT APPLY to non-Web, mobile-native software. |