Skip link allows easy menu bypass
What this criterion checks
This criterion maps to 2.4.1 Bypass Blocks. A detailed plain-language description is maintained in the WebLens criteria catalogue; the WCAG sub-test breakdown below describes exactly what the agent checks and what it does not.
How it's assessed
WebLens walks each user journey, captures a screenshot at every step, and an agent reasons over that evidence. See the how WebLens works for the full pipeline and the deterministic checks layered in for accessibility.
Sub-test coverage
2.4.1 Bypass Blocks is broken into 2 sub-tests. Coverage is honest about where the agent is reliable, where it only partially checks the requirement, and where a human reviewer is still needed.
2 partial
- A mechanism exists to bypass repeated navigation and get to the main contentPartial
Our tool checks whether the page has a "skip to content" link near the beginning and whether activating it moves keyboard focus past the navigation. This covers the most common bypass mechanism. What still needs manual review: pages that use page regions (like a clearly marked main content area) as their bypass mechanism instead of a skip link — screen readers can navigate by these regions, which also satisfies the criterion. Sites with multiple repeated content blocks (sidebars, footer links) may need a person to verify each block can be bypassed.
- Skip link works correctly and moves focus to the main content areaPartial
When our tool finds a skip link, it activates it and checks that focus moves beyond the navigation. However, verifying that subsequent Tab presses continue within the main content — rather than jumping back to the navigation — depends on observation and may not be thoroughly confirmed in every case.
How reliable it is
This criterion is still building up testing data, so confirm its findings as you review. See Accuracy & confidence for how the confidence tags are set.