### Source Peer feedback, collected in #167. Quote (translated): focus is not moved to the content when navigating, and after "Load more" the focus ended up on the body because the button is disabled while it loads. When choosing a sort with the keyboard the menu stayed open, so it was unclear whether the choice was made. ### Related #162 replaces "Load more" with pagination. If that is done first, only the focus after a page change is left of the first point. ### What to do - [ ] After "Load more" (or a page change in #162) the focus must not fall to `<body>`. For example, keep the button enabled with `aria-disabled` while it loads, or move the focus to the first new result. - [ ] After a choice in the sort menu, close the menu and give the focus back to its button, and tell the visitor what was chosen (a status message). - [ ] After a navigation to a new page, move the focus to the `<h1>` or the main content, so a keyboard and screen reader user does not start in the navbar. - [ ] Add e2e tests with the keyboard for each point. ### Done when - [ ] The three cases are checked in a real browser and the focus is never lost. _Comment made with Claude Code in discussion with Ronja_