W3C WCAG 2.4.1 Bypass Blocks (Level A)
Provide a mechanism to bypass blocks of content (such as navigation) that are repeated across multiple pages
Where this comes from
Provision: 2.4.1 Bypass Blocks (Level A)
Instrument: W3C Web Content Accessibility Guidelines (WCAG) 2.2
Citation: W3C, Web Content Accessibility Guidelines (WCAG) 2.2, Success Criterion 2.4.1 Bypass Blocks, Level A, W3C Recommendation 05 October 2023
Text version: WCAG 2.2
Who it applies to
It applies when all of these are true:
- Service type — any answer
What engineering work it implies
Sample acceptance criteria Landfall generates for this obligation:
- A 'Skip to main content' link is the first focusable element and becomes visible on focus
- ARIA landmark roles (header/nav/main/aside/footer) mark the repeated regions
- Heading structure lets users navigate past repeated blocks
- The skip mechanism still works after SPA route changes
- Unit tests cover the core logic (aim for >80% coverage on new code)
Questions people ask
- Does W3C WCAG 2.4.1 Bypass Blocks (Level A) apply to my service?
- It applies when Service type — any answer.
- From when does this apply?
- W3C WCAG 2.4.1 Bypass Blocks (Level A) applies from 5 October 2023. Its current status is: in force.
Find out whether this one lands on you
Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.
Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.