New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
The URL changes, but my cursor is still sitting on the old nav link like nothing happened.
What you'll have at the end
A route change that moves keyboard focus to the new page's own heading and updates the browser tab's title to match, on every navigation including the browser's own back and forward controls.
You need
A client-side router already wired up so links change the URL and swap the rendered view without a full page reload, with each route rendering its own visible heading.
Not covered
Announcing the change with a live region instead of moving focus, and building a dedicated skip-back-to-navigation control: this recipe only moves focus to the heading and updates the title.
Leans on
Scan an entire site for accessibility bugs from a terminal
for the automated sweep that still won't catch this exact runtime bug, though it catches plenty else across every page.
What does your app sound like to a screen reader user?
for turning on a real screen reader in the first place, before checking that it speaks the right heading here.
Checked 24 Aug 2026
Part of the Web Accessibility cookbook