Should a cookie banner move keyboard focus on load?

It should be reachable early and predictably. Whether it takes focus automatically depends on whether it blocks the page. If it blocks interaction, focus belongs inside it until the shopper chooses, and then it must be released.

Is a reject button required in the first layer?

For a fair choice, yes in practice. Hiding reject inside preferences while accept sits in the first layer draws criticism from privacy regulators and makes the keyboard path far longer for refusal than for acceptance.

How often should banner accessibility be checked?

After every consent platform or theme change, and on a regular monthly pass. Vendor updates ship independently of your release calendar, so a check tied only to your own deploys will miss them.

Can an automated scan verify banner focus behaviour?

No. Scans catch missing names and contrast. Focus order, traps, and focus return need a manual keyboard pass. That is why monitoring programmes pair the scan with a short scripted manual check.

Monitoring Skip Links: The First Tab Stop Nobody Tests

October 30, 2026

A skip link that is missing, points at the wrong target, or stays invisible breaks keyboard navigation from the first keypress. How to keep it under routine monitoring.

Press tab once on any store page. The first thing that should appear is a skip to content link. On a surprising number of stores it does not appear at all, or it appears and goes nowhere, because the target element it points to was renamed in a redesign and nobody updated the link.

A skip link exists because keyboard and screen reader users should not have to work through forty navigation links on every page. WCAG 2.4.1, bypass blocks, is the criterion. It is an A level requirement, the floor, and it still breaks quietly.

Three ways a skip link fails

First, it is absent. A new header component ships without it. Second, it is present but invisible on focus, styled away by the same reset that removes outlines, so a sighted keyboard user tabs past a link they never saw. Third, and most common, the link is there and visible but its target is dead: the main element lost its id, so activating the link does nothing at all.

Screen reader users get a version of the third failure too. Focus may move while the reading cursor does not, depending on implementation, leaving the user back in the navigation they tried to skip. A link that looks right in the markup can still fail in use, which is why this needs hands on testing, not a code scan.

A two minute test

Load the page, press tab once, and look. Is a link visible, with text that says where it goes? Press enter. Does the page jump past the navigation, and does the next tab press land on the first element of the main content rather than back in the header? That last check is the one that catches dead targets.

Repeat it on a product page and in the cart, not just the home page. Templates diverge. A store can have a working skip link on the home page and a broken one on the template that carries most of its traffic.

Monitoring, not memory

Add the skip link to the template regression list alongside focus visibility. Any change to the header, the main landmark, or the theme layout triggers the two minute test on every affected template before release.

Fix failures in the shared layout, once. The link, its target id, and its visible on focus style should live in one place in the theme, so a redesign cannot drop one half of the mechanism and keep the other.

Frequently asked questions

What WCAG criterion requires a skip link?

WCAG 2.4.1, bypass blocks, level A. It requires a mechanism to skip repeated blocks such as navigation. A skip link is the usual mechanism, though proper landmark structure also helps screen reader users.

Why does my skip link not move the screen reader cursor?

The target element may be missing its id, or the target may not be focusable. Giving the main element a tabindex of minus one and pointing the link at its id fixes most cases, but test it in a real screen reader.

Should the skip link be visible all the time?

It does not have to be. Visually hidden until focused is a standard, acceptable pattern, as long as it becomes clearly visible when it receives keyboard focus.

Which pages should be tested?

Every distinct template, at minimum home, collection, product, cart, and checkout. Template level differences are exactly where skip links quietly break.