For a fictional club guide, changing a reading filter should make the result understandable. A reader may choose a language from a dropdown, expect the visible article list to update on the same page, and continue from the control. That is different from opening a new tab or moving elsewhere without a clear warning.
Separate the filter choice from the next action
Imagine a control labelled “Language”, with options for English, Hindi and Marathi. Selecting “Hindi” may update only the article list on the current page. The selected value is the input; it is not automatically the same as pressing a separate “Go” button.
Compare two instructions: “Selection opens the chosen language in a new tab” and “Choose a language, then press Go.” The first warns before the setting changes; the second describes a separate activation step.
What counts as an unexplained jump?
In this hypothetical example, the reader selects Marathi. The visible list changes, but focus remains on the language control. The reader can understand the update and decide what to do next. This is a local page update, not necessarily a context change.
By contrast, selecting Marathi could unexpectedly open a new tab or move focus to an unrelated heading. An unannounced relocation interrupts the expected reading sequence.
How to assess the behaviour
Check the stated interaction rather than applying an absolute ban on automatic updates. Ask three concrete questions: does the filter update only the intended article list, is the reader told beforehand about any larger change, and does focus remain meaningful after the update? A list refresh can be suitable when it does not unexpectedly relocate the reader.
WCAG 2.2’s guidance for input changes explains that changing a control setting should not automatically cause a context change unless the reader has been advised beforehand. See the W3C explanation of input changes for the relevant criterion.