---
title: "Skip repeated navigation to the main content"
description: "Verify a skip-navigation link is revealed and usable through a separate keyboard procedure and moves focus to the intended page content."
canonical_url: "https://vostride.com/agent-library/accessibility-flows/skip-link-main-content.md"
md_url: "https://vostride.com/agent-library/accessibility-flows/skip-link-main-content.md"
content_kind: "recipe"
topic: "accessibility-flows"
---

# Skip repeated navigation to the main content

Verify a skip-navigation link is revealed and usable through a separate keyboard procedure and moves focus to the intended page content.

## Risk

A skip link can visually scroll the page while leaving keyboard focus at the header. Record the target focus independently and verify that the next meaningful keyboard interaction follows main-content order.

## Fixtures

- A test dashboard includes a repeated navigation header and a main region with a distinctive QA activity heading and primary action.
- The design includes a keyboard-revealed Skip to content link as the first intended navigation aid.
- A prepared keyboard and semantic audit can inspect the link target, focus destination, and main landmark identity.

## Steps

1. Open the dashboard from the defined starting focus and run the separate keyboard procedure to reveal Skip to content.
2. Verify the skip link is visibly readable rather than clipped beneath the sticky header.
3. Activate it through the keyboard procedure and verify QA activity is brought into view.
4. Inspect the independent focus trace and main-landmark evidence to verify focus moved to the intended content target.
5. Continue the keyboard procedure and verify the next meaningful action is in the main content rather than restarting the entire header navigation.

## Expected results

- The skip link becomes visible when reached through the prepared keyboard path.
- Its activation reaches the intended main content both visually and in independent focus evidence.
- The subsequent interaction order bypasses the repeated header under the product contract; this is one navigation accessibility check, not a complete audit.

## False-pass traps

- Viewport scrolling to the content does not prove focus moved with it.
- Clicking a hidden link with a pointer or script would bypass the keyboard discoverability requirement.

## Cleanup

- Reset dashboard focus and close the separate keyboard-audit session.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa web testing](/docs/agent-qa/guides/web-testing.md)

- [Accessibility workflow QA recipes](/agent-library/accessibility-flows.md)
- [Software factory QA library](/agent-library.md)