The Link Before the Logo: Auditing Skip Navigation on UK Council Homepages

A skip link is one of the smallest pieces of a council website, yet it carries a disproportionate amount of meaning. It is the first thing a keyboard user should meet when they press Tab on a homepage, and it is the mechanism that lets them bypass menus, logos, search boxes and promotional panels to reach the main content. When it works, it is quietly efficient. When it fails, it tells the user that the rest of the journey may require patience.

In 2026, the expectation is not new. The Web Content Accessibility Guidelines have long required a mechanism to bypass repeated blocks of content under success criterion 2.4.1. The Public Sector Bodies Accessibility Regulations 2018 made that expectation part of the routine compliance story for UK councils. Yet skip links remain a frequent failure in audits, not because the concept is difficult, but because the implementation is fragile. A link that is present in the HTML is not necessarily a link that works in the browser.

Why the first tab stop matters

For a keyboard-only user, the first few tab presses set the tone. If the skip link appears promptly and moves focus to the main content, the user gains confidence that the page has been designed with their method of navigation in mind. For a screen reader user, the same link can save dozens of repeated announcements. For a user with a motor impairment, it can reduce the number of key presses required before reaching the information they came for.

The skip link also functions as a diagnostic. It sits at the intersection of CSS, JavaScript, content management system templates, focus management and consent tooling. If an organisation cannot make its skip link reliable, it is worth asking what else may have been left to chance.

What a working skip link must do

A useful audit does not simply search the page source for the phrase skip to content. It tests the link as a user would. At minimum, the link should become visible when it receives keyboard focus, have an accessible name that clearly describes its destination, and move focus to the main content when activated with Enter. Moving the viewport is not enough. The focus indicator should land inside the main region so that the next Tab press continues from there.

There are three common standards to apply. First, the link should not rely on a mouse hover to appear. Second, the target should be a real element with a unique identifier, normally the main landmark, and it should be able to receive programmatic focus. Third, the link should remain usable when the page is zoomed, when a cookie banner is open, and when the site is viewed on a small screen with an external keyboard.

A repeatable audit routine

A short, disciplined routine is more valuable than an occasional heroic test. The following sequence can be repeated across homepage templates and council services.

1. Load the homepage in a fresh browser session and do not touch the mouse. Press Tab once. Record whether the skip link appears, where it appears, and whether it is legible against the page.

2. Check the link text. Labels such as Skip to content are acceptable, but the destination should be unambiguous. If there are several skip links, the first should address the most common need.

3. Activate the link with Enter. Observe the focus indicator. If the page merely scrolls and the next Tab press returns to the navigation, the bypass mechanism has not worked.

4. Inspect the target. Confirm that the identifier exists once, points to the main content rather than a wrapper, and is not hidden with display: none. A target with tabindex set to minus one is often the most reliable way to receive focus without adding the element to the normal tab order.

5. Repeat the test with a screen reader. Listen for the link announcement, activate it, and confirm that the reader moves to the main region rather than remaining in the banner or navigation.

6. Repeat at 200 per cent and 400 per cent zoom. A skip link that is visible but clipped, or a target that is obscured by a sticky header, is still a failure in practice.

7. Test with the cookie banner in its initial state, after acceptance, and after rejection. Consent tooling is one of the most common reasons a skip link becomes invisible or unreachable.

Common CMS and cookie-banner failures

Many failures are predictable. A template may insert the skip link before a consent overlay, leaving it visually present but covered by a higher stacking context. A content management system may strip the tabindex attribute from the main element during publishing, so the link scrolls but does not move focus. A visually hidden class may use display: none, which removes the link from the tab order altogether. A duplicated identifier may send focus to a different region on some templates but not others.

Sticky headers create a subtler problem. The skip link fires, the page scrolls, and the main heading disappears beneath a fixed header. The user has bypassed the navigation but cannot see the start of the content. A small amount of scroll margin on the target often resolves this without changing the visual design.

Consent banners deserve particular attention. If the banner traps focus, the skip link may never be reached. If the banner sits above the link in the stacking order, the link may be present but invisible. If the banner is dismissed with JavaScript that moves focus elsewhere, the skip link may work only in one state. Test the states, not just the default page load.

Fixing skip links without breaking the design

The most robust pattern remains a link that is visually hidden until it receives focus. It should use a clipping technique rather than display: none, become visible with a clear focus style, and sit above other page furniture when focused. The destination should be the main landmark, with a unique identifier and programmatic focus. The focus outline should not be removed. The link should be one of the first elements in the document, not inserted after the header by a script that may run late.

Design teams sometimes worry that a visible skip link will disrupt a carefully composed homepage. In practice, the link appears only for keyboard users and only while focused. It can be styled consistently with the organisation's focus treatment. The greater risk is a link that exists in the codebase but fails the first tab press.

A short release checklist

Before a council homepage is signed off, confirm that the skip link appears on first Tab, has a clear label, moves focus to the main content, survives the cookie banner, remains visible at zoom, and works with a screen reader. Check more than one template if the homepage shares components with service pages. Record the result in the accessibility statement or internal audit log so that the check is repeated after CMS upgrades.

The skip link is not a decorative nod to inclusion. It is the first test of whether the page respects a keyboard user's time. Passing it is not difficult, but it does require someone to press Tab and look.