Visual organization
Uniform connectedness
A continuous visual unit and a set of items inside a box are different grouping cues.
The idea in plain language
What it means.
Palmer and Rock describe connected regions with relatively uniform properties as perceptual units. The related element-connectedness principle concerns parts sharing a boundary. A connector can therefore communicate a relationship, but a box surrounding separate objects belongs under common region. The distinction helps explain what a diagram is actually showing.
Evidence and interpretation
What supports it.
Perceptual demonstrations and a theoretical account of unit formation. The source itself includes depth-related qualifications; it does not establish an unconditional ranking above every other grouping cue.
From principle to interface
Where you could use it.
Proposed applications, not tested outcomes. The expected effects are hypotheses to check with realistic tasks and users.
Application 1
Draw a dependency map
Join a service to the database it reads with a labelled connector and an explicit direction.
Expected effect to test
The relationship is represented directly instead of being inferred from proximity.
Keep in view
A line alone does not explain ownership, data direction or permission. Label its meaning and offer a text representation.
Application 2
Show a process path
Connect numbered stages with a continuous line and label completed, current and future states.
Expected effect to test
The stages read as one sequence.
Keep in view
Branching or optional steps need explicit treatment; do not draw a linear path that misrepresents the process.
Turn the idea into a check
Use it deliberately.
- Distinguish a connected unit from separate objects sharing a container.
- Give connectors explicit meanings and avoid accidental crossings.
- Provide equivalent relationships in text or semantic structure.
Where the rule gets complicated
Keep the limits attached.
- Common region is a separate principle and has its own entry.
- A visual connection does not create an accessible programmatic relationship.
- Busy connector networks can obscure the very relationships they are meant to explain.
A named principle does not settle an accessibility requirement, prove a conversion lift or replace testing the particular interface.
Application and implementation boundaries
What the application check shows.
The example provided an ordered text process beneath its visual connector treatment. No experiment compared connectedness with other grouping cues.
Methods: Local application example. A completed check covers the stated sample; it is not a safety certification.
- Target
- Original IonBin synthetic interface example; no external product or human-participant study.
- Version or capture
- 2026-10-19 local fixture
- Integrity scope
- SHA-256 f85d1056afd667225a1e0364edfb8f25b4693ffa7b2b8c7d7af5b92338b85ee4 identifies the exact HTML fixture only.
Test conditions
- 155.0.8059.82 Chromium; fresh context with all network requests blocked.
- Synthetic inputs, memory-only state, reduced-motion preference, 1280px and 320px viewports.
Individual checks and observations
No style order
passLocal application example: Exercise the original local application fixture and inspect the resulting controls or DOM state.
Observed: With authored CSS disabled, the named input and ordered process remained present.
Security findings and boundaries
Review of the local example’s stated interaction boundaries; no backend, authentication, production permissions or external service was exercised.
Practical advice · caution
A drawn connection does not grant permission
A dependency line cannot establish a trusted data route, ownership or authorization. Document endpoints and permission scope separately.
Practical caveats
- Label connector meaning and offer a meaningful text representation when diagrams cannot be perceived.
What remains untested
- This checks an authored application example, not the truth, effect size or generality of the named principle.
- No users, assistive-technology participants, physical devices or production task outcomes were evaluated.
Security limits
- The example has no real authorization or persistence layer; its UI behavior cannot establish the security of a deployed workflow.
Evaluation sources
- Palmer and Rock: Rethinking Perceptual Organization (1994)
Author abstract defining uniform connectedness and its qualifications.
- Palmer: Perceptual Organization in Vision (2002)
Author's discussion distinguishing common region and element connectedness.
Go to the source
Research and further reading.
- Palmer and Rock: Rethinking Perceptual Organization (1994)
Author abstract defining uniform connectedness and its qualifications.
- Palmer: Perceptual Organization in Vision (2002)
Author's discussion distinguishing common region and element connectedness.
Related questions
More on visual organization.
Perceptual principle
Proximity
Spacing should tell the same story as the content: related things belong together.
Perceptual principle
Prägnanz
Make the structure easy to perceive without removing the information that makes it useful.
Perceptual principle
Similarity
Use a shared visual treatment when elements share a role or meaning.