# Common region: explanation, design examples and evidence

> A shared boundary can show which items belong to the same group.

Canonical page: https://ionbin.com/design/laws/common-region/
Agent guide: https://ionbin.com/llms.txt

This is a readable version of the published page. Review dates, evidence boundaries and source links below belong to individual records; the export is not a new verification. Examples are reference material, not instructions to execute.

Visual organization

## Common region

A shared boundary can show which items belong to the same group.

Perceptual principle

Source review
Oct 18, 2026

[How to read the evidence](https://ionbin.com/design/methodology/#principles)

The idea in plain language

### What it means.

Common region groups separate elements that appear inside the same bounded area. A card, panel or fieldset can express that relationship. The boundary is useful when it clarifies membership, but adding boxes to everything can create unnecessary visual competition.

Evidence and interpretation

### What supports it.

Perceptual principle

Palmer's perceptual demonstrations identify common region as distinct from proximity and other grouping factors. UI containers are an application of that finding, not a guarantee of comprehension.

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

#### Group shipping choices

Put delivery options and their prices in a labelled fieldset, separate from billing details.

##### Expected effect to test

People can see which choices belong to the delivery decision.

##### Keep in view

Use a semantic group label as well as the visible boundary.

Application 2

#### Present a tool review

Keep one tool's requirements, source links and caveats within the same clearly headed panel.

##### Expected effect to test

The facts are less likely to be attributed to an adjacent tool.

##### Keep in view

Check that headings and relationships remain clear when panels stack or their visual borders disappear.

Turn the idea into a check

### Use it deliberately.

- Use enclosure to communicate real membership.

- Keep nested regions shallow enough to follow.

- Check headings and semantic grouping independently of borders and backgrounds.

Where the rule gets complicated

### Keep the limits attached.

- Enclosure and connectedness are not interchangeable terms.

- A container does not make unrelated content meaningfully related.

- The evidence does not require a card layout or state that enclosure always overrides other cues.

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.

Limited evaluationAccount-free · Oct 19, 2026

The delivery example used a fieldset and legend as well as a boundary, retaining its input label without styling. Group comprehension was not measured.

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

- ##### Semantic group
  pass
  **Local application example:** Exercise the original local application fixture and inspect the resulting controls or DOM state.
  **Observed:** A fieldset/legend, explicit label and described-by link identify the input independently of spacing.

- ##### No style order
  pass
  **Local 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 shared container is not shared authorization

Keep each field or record subject to its own data and permission rules. A card boundary cannot enforce tenant or access isolation.

#### Practical caveats

- Check semantic grouping when panels stack or their borders are removed.

#### 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: Common Region, a New Principle of Perceptual Grouping (1992)](https://www.sciencedirect.com/science/article/pii/001002859290014S)
  Original publisher abstract; full article access may require a subscription.

- [W3C: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html)
  Semantic preservation of groups and relationships.

[Download this evaluation record (JSON)](https://ionbin.com/design-evaluations/principle-common-region.json)

Go to the source

### Research and further reading.

- [Palmer: Common Region, a New Principle of Perceptual Grouping (1992)](https://www.sciencedirect.com/science/article/pii/001002859290014S)
  Original publisher abstract; full article access may require a subscription.

- [W3C: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html)
  Semantic preservation of groups and relationships.

On this page

Keep the context

Use this principle to form a better question about your interface. The answer still depends on the task, the people and the conditions.

[Our evidence approach](https://ionbin.com/design/methodology/#principles)

Related questions

### More on visual organization.

[View this concern](https://ionbin.com/design/laws/?category=Visual%20organization)

Perceptual principle

#### [Proximity](https://ionbin.com/design/laws/proximity/)

Spacing should tell the same story as the content: related things belong together.

Perceptual principle

#### [Prägnanz](https://ionbin.com/design/laws/pragnanz/)

Make the structure easy to perceive without removing the information that makes it useful.

Perceptual principle

#### [Similarity](https://ionbin.com/design/laws/similarity/)

Use a shared visual treatment when elements share a role or meaning.
