Interaction testing
Test Focus After Client-Side Navigation
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Review what happens when a single-page application changes its main view without a full browser load. Check the document title, announcement and next keyboard position together. The goal is an understandable transition, not a mandatory identical focus rule for every route.
A practical example
Selecting an account section replaces the main content while the navigation remains mounted.
How to check it
- Activate an internal route with the keyboard. Record the active element before and after the transition and whether the new page title is meaningful.
- Read the new content with a screen reader. Check whether a user can identify the destination and reach its primary content without re-reading unrelated material.
- Test browser Back, filtered results and nested views separately. Verify that intentional focus restoration does not override a user's interaction after the route has loaded.
What can be missed
Moving focus on every minor update can be disruptive. Distinguish a new page-like context from an inline update that should preserve focus and announce a status.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.