In a client-side routed app, a user activates a link. The URL changes and the new page renders. What has the browser stopped doing for you, and what must you now do by hand?
Answer it out loud before you open anything. The value of the flags below is in comparing them to what you actually said.
The situation behind the question
A documentation site converted from server-rendered pages to a SPA. Nothing looks different. A screen-reader user reports that following a link "does nothing", and a keyboard user reports that Tab after navigating goes to the site header again from the top.
What it is really testing
Whether the candidate knows what a real navigation provides and that client-side routing silently opts out of all of it. This is the clearest case in the domain of accessibility as engineering: nothing is visually wrong and the page is unusable for two input methods.