While working on a SPA, it often comes up that we paginate content to reduce UI complexity, even though the other "pages" are already available.
Thinking about this from a keyboard or screen reader user's perspective, it seems like pagination could lead to a more complicated UI, as the user would need to choose "next page", then move their focus to the top of the screen to resume reading again. It seems like a better experience would be to allow screen readers to access all the content immediately, and let the user navigate using Headings
In the image above, we have a series of 6 questions that the user gets asked. A visual user sees one question at a time. After answering one question, the answered question slides away and the next question slides in to view. The arrows in the bottom right allow the user to skip a question or go back. JS moved the user's focus as answer or skip a question.
The alternative navigation for a screen reader user might allow them to read all 6 questions by skipping to the next Heading, with an aria-hidden on the controls.