An SPA Audit for the Page That Never Reloads and Never Moves Focus

What We Keep Finding

On a classic site, clicking a link reloads the page and the screen reader starts fresh at the top. In a single-page app the URL changes, the view swaps, and none of that happens for free. That much is the inheritance every SPA shares. What has changed, and changed recently enough that most advice has not caught up, is that the announcement half now has framework answers and the focus half still has none.

Announcement first, because the answer depends on what you are running. Next.js ships a route announcer in both of its routers and mounts it whether you asked for it or not. Nuxt ships one too, since v3.12, but it is a component you have to add yourself, so a default Nuxt app is silent. Every announcer we have looked at reads the page title, which means the real failure has moved. Two routes sharing a title announce nothing, and a missing or duplicated title is now the bug rather than the framework being deaf. Politeness differs as well, since Next interrupts and Nuxt waits its turn.

Focus is the half nobody solved. No framework we have checked moves it. After a navigation, focus is still on the link that was clicked, in a view that no longer exists. Which is why a keyboard user can hear the new page announced and still be unable to reach it. And the two halves interact rather than stacking. Moving focus to the new view is itself a change of context. So a page that moves focus and also fires its own announcement says the same thing twice, and the second one talks over the first. Doing both is not belt and braces. It is a defect.

Then there is everything that updates without a navigation at all, which is most of what a modern app does. Filters, tabs, infinite feeds, optimistic saves. Changing content is not automatically a change of context, so those need announcing rather than focus moves, and the distinction is exactly where in-app updates get built wrong.