Seeing a focus outline move to a tab does not necessarily mean that its content panel has changed. An accessible tab pattern can use manual activation. In that arrangement, moving keyboard focus and selecting the next panel are separate steps. The focus outline alone is therefore incomplete evidence of a panel change.
A hypothetical manual-activation example
Hypothetical example: A tab strip contains “Overview” and “Details.” At the start, Overview has focus and is selected, so the Overview panel is visible. The reader presses the Right Arrow key once. Focus moves to Details, but Overview remains selected and its panel remains visible. The reader then presses Enter. Details becomes selected, and the Details panel replaces Overview.
| Moment | Focused tab | Selected tab | Visible panel |
|---|---|---|---|
| Before Arrow | Overview | Overview | Overview |
| After Arrow | Details | Overview | Overview |
| After Enter | Details | Details | Details |
What the state change means
In the middle row, the reader has reached Details but has not activated it. A support note saying “Details selected, wrong content shown” would misdescribe that sequence. The more precise note is “Details focused; Overview still selected and visible.” The MDN tab-role reference describes the distinction between focus and selection, including keyboard movement and optional automatic activation.
Automatic tabs may behave differently. In that design, moving focus with an arrow can also select the new tab and show its panel immediately. Thus, the same key press can produce different visible results in different implementations.
Practical limit when reading a screen
Use the control’s selected state and the panel content—not merely the focus ring—to decide whether a tab switch occurred. This explanation concerns an implemented accessible tab pattern, not a built-in HTML tab element. A visual row of buttons, links, or decorative labels may only resemble tabs and may follow other rules. The observation alone does not diagnose a broken control, and it does not justify changing ARIA or keyboard behavior without examining the declared control pattern.