Concept cluster
Compare static tabular reading, cell-by-cell interaction, and expandable hierarchical navigation.
Should people read tabular data, interact cell by cell, or expand a hierarchy?
Try it
Compare all three behaviors
Shared comparison scenario: A workspace presents a large information set whose structure and interaction model determine how people scan, edit, or expand it.
This context stays fixed. Switch concepts to observe the mission, edge case, and specimen specific to each behavior.
Table
Table is read as document content and its cells are not focus-managed; Data grid is a composite widget with arrow-key cell navigation, while Tree view organizes hierarchical nodes.
Your task
Sort Name ascending and then descending while confirming focus and header context remain intact.
Edge case to verify
Long values use horizontal overflow without converting rows into inaccessible cards or breaking header associations.
Mission
Sort Name ascending and then descending while confirming focus and header context remain intact.
| Status | Owner | |
|---|---|---|
| Beacon | Review | Léo |
| Atlas | Ready | Amina |
| Comet | Draft | Marta |
Select a numbered marker on the schematic, or use the list below, to see its role. The schematic shows the concept's representative state.
Table
The tabular container that preserves row and column relationships.
These descriptions fit every concept in the cluster, so none of them is enough to decide.
Audience measurement
With your consent, Google Analytics and aggregate first-party counters measure site usage to help us improve it. These counters contain no search text, candidate, session identifier, or event identifier. You can change your choice anytime via “Cookies” in the footer.