1. Identify what the reader needs to bypass
Open a representative page and identify the repeated header, navigation, or other material before the main task. Define where the page’s main content begins. A directory hub, an article, and a form may have different useful destinations even when they share the same header.
W3C’s G1 technique describes a link at the start of the page that moves focus past repeated material to the main content. It is one documented way to address bypassing blocks, not a requirement that every site use an identical implementation. Keep the desired reader outcome clear before choosing the markup.
Sources: [1]
2. Check the first keyboard encounter
W3C’s procedure checks that the link is the first focusable control, has a description that communicates its purpose, and is visible either always or when focused. Use a concise label such as “Skip to main content” when that accurately names the destination.
In a real browser check, begin from a known starting point and move focus with the keyboard. Inspect whether the focused link can be seen against the page background and whether a sticky header, banner, or overlay covers it. Record the viewport and browser used; a source-code check alone cannot show whether the visible result is usable.
Sources: [1]
3. Verify the destination in the rendered page
Follow the link and inspect the element it targets. Confirm that the target exists once on the page and corresponds to the intended main content. A copied template can accidentally retain a fragment identifier that belongs to a different layout.
Compare the visual position with the actual navigation result. Jumping the viewport while leaving the reader at an unrelated keyboard position is not the outcome you intended. W3C’s test specifically includes checking the resulting focus. Avoid declaring success merely because the address bar now contains a fragment or because an automated link checker found the target ID.
Sources: [1]
4. Continue the task after the jump
After activation, continue navigating through the main content’s controls or links. Check that the path makes sense for the page: a filter on a directory, the first useful link in an article, or the initial field of a form. Also check that visible content is not hidden beneath a fixed header.
Repeat on pages that use different templates and on the responsive layouts you support. Shared CSS can make a link work in one arrangement and hide it in another. If a consent banner or dialog is part of the normal experience, include its relevant state in the test record rather than testing only a simplified page.
5. Keep a focused regression record
Record the tested page, viewport, browser, starting state, result, and any unresolved issue. Save a short reproduction sequence for a failure so another maintainer can repeat it. Keep static findings, such as a missing target, distinct from observed keyboard behavior.
When the header, main layout, or overlay behavior changes, repeat this route. The check is small enough to include in a release review, but it does not replace a wider keyboard or accessibility assessment. If browser testing is unavailable, say which structural checks passed and leave interactive verification pending instead of describing the link as fully tested.
Your quick checklist
- The intended main-content destination is defined.
- The link is encountered and visible during keyboard navigation.
- The unique target exists and focus reaches the intended area.
- Navigation continues usefully on relevant responsive layouts.
- Observed behavior and remaining test gaps are recorded.
Sources & scope
W3C supports the skip-link technique and test criteria. The release worksheet is ATN editorial guidance. This article describes how to test a site; it does not claim that a browser or assistive-technology audit was performed on ATN.
- W3C WCAG Technique G1: Skip to main content (opens in a new tab)Source checked October 9, 2026
Published October 9, 2026. No affiliate links or paid placements in this guide.
