Skip Link Accessibility Ticket Example
Skip-link tickets should name the repeated block, the intended landing point, and how keyboard users can prove the shortcut works.
Developer-ready ticket
# [Medium] Homepage: keyboard users cannot bypass repeated header navigation ## User impact Keyboard and screen reader users must tab through the same header navigation on every page before reaching the main content. This adds avoidable effort and makes content-heavy pages slower to use. ## Expected behavior At the start of the page, keyboard users can activate a visible-on-focus skip link that moves focus to the main content. The target is the page's main landmark or the first meaningful heading inside it. ## Actual behavior The first Tab stop is the logo link, followed by every primary navigation and account link. There is no skip link or equivalent bypass mechanism. ## Reproduction steps 1. Open the homepage. 2. Press Tab from the browser address bar. 3. Continue tabbing until the page content receives focus. 4. Observe that repeated header navigation cannot be skipped. ## Likely WCAG references to verify - 2.4.1 Bypass Blocks - 2.4.3 Focus Order - 2.4.7 Focus Visible ## Acceptance criteria - A skip link or equivalent mechanism appears when it receives keyboard focus. - Activating the skip link moves focus to the main content target. - The target is a real main landmark or focusable content start. - The skip link remains usable at common desktop, mobile, and zoomed viewports.
Paste-ready input for the generator
Manual keyboard finding: homepage is missing a skip link. Repeated header navigation contains logo, category links, search, account, and cart controls before the main content. Keyboard users must tab through the full header on every page. Page: Homepage Expected: a visible-on-focus skip link moves focus to the main content landmark. Actual: the first Tab stop is the logo and there is no bypass mechanism.