acc

How to fix: Skip navigation link (WCAG 2.4.1 A)

Part of the Accessibility pillar on the Site Integrity Index.

Why this matters

On every page, keyboard users currently tab through every nav link before reaching the main content. A skip-link as the first focusable element bypasses that. WCAG 2.4.1 Level A: provide a mechanism to bypass blocks of repeated content.

Background

Keyboard users tab through every nav link before reaching main content on every page visit. A skip link as the first focusable element bypasses that. WCAG 2.4.1 Level A applies.

References

WCAG 2.1 SC 2.4.1 Bypass Blocks (A)

How to fix

Code snippet for each stack we cover. Pick the one matching your server / framework.

nginx

No server config — template change.

apache

Same.

cloudflare

Same.

wordpress

Add a skip-link as the FIRST <a> in <body>: <a class="screen-reader-text" href="#main">Skip to content</a>. Most accessibility-aware themes (Twenty Twenty-Four onwards) include this.

flask

Base template: add <a class="skip-link" href="#main">Skip to content</a> as the first body element. Style with CSS to show only on focus.

express

Same.

rails

Same.

Verify it's working

Press Tab once on a fresh page. The first focusable element should be the skip link.

Want to know if your site has this issue?

Run a free audit — security, GDPR, technical SEO, AEO/GEO, and WCAG accessibility.

Audit my site →