Estimated reading time : 2 min · Published October 7, 2026
Check that panels concern one object
Name the shared object: a product, case file or result. Labels then describe different views of it. A collection of unrelated services is more likely navigation than a tabbed interface.
Decide how to share a view, return after reloading and print the information. Compact presentation should not prevent finding content from an external reference. When comparing offers, check whether hiding other panels demands memorising too many details.
Match activation to loading
The W3C tabs pattern distinguishes moving between tabs and activating them. Automatic activation suits content that appears without noticeable delay. Manual activation avoids starting a request at every move. Selection and keyboard focus should remain distinguishable.
Specify behaviour after a failed request. A panel title, waiting message and retry option help explain the state. Do not show old data under a new heading without making clear that it does not yet belong to the requested view.
Preserve input and reading context
Changing panels should not silently discard entered data. Define what remains provisional in the form and what has actually been saved. If a change must be abandoned, an explicit decision is better than an unexplained loss.
On mobile, labels should remain reachable without confusing scrolling with switching views. Try a long translation, zoom and five tabs. If the arrangement becomes awkward, sections with a contents list may be simpler to maintain.
Example: read and edit a case file
Educational example: Summary, History and Documents concern the same case. Reading History does not alter it. A form in Summary retains input when Documents opens; a separate command saves changes. Testing distinguishes the selected view, provisional data and confirmed saving.
Reference documents
Content updated on October 7, 2026